phase-breakdown

To break down a project phase into developer tasks, analyze the phase specification, related specs, and deliverables to produce a prioritized, actionable task plan. This enforces safe task generation with an approval gate before creating files.

Phase management in dotnet project planning is the process of translating a phase specification into concrete developer tasks. It involves parsing phase identifiers, generating task breakdowns, and enforcing an approval workflow for safe task creation.

Yes, you can validate or refresh a generated task breakdown by passing flags like --validate or --refresh with the phase identifier. This updates the task plan against the current phase scope, dependencies, and related specs.

Yes, the dotnet-tech-lead workflow requires an approval step. It prepares a task summary for user approval before creating any files, enforcing guardrails to prevent unintended file changes and ensure complete task coverage.

To normalize phase identifiers when generating a task plan, input variations like 03, 3, or phase-03 are automatically extracted and normalized. This ensures the system correctly aligns the generated tasks with the intended phase scope.

Automated phase breakdown limitations include strict guardrails that prevent unintended file changes and an enforced approval gate. Task generation derives concrete tasks from related specs rather than duplicating content, ensuring safe, auditable outputs.