A Claude Code plugin for structured, context-efficient software development. Jump to installation if you're ready to get started.
Philosophy
Accelerator structures development into discrete phases — research, plan, implement — where each phase runs with minimal context and communicates with the next through the filesystem. This design is intentional: by writing research findings, plans, and other artifacts to disk rather than holding them in the conversation, each step stays focused and avoids the quality degradation that comes with large, cluttered context windows.
The result is a development workflow where:
- Each phase has a clear purpose and bounded scope
- The filesystem (specifically the
meta/directory) serves as persistent shared memory between phases and sessions - Subagents handle exploratory work in isolation, returning only summaries to the main context
- Human review happens at the highest-leverage points (research quality and plan quality) before implementation begins
For example, a research phase might read 50 files across a codebase, but only a structured summary is written to disk and passed to the planning phase — keeping the planner focused and accurate.
The Development Loop
The primary workflow is a three-phase loop:
research-codebase → create-plan → implement-plan
↓ ↓ ↓
meta/research/ meta/plans/ checked-off plan
-
Research (
/accelerator:research-codebase "how does auth work?"): Investigate the codebase using parallel subagents. Produces a structured research document inmeta/research/with findings, file references, and architectural context. -
Plan (
/accelerator:create-plan ENG-1234): Build a phased implementation plan informed by research. Produces a plan document inmeta/plans/with specific file changes, success criteria, and testing strategy. The plan is reviewed by the developer before proceeding. -
Implement (
/accelerator:implement-plan @meta/plans/plan.md): Execute the plan phase by phase, checking off success criteria as each phase completes. The plan file serves as both instructions and progress tracker.
Three complementary skills support this loop:
/accelerator:review-plan @meta/plans/plan.md— Review a plan through multiple quality lenses before implementation/accelerator:stress-test-plan @meta/plans/plan.md— Interactively stress-test a plan through adversarial questioning to find issues, inconsistencies, and gaps/accelerator:validate-plan @meta/plans/plan.md— Verify after implementation that the code matches the plan
The meta/ Directory
Every project using Accelerator gets a meta/ directory (by default) that
serves as persistent state for the development workflow. Each skill reads from
and writes to predictable paths within it. Run /accelerator:init to
create all directories up front, or let skills create them on first use.
These paths can be overridden via the paths configuration section:
| Directory | Purpose | Written by |
|---|---|---|
research/ | Research findings with YAML frontmatter | research-codebase |
plans/ | Implementation plans with phased changes | create-plan |
decisions/ | Architecture decision records (ADRs) | create-adr, extract-adrs, review-adr |
reviews/ | Review summaries and per-lens results | review-pr, review-plan |
validations/ | Plan validation reports | validate-plan |
prs/ | PR descriptions | describe-pr |
templates/ | Reusable templates (e.g., PR descriptions) | manual |
tickets/ | Ticket files referenced by planning | manual |
notes/ | Notes and working documents | manual |
tmp/ | Ephemeral working data (e.g., review artifacts) | review-pr |
This approach means: