writing-plans_skill

Overview

This skill creates detailed, executable implementation plans after the brainstorming or design phase. Plans are written so an enthusiastic junior developer with no context can follow them to completion, including tests, file paths, verification commands, and rollback steps.

How this skill works

The skill generates a structured markdown plan saved to a timestamped path and broken into prerequisites, ordered tasks, integration tests, manual verification, and rollback instructions. Each task includes exact file paths, a test-first code snippet, the implementation snippet, and the command to verify expected test output. It also appends a short execution handoff with options for in-session or parallel execution.

When to use it

• After design or architecture decisions are finalized
• When you need a plan that a junior developer can execute end-to-end
• Before handing work to a subagent or another developer
• When tests and verifiable steps are required for delivery
• When you want reproducible rollback and integration steps

Best practices

• Always include exact file paths and complete code for tests and implementation
• Write tests first (RED) and provide the exact command and expected passing output
• Order tasks so each builds on the previous with no forward dependencies
• List prerequisites and environment setup explicitly
• Keep plans DRY and avoid speculative changes — prefer minimal, test-driven changes

Example use cases

• Implement a new API endpoint with unit and integration tests and manual verification steps
• Add a feature toggle with tests, documentation file updates, and rollback instructions
• Migrate a small module with step-by-step tests and verification commands
• Onboard a contributor by giving them a complete, runnable implementation plan they can follow