Step 9 post-merge cleanup is opt-in and easy to miss (session ends after the merge push, manual merge, or interruption). Once PLAN.md is set to Complete, the folder became invisible to the session-start check, so a skipped cleanup orphaned plans/<feature>/ forever.
Add a session-start reconciliation pass in references/resumability-and-abort.md that detects already-merged features whose plan folder still exists (via Status Complete, 'git branch --merged', or a 'Merge feature/<name>' commit) and re-offers the Step 9 cleanup choices. Cross-referenced from SKILL.md (Key Rule #1, workflow-at-a-glance, Step 9 line) and references/final-review-and-merge.md. Rebuilt the feature-planner.skill bundle.
Add a super-intensive, adversarial plan-reviewer agent that runs after the plan
is drafted and BEFORE the approval gate, to catch wasteful or wrong design
before any implementation effort is spent. Verdict can be REDESIGN REQUIRED;
findings are sorted into Critical Gaps (block) vs Suggestions (non-blocking) so
the two never get conflated at the approval gate. It must open the codebase to
verify claims (files exist, "no existing impl" holds, "parallel" phases are
disjoint). Conditional trigger: 4+ phases / Orchestrator / Automated /
security|data-sensitive. Wired into SKILL.md, discovery-and-planning (Step 5.5),
agent-spawning (spawn pattern + opus model profile + cost), and
modes-and-strategies (most valuable in Automated mode, the only human gate).
Review hardening also addressed:
- test-writer derives assertions from acceptance criteria, not the diff, so a
failing test is signal (impl bug) rather than something to "fix" to match
buggy behavior
- early per-phase security/data pass for sensitive phases (not only final review)
- Outstanding Warnings ledger in PLAN.md so non-blocking warnings can't
accumulate invisibly across phases
- Automated-mode global circuit breaker (cost / agent-count cap)
- new `data` domain tag carrying a migration-safety addendum
Bump README Last updated date.
alexei.dolgolyov