accelerator

A Claude Code plugin for structured, context-efficient software development.

Getting Started

Add the marketplace and install the stable plugin:

/plugin marketplace add atomicinnovation/accelerator
/plugin install accelerator@atomic-innovation

Then initialise your project and run the research → plan → implement loop:

/accelerator:init
/accelerator:research-codebase "how does auth work?"   # 1. research
/accelerator:create-plan                               # 2. plan (optionally pass a work-item key)
/accelerator:implement-plan                            # 3. implement

See the Development Loop for the full workflow, and Installation for the prerelease channel (where the newest features land first), local checkout, and compatibility details.

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/codebase/ meta/plans/    checked-off plan

1. Research (/accelerator:research-codebase "how does auth work?"): Investigate the codebase using parallel subagents. Produces a structured research document in meta/research/codebase/ with findings, file references, and architectural context.

2. Plan (/accelerator:create-plan ENG-1234): Build a phased implementation plan informed by research. Produces a plan document in meta/plans/ with specific file changes, success criteria, and testing strategy. The plan is reviewed by the developer before proceeding.

3. 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.

Companion skills handle issue investigation and quick note capture:

• /accelerator:research-issue "auth timeout on token refresh" — Investigate production issues through hypothesis-driven debugging. Accepts stacktraces, logs, or behavioral descriptions and produces an RCA document in meta/research/issues/.
• /accelerator:create-note "rate limiter resets on deploy" — Capture a short-form note (observation, insight, snippet) to meta/notes/.

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: