LennardZuendorf
UserA framework of framework for a spec driven AI SLDC with claude code.
Categories
Indexed Skills (8)
spec
Maintain `.spec/` design docs across two layers: long-living root specs (`product.md`, `tech.md`, `design.md`, `plan.md`, `lessons.md`, branch docs) and ephemeral per-feature folders under `features/<name>/` that merge to root then archive. Read before code. Trigger on: scoping a feature, bootstrapping strategy, reviewing architecture, updating a spec, validating consistency, or user says spec, PRD, design doc, tech design, feature spec, branch doc.
vibe-feature
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.
vibe-setup
Install or repair the vibe workflow harness in a repo. Read-only audit (detect) then write/merge bootstrap (apply) — never clobbers existing content. Writes the constitution block, scaffolds .agents/flow + .spec, preflights required plugins. Trigger on: set up vibe, bootstrap the harness, repair the workflow, install, onboard a repo, or user says setup.
vibe-amend
Correct the scope of the work in flight without leaving the current state. A modifier, not a flow: edits the target state's spec surface, then returns there. Trigger on: amend scope, adjust the plan, revise the spec mid-flight, scope changed, that's not quite right, or user says amend.
vibe-compound
Consolidate at end of work: record tagged lessons, promote cross-cutting decisions into root specs, archive the feature, regenerate the active-rules digest. Serves feature.compound and strategy.compound. Trigger on: compound, wrap up, record lessons, finish the branch, promote to specs, archive feature.
vibe-quick
Small bounded fixes — the low-ceremony escape valve. triage → fix → verify. Writes src/ plus an optional .spec/quick/<slug>.md note. No feature specs. Trigger on: quick fix, bug, small change, tweak, patch, maintenance, or user says quick. If scope balloons, escalate to vibe-feature.
vibe-strategy
Set or refocus project direction: brainstorm, then write the root .spec docs (product/tech/design/plan). The strategy flow — no source code. Trigger on: project direction, strategy, roadmap, "what should we build", refocus, rewrite product/tech/design/plan, or user says strategy.
vibe-verify
Gather evidence before calling work done: run tests/build, request review, debug failures. Used by feature.verify and quick.verify. Writes no specs — produces evidence and routing. Trigger on: verify, prove it works, check the change, evidence before done, pre-ship review, or user says verify.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.