incremental-planning

You can plan multi-file coding tasks with issue tracking by replacing native plan mode with an incremental planning workflow that writes structured plan content to files and cross-references BUGS.md to surface tracked issues. It prompts clarifying questions and records work in a structured plan tree.

Incremental planning is an iterative, file-backed workflow that replaces monolithic planning by capturing decisions, questions, and assumptions. It improves project management by applying phase-based execution with per-task quality reviews, tiered breakpoints, and assumption surfacing for continuous traceability across phases.

Yes, incremental planning works with GitHub and Jira for issue tracking integration. It aligns planning with ticketing workflows and tracks cross-references to open bugs via BUGS.md to maintain continuous traceability across project phases.

The best way to track open bugs during multi-file project planning is to cross-reference a BUGS.md file within your structured plan tree. This surfaces tracked issues continuously across phases and aligns them with external ticketing workflows from GitHub or Jira.

Yes, you can use a file-based plan tree instead of native plan mode for complex workflows. It applies when asked to plan across multi-file tasks, prompting clarifying questions first and recording work in a structured plan directory with phase-based execution support.

You should not use incremental planning for simple, single-file tasks that do not require phase-based execution or external issue tracking. It is designed for multi-file tasks needing clarifying questions, assumption surfacing, and cross-referenced bug tracking.