| name | plan-design |
| license | MIT |
| metadata | {"version":"1.0.0"} |
| description | USE FOR: Implementation plans and durable task tracking: reduce ambiguity, compare options, parallel investigation, multi-source synthesis, review gates, task artifacts, evidence logs, handoff/resume, and DONE/BLOCKED verification. DO NOT USE FOR: unrelated tasks, broad rewrites outside the request, or generated runtime outputs.
|
Plan Design
Owns implementation-plan authoring and durable task tracking for plan-ready
tasks: ambiguity reduction, option framing, multi-source synthesis, review
gates, task artifacts, evidence logs, and handoff/resume.
1. Workflow
- Inspect the relevant files, current repo conventions, and
git status.
- Read Plan Authoring before changing
behavior or giving detailed instructions.
- If the task is fuzzy or has multiple viable approaches, read
Brainstorming and stabilize the direction
before drafting the execution plan.
- If plan terms, states, conditions, cause categories, or mitigation names are
ambiguous, use
clarify-concepts before the plan language hardens.
- Make the smallest scoped change that satisfies the request.
- Run the checks named in the plan authoring guide or the nearest repo
harness.
- Report verification results and any remaining risk.
2. References
