Writing Plans

Overview

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.

Announce at start: "I'm using the writing-plans skill to create the implementation plan."

Context: If working in an isolated worktree, it should have been created via the solopowers-using-git-worktrees skill at execution time.

Save plans to: a SoloTerm project scratchpad named solopowers/plans/YYYY-MM-DD-<feature-name>

• (User preferences for scratchpad name or destination override this default)
• Do not write or commit a repo Markdown file by default. If the user wants the scratchpad persisted to Git later, use the solopowers-commit-scratchpad skill.

Scope Check

If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.