plan-itlisted

# plan-it Personal workflow for turning "let's build a feature" into a milestone and a reviewed, drafted set of GitHub issues. The methodology — classify, scope, reconcile design, draft, review, sequence, create — is portable across GitHub-based projects; each consuming project supplies its own stack conventions inside that shape. See `README.md` for the plain-English walkthrough and reasoning. ## Two work origins - **Planned work** — starts from an intentional proposed change, not an unexpected finding. A feature ask in conversation enters the pipeline below at classification (step 2) and still requires scope discovery; an approved `plan.md` section (`rules/plan-md-input.md`) enters at step 1 with its architecture and decisions already canonical. Both are the same Planned-work origin. - **Discovered work** — starts from an unexpected finding (implementation, code review, manual testing, production/debugging, another workflow) with scope not yet known. Runs `rules/discovered-work.md`'s investigation first; only a validated finding enters the pipeline. Both origins converge on the same canonical-issue pipeline and the same review bar — Discovered work never gets a lighter-weight issue. ## Pipeline 1. Consume an approved `plan.md` input when one exists (`rules/plan-md-input.md`); otherwise skip to classification. 2. Classify the feature — resource/CRUD, cross-cutting capability, extension, or refactor (`rules/feature-classification.md`). 3. Load the matchi