writing-plans

Topics in the source

• Writing Plans
• Overview
• Bite-Sized Task Granularity
• Plan Document Header
• Task Structure
• Remember
• Execution Handoff

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: This should be run in a dedicated worktree (created by brainstorming skill). Save plans to: docs/plans/YYYY-MM-DD- .md Each step is one action (2-5 minutes): "Write the failing test" - step "Run it to make sure it fails" - step "Implement the minimal code to make the test pass" - step "Run the tests and make sure they pass" - step "Commit" - step Every plan MUST start with this header: Step 2: Run test to verify it fails Run: pytest tests/path/test.py::testname -v Expected: FAIL with "function not defined" Step 3: Write minimal implementation Step 4: Run test to verify it passes Run: pytest tests/path/test

This is an excerpt. Refer to the complete source and its current requirements.