quick-devlisted
Install: claude install-skill rterakedis/leanwheel-skills
# Quick Dev Skill
**Goal:** Implement one-off features/bugfixes that follow architecture and keep docs current.
**When:** Post-MVP one-offs where epic/story is overhead. Use full flywheel for large feature areas. For a one-off in a folder with **no** leanwheel docs (`docs/prd.md`/`docs/architecture.md` absent), use `/dev-single-goal` instead — this skill requires both.
## Activation
1. Read `docs/architecture.md` (required constraint document).
2. Read `docs/prd.md` (what exists; don't duplicate/contradict).
3. Read `CLAUDE.md` if exists (project conventions).
4. Identify intent. If unclear: "What should this do, user-facing outcome?"
## Phase 1 — Scope Check
Single goal = one deliverable (cross-layer work OK if serving one goal).
Multi-goal = split into separate runs.
If multi-goal, ask which to do first.
## Phase 2 — Write the Spec
Write to `docs/specs/{slug}.md` using [spec-template.md](spec-template.md). Rules:
- Intent frozen after approval
- Boundaries (Always/Ask-First/Never) drive implementation
- I/O matrix optional (include only if needed)
- Tasks are file-level, specific actions
- ACs are system behaviors (not I/O duplicates)
- Target 900–1300 tokens
Get explicit approval before implementing.
## Phase 3 — Implement
For each task:
1. Implement.
2. Check off: `[ ]` → `[x]`.
3. If wrong assumption: update spec, don't silently deviate.
Stop only if: Ask-First boundary triggered, dependency missing, or requires out-of-scope changes risking breakage.
**Veri