bx-plan-writer

Implementation plan generation transforms a project spec into a structured, task-level plan. It breaks down requirements into bite-sized tasks across code, tests, and docs, including specific files to touch and testing instructions for engineers with zero codebase context.

Task breakdown divides multi-step software development requirements into deterministic, bite-sized deliverables. You need it when teams require repeatable plan generation from product specs, ensuring clear deliverables and traceable planning artifacts for engineers lacking project context.

Spec-to-plan generation applies to multi-step tasks across code, tests, docs, and project planning. It documents everything engineers need to check, satisfying requirements for deterministic task breakdown and cross-cutting risk highlighting alongside needed references and prerequisites.

Implementation plan generation produces collaboration-friendly docs by saving plans to a predictable path for sharing with teams. It identifies cross-cutting risks and prerequisites, ensuring repeatable plan generation that provides traceable planning artifacts for the entire team.

To ensure engineers follow an implementation plan without codebase context, generate a plan that documents everything needed: which files to touch for each task, code, testing, and docs to check. It provides bite-sized tasks following DRY, YAGNI, and frequent commits principles.

Risk and dependency highlighting identifies cross-cutting risks, needed references, and prerequisites during project plan creation. It transforms product specs into structured implementation plans, ensuring engineers understand all dependencies before starting their assigned bite-sized tasks.