writing-plans

Writing Plans

Write comprehensive implementation plans assuming the engineer has zero codebase context and questionable taste. Exact file paths. Complete code. Expected output at each step. DRY. YAGNI. TDD. Frequent commits.

Announce: "Using writing-plans to create the implementation plan."

Save to: docs/superskills/plans/YYYY-MM-DD-<feature-name>.md

---

Pre-Check

Confirm audit-design Gate Result is PASS or PASS WITH FLAGS before starting. If Gate Result = HOLD → return to brainstorming. Do not write a plan for an unapproved design.

---

DPS Section 8 Check

# Check if DPS has build order:
grep -c "PHASE 0" .dps/spec/BLUEPRINT.md 2>/dev/null | xargs echo "DPS phases defined:"

If DPS APPROVED-SSOT AND Section 8 has phases filled: → Import phase/task structure from BLUEPRINT Section 8 → Plan document: add header > Build order imported from DPS BLUEPRINT §8 → Do NOT create new build order — work within DPS phases

If DPS APPROVED-SSOT AND Section 8 is empty/template: → Generate plan as normal → Write phase/task structure BACK to BLUEPRINT Section 8 → Commit: git commit -m "dps: populate BLUEPRINT §8 build order [writing-plans]"

If DPS NOT PRESENT: → Standard behavior (unchanged)

---

Scope Check

If spec covers multiple independent subsystems → suggest splitting into separate plans. Each plan produces working, testable software on its own.

---

File Structure

Before defining tasks, map which files are created/modified and each one's responsibility.

• One clear responsibility per file
• Files that change together should live together
• Follow existing patterns in existing codebases

---

Task Granularity (2–5 min each)

"Write the failing test"           — step
"Run it, confirm it fails"         — step
"Write minimal implementation"     — step
"Run tests, confirm pass"          — step
"Commit"                           — step

---

Plan Document Header

# [Feature Name] Implementation Plan

> **For agentic workers:** Use `subagent-driven-development` (recommended)
> or `executing-plans` to implement this plan task-by-task.

**Goal:** [One sentence]
**Architecture:** [2-3 sentences]
**Tech Stack:** [Key technologies]
**Audit Gate:** [PASS | PASS WITH FLAGS — from audit-design]
**Risk Flags:** [HIGH tasks from task-risk-score, or "none"]

---