writing-plans

To turn a software specification into an implementation plan, you provide the spec in plain language and the system decomposes it into concrete, auditable steps. It identifies required files, tests, and documentation, mapping responsibilities across design decisions and code changes.

Task decomposition for multi-step software projects is the process of breaking a spec into small, auditable implementation steps. It maps out specific files to modify, tests to write, and documentation to check before any code is touched.

You generate a plan with file changes by submitting your requirements document for structured processing. The system analyzes the spec and produces a deterministic, task-by-task plan detailing exact file modifications, required tests, and commit-ready changes.

You can use this for product design and project scoping, as well as software engineering. It applies to any multi-step project requiring detailed tasks and file mapping, generating comprehensive plans from plain language or brief descriptions.

The generated implementation plan encourages best practices like TDD, DRY, and YAGNI during plan generation. It structures tasks to align with these principles while organizing required files, tests, and documentation into clear, auditable steps.

Generated implementation plans are saved to a versioned path at docs/superpowers/plans/ to enable traceability. This ensures every required file, test, and documentation item identified during task decomposition remains accessible.