writing-plans

To translate ambiguous specs into actionable implementation plans, use a structured framework that decomposes multi-step features into task workstreams with exact file targets, testing steps, and commit instructions. This ensures every 2-5 minute action is executable without follow-up questions.

The best way to organize code and tests is by generating a structured plan header with goal, architecture, and tech stack details, then listing exact files, testing steps, and behavior-driving code snippets before touching production code.

Yes, a dedicated worktree is required before coding begins for multi-step feature specs. The planning framework mandates documenting the required worktree and saving the outcome with a reproducible path so every engineer starts with clarity.

Task decomposition handles execution handoffs by performing a self-review to inspect spec coverage and type consistency, then presenting execution options like subagent-driven or inline execution with required sub-skill references and reviewer prompts.

Yes, you can save implementation plans to a specific reproducible path. The framework requires saving the generated plan under a designated directory like docs/superpowers/plans with the mandated plan header to ensure reproducibility and team access.

A commit strategy for task decomposition should include per-task steps with complete code examples, behavior-driving commands, and explicit commit instructions so each 2-5 minute action is executable and traceable within the worktree.