decaf-plan

Plugin decaf-plan from marketplace decaf in alphaleonis/decaf-claude. Commands read from the repo's manifest — 6 days ago.

Skills (13)

• architecture-review

  Explore a codebase for structural and testability improvements — deepening shallow modules, untangling tight coupling — and write up recommendations (RFCs), not code changes. Use when you want to find architecture-level improvements rather than fix specific lines of code.

• breakdown-phase

  Break one phase of a plan into concrete, buildable features, each with a done-checklist. Use when you're about to start a phase and need it decomposed into work items with acceptance criteria.

• capture

  Capture a follow-up idea or task as a work-item draft without interrupting current work. Use to quickly jot down something you think of mid-task so it gets tracked. Works with nibs, GitHub, Azure DevOps, or a Markdown fallback.

• challenge-decision

  Stress-test a decision you're about to make by arguing against it — decompose it into claims/assumptions/constraints, verify each, steel-man the strongest case for the opposite, and return a STAND/REVISE/ESCALATE verdict. Use before committing to architectural choices, technology selection, or trade

• close-out

  Reconcile what was built against what was planned, record decisions and deviations, close the item (a single phase or a whole plan), and file follow-ups for deferred work. Use after finishing a phase or plan to keep planned and actual from drifting apart.

• draft-plan

  Turn a spec into an ordered, phased build plan and create the work-item nibs for it. Use when you have a spec (PRD) and need to break it into vertical-slice phases (tracer bullets) ready to implement.

• draft-spec

  Interview the user and explore the code to write a spec (PRD) — what to build and why. Use when starting a new feature and you need to capture the problem, solution, and requirements before planning how to build it.

• explore-designs

  Generate several radically different designs for a decision — from a single method up to a whole architecture — then compare them and write up the one you choose (the "design it twice" habit). Use when a design choice is open and you want real alternatives before committing.

• grill-me

  Interview the user one decision at a time to stress-test a plan or design until it holds up. Use when you want to pressure-test an idea, find the weak points in a plan, or be grilled on a design before committing to it.

• refine

  Take an under-specified work item and make it actionable — resolve its open questions through a short interview grounded in the code, and give it acceptance criteria. Use on a captured draft, or any item too vague to start on.

• research

  Dig into an unfamiliar problem or technology from several angles and write up what you find. Use before drafting a spec, when the domain, tools, or trade-offs aren't well understood yet.

• resolve-architecture-review

  Walk through architecture-review proposals, designing the interface and writing an RFC for each — one at a time, or with "batch" triage all candidates first, explore the chosen ones together, then review the results. Use after architecture-review to turn its candidates into concrete RFCs.

• resolve-open-questions

  Walk the open questions an autonomous run left behind — decisions it could not make, calls it made that you may reverse, checks only a person can run — one at a time, with what happened, the options and a recommendation for each. Use after auto-deliver ends with an open-questions item.

Subagents (1)

• architect

  Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences

Similar plugins