← ClaudeAtlas

aih-planlisted

Research a problem and produce a plan without writing code. Use when you want to think before building.
overdrive-dev/aihaus-flow · ★ 4 · AI & Automation · score 80
Install: claude install-skill overdrive-dev/aihaus-flow
## Task Research `$ARGUMENTS` and produce a detailed plan at `.aihaus/plans/[slug]/PLAN.md`. No code changes. ## Phase 0 — --from-brainstorm seeding (conditional) If `$ARGUMENTS` contains `--from-brainstorm <slug>`, follow `annexes/from-brainstorm.md` before Phase 1. Else skip. ## Phase 1 — Capture + clarify 1. **Silent context load:** `.aihaus/memory/MEMORY.md`, `.aihaus/project.md`, `.aihaus/decisions.md`, `.aihaus/knowledge.md`. 2. **Parallel evidence gathering** — in a single message, spawn **both** `assumptions-analyzer` AND `pattern-mapper` as concurrent Agent calls. assumptions-analyzer writes `.aihaus/plans/[slug]/ASSUMPTIONS.md` (evidence-tagged findings, blocker flags); pattern-mapper writes `.aihaus/plans/[slug]/PATTERNS.md` (concrete codebase analogs with file excerpts). Wait for both to return before Step 3. Rationale: pattern context informs which clarifying question matters most, so combining the spawns avoids serial wallclock cost AND makes Step 3 evidence-driven. (Replaces former Phase 2 Step 6 — pattern-mapping is no longer a separate phase.) 3. **Clarify (conditional)** — default position is **proceed**. Ask only when ≥2 dimensions are genuinely missing AND the missing info materially changes the plan. Dimensions: (i) goal/intent, (ii) constraint/deadline, (iii) scope hint (bugfix vs feature vs milestone), (iv) attachment context. Heuristic: if `$ARGUMENTS` includes a specific file/function/path OR references an attachment OR is a well-formed "I want X be