executing-plans

You can execute a development plan in a controlled session with per-task status updates like in_progress and completed. This approach maintains task tracking and alignment through built-in review checkpoints across iterative work cycles.

Reviewing an implementation plan requires a loading step to critically identify gaps before execution. This ensures the development workflow maintains quality and alignment through built-in verifications across all planned tasks.

Yes, plan execution supports optional integration with sub-skills for git workflows. This allows you to coordinate development tasks and verifications directly alongside git operations during the implementation cycle.

You verify completed tasks by using built-in verifications configured for each item in the implementation plan. The session tracks task status updates and reports verifications across iterative work cycles to ensure quality.

Yes, a structured written plan is required as input to load and critically review before execution. The guided session uses this plan to track per-task status updates and apply verifications across the development workflow.

Yes, the execution session coordinates with related workflow skills to finish a development branch. This provides complete implementations by integrating task verifications with release finalization steps.