executing-issues

To execute a GitHub issue from an implementation plan, load the plan file from doc/plans/issues/gi_*.md and process the predefined steps in batches. The execution updates issue statuses through the lifecycle and validates target file references against the plan's acceptance criteria.

Issue execution requires an implementation plan containing Summary, Implementation Steps with checkboxes, Acceptance Criteria, and Testing sections. The plan file must exist at doc/plans/issues/gi_*.md with clear steps and acceptance criteria to enable batch execution and lifecycle management.

Issue lifecycle management tracks status transitions from Draft to In Progress to Complete. During execution, progress is recorded and status changes are propagated to module plans, ensuring consistent tracking across tasks until acceptance criteria are verified.

If plan assumptions are unmet during GitHub issue execution, the process validates references to target files and dependencies, then surfaces questions. This prevents executing flawed steps and ensures the implementation plan aligns with the actual project environment.

Yes, you can track batch execution progress for GitHub issues. The execution process creates a TodoWrite-like record to manage tasks in batches, providing visibility into batch completion and reporting final results after verifying the acceptance criteria.

No, issue execution requires a detailed planning document. The workflow depends on a predefined plan file at doc/plans/issues/gi_*.md containing implementation steps and acceptance criteria to manage the lifecycle and validate task completion.