featurelisted

End-to-end feature workflow around the agent — spec by interview, a plan of 2–5-minute tasks, test-first execution with checkpoint commits, then an evidence-gated finish. Effort-scaled: a one-sentence diff skips straight to implementation; a real feature gets spec.md → plan.md → task-by-task TDD, with all state in out/dev/<change>/ so any later session resumes at the first unchecked task. Human-in-the-loop: the spec and the plan are approved (and editable) before any code is written, and nothing ships without the done gate. Use when the user wants to build, add, or implement a feature or start non-trivial coding work — e.g. "/feature add rate limiting", "implement X", "build a Y that Z", "resume the <change> feature". For fixing something broken use bugfix; for just the end-of-session shipping gate use done; for this whole loop end-to-end without approval stops, suggest the user run /autopilot (explicit invocation only).
duthaho/skillhub · ★ 6 · Code & Development · score 75

Install: claude install-skill duthaho/skillhub

# feature — spec → plan → build, effort-scaled `/feature <description>` — start (or resume) a piece of work `/feature` — list changes in flight under `out/dev/` Answer one question: **what is the smallest process that gets THIS change built correctly?** The two documented failure modes of workflow suites are opposite: heavyweight gates firing on typo-sized changes, and freestyle sessions shipping unverified scope creep. This skill scales the process to the change — never the other way around. ## Step 0 — Size the change (the escape hatch comes first) Classify before doing anything else, and say which tier you picked: - **Trivial** — you could describe the exact diff in one sentence (typo, rename, config value, one-line fix). → No spec, no plan, no folder. Make the change, then run the **done** gate's evidence checklist inline. Stop here. - **Small** — one focused change, ≤ ~3 files, design obvious. → Skip the spec interview; write the plan directly **in chat** for approval, execute with the Step 3 rules, finish with **done**. No folder unless the user wants to pause and resume. - **Standard** — anything multi-file, multi-session, or with real design decisions. → Full loop below. If the user explicitly asks for the full treatment ("spec this out"), honor it regardless of size. When genuinely unsure between tiers, pick the smaller one and say so — the plan contract (Step 3) catches scope growth and upgrades the tier if needed. ## The change folder — state acr