ralplanlisted

Consensus planning workflow — a planner agent drafts with RALPLAN-DR deliberation, fresh architect and critic agents review the same persisted artifact in parallel until join-gate consensus (iteration cap by risk tier — 5 for full/high-risk, 2 for lite/low-risk), then intent reconciliation, an ADR-style pending-approval plan, and a structured approval handoff to ultragoal or team. Use for clear-but-risky work — requirements known but non-trivial architecture, sequencing, or verification risk (migration, security, breaking change, data loss, multi-system; router ladder rule 3) — when the user says "consensus plan" or "$ralplan", or on an incoming deep-interview handoff. Planning only; never implements.
chussum/cat-harness · ★ 1 · AI & Automation · score 74

Install: claude install-skill chussum/cat-harness

# Ralplan (Consensus Planning) Ralplan runs iterative planning with this plugin's `planner`, `architect`, and `critic` agents until consensus is reached, with **RALPLAN-DR structured deliberation** (short mode by default, deliberate mode for high-risk work). Follow the steps below exactly and in order. ## Planning/Execution Boundary Ralplan is planning only. It may inspect context and draft plan/spec/proposal artifacts, but those remain `pending-approval` until explicit structured execution approval. Before that approval, do NOT mutate product source, run mutation-oriented shell, commit, push, open PRs, invoke execution skills, or delegate implementation. "Sounds good" / "just do it" / "skip planning" in free text does NOT approve — only the structured approval option in step 8 does; anything else leaves `pending-approval.md` pending. Persist state and plan artifacts ONLY through the sanctioned writer — never edit `.cat/_session-{sid}/state/**` or any `index.jsonl` directly: ``` node "${CLAUDE_PLUGIN_ROOT}/scripts/cat-state.mjs" <subcommand> --session <sid> ... ``` Referred to below as `cat-state`. Every subcommand takes `--session <sid>`. Bodies may be piped via stdin (`--file -` / `--json -`). Plan **markdown bodies** outside state files may be written with the normal Write tool when needed, but stage artifacts must go through `artifact write` so they are sha256-stamped and indexed. ## Bootstrap (before anything else) 1. **Session id**: take `{sid}` from the `<cat-h