softhouse-planlisted

Planning-only phase of the Softhouse pipeline — breaks a requirement into a reviewable task graph with executor routing, dependencies, and model assignments, writes it to .softhouse/tasks.json, and stops. Never spawns worker agents or modifies source code. Use when the user runs /softhouse-plan or wants to review a pipeline plan before executing it with /softhouse resume.
buya-v/claude-softhouse · ★ 0 · AI & Automation · score 70

Install: claude install-skill buya-v/claude-softhouse

# /softhouse-plan — Plan Only (No Execution) (v2)  **PIPELINE VERSION: `2.2`** — must match `/softhouse`'s version exactly. These two skills share one schema; if they disagree, a plan written here will not execute correctly there. Runs only the planning phase of the Softhouse pipeline (Steps 0-2) without executing any tasks. Use this to review and refine the task graph before committing to execution. Schema and rules are IDENTICAL to `/softhouse` STEP 2 (v2) — a plan written here must execute unmodified under `/softhouse resume`. ## Usage - `/softhouse-plan <requirement>` — Generate a task plan ## Steps ### STEP 0 — Pre-flight 1. Run `git status` — abort if working tree is dirty. 1b. **Pipeline-version check** — read `.softhouse/pipeline.json` and apply the SAME rules as `/softhouse` STEP 0: missing → pin at the current version and say so; major mismatch → stop and ask the user to adopt; minor mismatch → warn, re-pin, continue; pinned newer than the skill → warn and ask. A plan must be written by the same pipeline version that will execute it, or `/softhouse resume` will reject it. 2. Read `CLAUDE.md` (or project context file) if it exists. 3. Read `.softhouse/patterns.md` for learned patterns. 4. Read `.softhouse/tasks.json` — check current state. If a run is already IN PROGRESS (any task `in_progress`), warn the user. If the previous run is terminal (all tasks done/approved/deferred/cancelled), it is safe to replace — archive it