soleri-writing-planslisted

# Writing Plans Write implementation plans assuming the engineer has zero codebase context. Document everything: which files to touch, code, testing, expected output. Bite-sized tasks. DRY. YAGNI. TDD. Frequent commits. **Announce at start:** "I'm using the writing-plans skill to create the implementation plan." **Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md` ## Before Writing — Search First ### 1. Vault First ``` YOUR_AGENT_core op:memory_search params: { query: "<plan topic>", crossProject: true } ``` ``` YOUR_AGENT_core op:search_intelligent params: { query: "<feature being planned>" } YOUR_AGENT_core op:brain_strengths YOUR_AGENT_core op:vault_domains YOUR_AGENT_core op:vault_tags ``` ### 2. Web Search Second If vault lacks guidance: libraries, reference implementations, API docs, known pitfalls. ### 3. Then Write the Plan Incorporate vault insights and web findings. Reference specific entries. ## Create a Tracked Plan ``` YOUR_AGENT_core op:create_plan params: { objective: "<one-sentence goal>", scope: "<which parts of the codebase are affected>", tasks: [{ title: "Step 1", description: "details" }], alternatives: [ { approach: "<rejected approach>", pros: ["advantage 1", "advantage 2"], cons: ["disadvantage 1", "disadvantage 2"], rejected_reason: "<why this approach was not chosen>" } ] } ``` **Always include 2+ alternatives.** The grader (Pass 8) checks `plan.alternatives