repo-harness-autoplan

# repo-harness-autoplan Use this command when the user wants the whole repo-harness workflow handled automatically. ## Protocol 1. Confirm the working repo and inspect state with `bun scripts/inspect-project-state.ts --repo <repo> --format text` when available. 2. Draft the action plan with `repo-harness-plan` rules. 3. Run self-review 1, the completeness pass: goal, scope, P1/P2/P3, interfaces, tests, rollback, no placeholders. 4. Revise the plan once from the completeness findings. 5. Run self-review 2, the adversarial and shipability pass: failing gates, unsafe automation, permission boundaries, 10x breakpoints, and PR closeout readiness. 6. Execute the approved plan without re-litigating decisions unless live repo drift makes it unsafe. 7. Run Waza `/check` semantics and record the sprint review, external acceptance, and `verify-sprint` evidence. 8. Call `repo-harness-ship` for the final default PR closeout. ## Reusable Workflow Packaging Rubric When the user wants to package repeated work into a skill, subagent, automation, or existing command extension: 1. Build a compact shortlist before recommending creation. 2. Use evidence in this order: current repo docs and task files, recent sessions or task summaries, Memories and rollout summaries, Chronicle for discovery only, then existing skills, custom agents, and automations. 3. For each candidate, report the repeated workflow, evidence and dates, frequency/confidence, recommended form, and why to create, ex...