Skip to content

nando65/orathon-second-brain / .agents/skills/improve

improve

Verified

Turn one recurring pain point into one measurable, bounded workflow improvement.

FileKindSize
SKILL.mdskill md2.0 KB
---
name: improve
description: Turn one recurring pain point into one measurable, bounded workflow improvement.
argument-hint: "[problem or workflow]"
---

# Improve

Read `SYSTEM.md`, current objectives, source registry, decision journal, relevant captures, and recent healthchecks.

The goal is one useful improvement per run, not a broad transformation plan.

## Step 1 — Select one problem

Prefer a problem that is:
- repeated,
- expensive in time or errors,
- tied to a current objective,
- and narrow enough to test.

If the user already supplied a specific problem, use it unless evidence shows a prerequisite is missing.

## Step 2 — Define the before and after

Capture:
- current process,
- current pain or failure mode,
- desired output,
- one measurable success signal,
- who reviews or owns the result.

## Step 3 — Simplify before automating

Ask:
- Can any step be removed?
- Can inputs be standardized?
- Can a deterministic rule solve part of it?
- Which parts genuinely need language-model reasoning?
- Which decisions should remain human-owned?

## Step 4 — Map the workflow

Write:
- trigger,
- inputs and authoritative sources,
- ordered operations,
- decisions/branches,
- output destination,
- error path,
- privacy or permission constraints.

## Step 5 — Choose the smallest implementation

Use the least complex option that meets the goal:

1. checklist or template,
2. reusable prompt,
3. deterministic script,
4. AI-assisted workflow with review,
5. multi-step agent only when the earlier options are insufficient.

## Step 6 — Define acceptance

Before building, specify:
- sample input,
- expected output,
- what must never happen,
- how a human will verify quality,
- what evidence is required before increasing autonomy.

## Deliver

Record the decision in `journal/decisions.md`.

Then create or update one artifact under `workflows/` that implements the chosen approach. Preserve unrelated files.

End with:
- what changed,
- how to test it,
- what evidence would justify the next iteration.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall