i9wa4 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.
This skill owns planning semantics and evidence expectations, not artifact storage or delivery mechanics. Leave a durable artifact of your work; where and how it is created, reused, discovered, and delivered is governed elsewhere in this environment.
Follow the output language designated by the active runtime/session policy or explicit request. Do not establish an independent language policy in this skill.
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-conceptsbefore 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
- Plan Authoring
- Brainstorming
- Durable Task Tracking