build-planlisted

HETS-aware planning for multi-file substantive work. Wraps the planner agent with route-decide gating (Step 0) and architect-spawn recommendation (Step 3) when convergence_value ≥ 0.10. Invoke via /build-plan or implicitly when plan mode is entered for substantive multi-file work. Additive to /plan — does not replace it.
shashankcm95/claude-power-loom · ★ 1 · Web & Frontend · score 80

Install: claude install-skill shashankcm95/claude-power-loom

# build-plan — HETS-aware plan authoring ## Why this skill exists Phases H.7.5/7.6/7.7/7.8 demonstrated a recurring drift: root-direct skipped plan-mode + route-decide gate + HETS architect spawn for multi-file substantive work, even when those gates would have caught real defects. Mira's H.7.7+H.7.8 retrospective surfaced 3 CRITICAL + 2 HIGH bugs traceable to this drift. The discipline existed in `rules/core/workflow.md:28-44` as a soft norm, but soft norms drift. This skill converts the soft norm into a sharper gate by: 1. Running `route-decide.js` deterministically before any planning happens (Step 0) 2. Recommending architect spawn when `convergence_value ≥ 0.10` (Step 3) 3. Producing plans that conform to `swarm/plan-template.md` schema (Step 4) 4. Preserving user authority at the final gate (Step 5) ## Steps ### 1. Route-decide gate Invoke `node ~/Documents/claude-toolkit/scripts/agent-team/route-decide.js --task "$TASK"` (with `--context` on continuations). Decision matrix: - `route` → continue silently (HETS-aware planning warranted) - `borderline` → surface decomposition to user; let them pick `/build-plan` vs `/plan` vs cancel - `root` → recommend `/plan` instead; do not proceed (escape: `--force-plan`) - `[ROUTE-DECISION-UNCERTAIN]` → re-invoke with `--context` or surface for explicit user choice ### 2. Phase 1 — Reconnaissance (Explore agents) Per plan-mode workflow Phase 1: launch up to 3 Explore agents in parallel. Each gets a specific search focus. Rea