issue-workflow

GitHub issue-driven workflow uses issues as your single source of truth for planning, progress tracking, and task selection. Pull active epic context to identify next tasks, score them for complexity, and route work to appropriate action based on blockers and dependencies.

Structure work by pulling active epic context and recent learnings, then identify next tasks from your build order. Close completed sub-issues to keep progress transparent and update epic checklists as work advances through planning and implementation phases.

Score tasks for complexity while examining issue context for blockers and dependencies. This routing determines whether work needs plan mode for high-impact decisions or direct implementation, ensuring disciplined task selection and progress updates.

Yes. GitHub issue-driven workflow consolidates coordination and status-tracking by enforcing a single source of truth. Use it for managing work priorities, checking project status, updating progress, and maintaining transparency through closed sub-issues and updated epic checklists.

Score task complexity and examine blockers identified in issue context. High-impact work or tasks with significant dependencies route to plan mode for upfront design; straightforward tasks with no blockers move to direct implementation.

Closing completed sub-issues maintains transparency and enforces discipline around work completion. It keeps epic checklists accurate and ensures your GitHub issues remain a reliable single source of truth for current project state and progress tracking.