technical-planning

To turn a written specification into a structured software development plan, you provide the spec path to generate phases, detailed tasks, acceptance criteria, and dependency maps. The plan artifacts are then output directly under docs/workflow/planning.

Task traceability in software planning maps generated tasks back to the original specification to ensure full coverage of validated decisions. This is achieved by authoring detailed task descriptions that can be independently tested and explicitly traced to spec requirements.

Adding approval gates to a phased project plan involves enforcing explicit approvals before progressing through steps. This plan governance ensures alignment with the specification by requiring validation at each milestone before subsequent tasks begin.

Yes, you can generate a phased plan directly from inline context instead of a full specification file. The skill processes either a full specification path or provided inline context to produce phases, tasks, and dependencies.

Mapping task dependencies and execution order requires analyzing and recording task relationships within the plan. This process identifies dependencies and priority execution order to prevent cycles and ambiguity during software delivery.

The best way to structure milestones and acceptance criteria for a software specification is to break the spec into a phased plan with clear milestones. Each phase generates detailed task descriptions with specific acceptance criteria for independent testing.