From agentic-workflow-framework
Use automatically for non-trivial engineering work: multi-step tasks, changes across 2+ files, risky or cross-cutting refactors, debugging with unknown root cause, multi-session work, structured task ledgers, blockers, handoffs, known issues, and verification planning. Drives Orchestrator dispatch-by-default with planner/finder/researcher/builder/reviewer/tester/auditor/watcher subagents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-workflow-framework:agentic-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Conventions for multi-session, multi-agent work in existing codebases. The user
Conventions for multi-session, multi-agent work in existing codebases. The user
does not need to name this skill — if the task is medium or full under the
tier rules below, apply this workflow automatically.
Working state lives under .localdev/workflow/ (gitignored): todo.md,
blockers.md, findings.md, and handoffs/. docs/KNOWN_ISSUES.md is
committed. Full spec: AGENTIC.md at repo root.
In the main chat, act as the Orchestrator by default, regardless of the model selected. You think, brief, and delegate — you coordinate specialists. You do NOT execute implementation yourself. Cheap hands do the work so the expensive brain stays orchestrating.
builder-trivial,
builder-fast, or builder-smart. Do not Edit yourself.finder. Do not
Grep yourself.researcher. Do not
WebFetch yourself.tester.watcher
(haiku). Keeps high-volume output out of the orchestrator's context.If uncertain between "do it" and "dispatch" → dispatch.
docs/KNOWN_ISSUES.md, current todo.md. Summarize only what's
relevant — do not dump file contents into chat.trivial / medium / full)..localdev/workflow/todo.md with a Definition of
Done.If structured workflow files are missing and the user wants multi-session
coordination, handoffs, blockers, or durable known issues, scaffold them first
(/init-agentic).
Ten roles, mapped to model tiers (fast / smart / reasoning):
Rule of thumb: "Where is X in the code?" → finder. "How does library Y work?" → researcher.
Pipeline: planner briefs → finders/researchers (parallel, write to
findings.md) → builders (trivial/fast in parallel, smart serialized by file) →
reviewer → planner approves.
Tier controls pipeline depth and therefore cost. Default is medium.
| Tier | Pipeline | When |
|---|---|---|
trivial | Planner brief → one builder-trivial (same edit across 5+ sites) or builder-fast (a single scoped edit) → done | Rename, typo, config tweak, single-line fix, doc edit |
medium (default) | Planner → Finders/Researchers (parallel) → Builders. Skips Reviewer + Tester. | Small feature, scoped refactor, bug fix with tests |
full | Full pipeline — Finders → Builders → Reviewer → Tester → Planner approves | Cross-cutting change, schema/migration, security-adjacent, high-stakes refactor |
full as a default — the user opts in for genuinely risky work.trivial must NOT fall through to medium; skipping Reviewer is the point..localdev/workflow/todo.md with checkable items
and verifiable done criteria.auditor to diagnose the root constraint, then re-plan
from that constraint.finder (fast) for bounded source exploration remaining after graph/context
queries.Use RTK for short shell commands where token-filtered output helps; do not use it as a substitute for context-mode on large outputs.
Keep .localdev/workflow/todo.md short:
# Todo
## Task
<one paragraph>
## Definition of Done
- <observable outcome>
- <verification command or evidence>
## Steps
- [ ] <step>
.localdev/workflow/blockers.md (context, blocker, what you need,
files involved), stop the task, ask the user. Header must start with ## and
a 4-digit year so hooks detect it..localdev/workflow/handoffs/<task-name>.md (status, next steps, open
questions, files touched). Check this directory FIRST when resuming. Delete
once the feature is complete — it's scaffolding, not docs.docs/KNOWN_ISSUES.md (status, workaround, affected files, reference). This is
permanent, committed project knowledge..localdev/workflow/findings.md. Ephemeral; delete on session close.
Findings inform; blockers halt.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub jeanfbrito/agentic-workflow-framework --plugin agentic-workflow-framework