using-long-task

Context persistence across multi-session development is managed by persisting project state using artifacts like `feature-list.json` and `task-progress.md`. The Skill automatically routes to the correct phase-specific sub-skill based on the current project state.

A phased workflow for complex software project management guides the AI through distinct project phases: Requirements, Design, Initialization, Development, and Testing. This structured approach ensures tasks are executed systematically across long-term projects.

To start a new software project using long-task orchestration, invoke the Skill at the beginning of a session. It will automatically determine the correct starting phase, such as requirements gathering, and execute the appropriate sub-skill.

Yes, you can use this multi-session workflow for large project initialization. It orchestrates complex software development by managing requirements, design, initialization, work cycles, and system testing specifically for complex projects.

The primary limitation of managing long-term development cycles with persistent artifacts is the strict dependency on structured phase transitions. The workflow requires continuous updates to files like `task-progress.md` to maintain context continuity and ensure correct phase routing.