Phase Tracking Skill

Multi-phase feature implementation tracking requires parsing feature documents for phase markers to maintain detailed status reports. This approach identifies blockers, generates phased backlogs, and manages phase transition criteria to ensure comprehensive feature development lifecycle completion.

Agile development projects often neglect Phase 2 tasks because there is no systematic phase management tracking continuous progress. Without parsing feature documents for phase markers and generating automatic Phase 2 backlogs upon Phase 1 completion, subsequent items are easily forgotten.

To generate phase transition checklists for feature tracking, the system parses defined markers in feature documents and evaluates transition conditions. This ensures all prerequisites are met before moving from Phase 1 to Phase 2, providing clear visibility into the feature lifecycle.

Yes, you can use markdown feature documents for automated phase management by defining specific phase markers within the files. The system automatically detects and categorizes feature items into Phase 1, Phase 1.5, Phase 2, etc., based on these defined markers to maintain status tracking.

The best way to manage blockers across feature development phases is to maintain a clear overview of total, complete, in-progress, and blocked items for each phase. This systematic tracking identifies specific blockers and generates concise progress reports highlighting critical issues.

Yes, you need to manually define phase markers in your feature documents for backlog generation to work. The system automatically creates Phase 2 backlogs when Phase 1 is completed by parsing these defined markers, prioritizing items based on dependencies and impact.