Full Workflow

Accelerator is a toolkit, not a fixed pipeline. The skills are designed to fit together end to end — from capturing work through to shipping a PR — but you pick the parts you need. A bug fix might be research-issue → create-plan → implement-plan; a larger feature might run the whole map below.

The spine is the Development Loop — research → plan → implement. The other families attach to it: some feed work in before research, others capture decisions along the way and land the change after.

The spine, end to end

Taken end to end, a full pass runs research → plan → implement → review → commit → PR. Each solid arrow is a hand-off through a document in meta/, not through the conversation:

The review boxes are deliberate pauses: plan review happens before any code exists (the cheapest point to change course), and PR review closes the loop after the change lands on a branch.

The full map

Each box below is a skill family from All skills.

How the families fit together

Each heading below is a skill family from All skills. They are ordered by where they sit relative to the spine — what feeds work in, the loop itself, and what lands the result.

Work Items, Issue Trackers & Design Convergence — what gets worked on. Work items are the unit of work. They can be created locally, or synced both ways with a remote issue tracker (Jira or Linear). Design convergence feeds the funnel from the other side: it inventories a frontend, analyses gaps, and emits a document that extract-work-items turns into work items.

Investigation & Notes — understand before planning. Two skills feed the loop ahead of research when needed: research-issue for hypothesis-driven bug investigation, and conduct-spike for time-boxed uncertainty reduction. create-note captures observations at any point.

Development Loop — the spine. The loop opens with research-codebase, which investigates the code and writes a structured findings document. create-plan builds a phased plan from that research; review-plan and stress-test-plan iterate on its quality before any code is written; implement-plan executes it phase by phase; validate-plan confirms the result matches the plan. See the Development Loop for detail.

Architecture Decision Records — captured as you go. ADRs record architectural decisions made during planning or implementation; extract-adrs pulls them out of existing research and plan documents.

VCS & PR — land the change. The VCS & PR workflow closes the loop: commit through implementation, then describe-pr, review-pr, and respond-to-pr to get the change reviewed and merged.

Every skill reads and writes the shared meta/ directory, so phases hand off through the filesystem rather than the conversation. For the complete catalogue, see All skills.