Writing Plans

Overview

Thinking budget: Use Medium thinking by default to stay grounded in reading real code, lockfiles, and schemas rather than speculating. Bump to HIGH thinking only when architecting net-new subsystems, complex distributed state machines, or zero-downtime database migrations.

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

Assume they are a skilled developer who knows almost nothing about our toolset or problem domain, and does not know good test design well.

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

Context: run this in a dedicated worktree (created by the brainstorming skill).