vibe-featurelisted

Design and build a named feature end to end: design → plan → impl → verify → compound. The main build loop. Writes feature specs under .spec/features/<name>/ then source under src/ and tests/. Trigger on: building a feature, "I need <feature>", implement, add capability, feature work, or user says feature.
LennardZuendorf/vibe · ★ 0 · AI & Automation · score 68

Install: claude install-skill LennardZuendorf/vibe

# vibe-feature — build loop Carries a named feature from spec to verified code. Five states with **two human gates**: after `plan` (before impl) and after `verify` (before ship/compound). Everything between is autonomous. `feature.design → feature.plan →[gate] feature.impl → feature.verify →[gate] (feature.compound | feature.impl | feature.plan)` ## Procedure 1. **Locate + name.** Read `.agents/flow/state.json`. Establish the feature name and set it: `bash .agents/flow/scripts/set-state.sh feature.design <name>`. The name is carried in the cursor across all feature states. 2. **Design** (`feature.design`, caveman lite). Read `.spec/lessons.md` first. Delegate to `superpowers:brainstorming` for the human dialogue, plus the `code-explorer` subagent to trace the codebase and `code-architect` to sketch approaches — they compose, they do not compete. Write **only** `.spec/features/<name>/product.md` and `tech.md` (inject those exact paths). Suggest `feature.plan` when the approach is chosen. 3. **Plan** (`feature.plan`, caveman lite). Delegate to `superpowers:writing-plans` + `code-architect`. Write `.spec/features/<name>/plan.md`. Give every implementation unit a **stable ID** (`U1`, `U2`, …); IDs never change on reorder or split. **Human gate:** confirm the plan before moving to impl. 4. **Impl** (`feature.impl`, caveman full). Delegate to `superpowers:executing-plans` + `superpowers:test-driven-development`. Write `src/**` and `tests/*