task-generator

Converting a project plan into atomic git commits requires generating independent TASK-FASE-*.md documents from plan artifacts. This maps each phase into concrete work items with conventional commit messages and dependency graphs for end-to-end traceability.

Phase decomposition for task generation breaks down FASE plan artifacts into atomic, auditable work items. It ensures traceability by linking each generated TASK-FASE-*.md file back to the original plan, FASE, and specifications for complete provenance.

Yes, you can generate tasks for a single phase by running the generator with a specific phase flag. This regenerates only the targeted TASK-FASE-*.md document, allowing per-FASE execution without affecting other atomic tasks.

Yes, the generated task output includes revert strategies for git workflows. Along with conventional commit messages and review checklists, these reversible tasks provide governance and rollback planning for human review.

Plan to tasks conversion requires plan/PLAN-FASE-*.md and plan/fases/FASE-*.md artifacts as input. The generator outputs TASK-FASE-*.md, TASK-INDEX.md, and TASK-ORDER.md documents into a task/ directory, while reading optional scripts/ and references/ directories to enrich tasks.

You should not use automated task generation from plan artifacts when your project lacks structured FASE and plan markdown files. The generator depends on these specific input formats to produce traceable, atomic work items and validate outputs against governance checks.