← ClaudeAtlas

aih-featurelisted

Implement a scoped feature — plan, branch, build, test, commit. Use for changes that fit in one session.
overdrive-dev/aihaus-flow · ★ 4 · AI & Automation · score 80
Install: claude install-skill overdrive-dev/aihaus-flow
## Task Implement a scoped feature end-to-end: understand, plan, get approval, branch, build, test, review, commit. $ARGUMENTS ## --plan Flag (optional) If `$ARGUMENTS` contains `--plan`, extract the word immediately after `--plan` as the **slug**. 1. **Attempt to read** `.aihaus/plans/[slug]/PLAN.md`. 2. **If the file exists** AND has no unresolved `## Open Questions` section (or the section is empty): **skip Phase 1 entirely** — do NOT re-ask scoping questions, do NOT issue Step 5 "STOP HERE". The plan contains the approved analysis. Dispatch to Phase 2 immediately. - Emit a single 3-bullet pre-flight summary before Phase 2: (PLAN.md slug, Affected Files count, Estimated Scope). No interactive acknowledgment needed. - Carry the plan's "Affected Files" list as the authoritative scope for Phase 2. Do not re-scan the codebase. - In the Phase 2 RUN-MANIFEST progress log, note: "Using plan: `.aihaus/plans/[slug]/PLAN.md` — Phase 1 short-circuited." 3. **If the file exists** BUT contains an `## Open Questions` section with unresolved items: fall back to the full Phase 1 below — the plan is incomplete and needs scoping input before execution. 4. **If the file does not exist**, report this error and **stop**: > "Plan not found at `.aihaus/plans/[slug]/PLAN.md`. Run `/aih-plan` first to create it." 5. **If no `--plan` flag is present**, proceed normally — all Phase 1 steps below apply in full. ## Phase 1: Understand & Plan (interactive — ask questions, then wait for