← ClaudeAtlas

dev-single-goallisted

Implement a single stated goal in any folder — no project docs required. Grills for intent, writes a verifiable plan, executes, and verifies by running. Use when the user states a task/goal in a folder with no leanwheel docs/ tree, or says "single goal", "dev goal", "just do this here", or "one-off task".
rterakedis/leanwheel-skills · ★ 2 · AI & Automation · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Dev Single Goal Skill **Goal:** Drop into any folder, take one stated goal from intent → grilled requirements → approved verifiable plan → implemented → verified green. Zero doc prerequisites, zero doc obligations. **When:** Any folder that is *not* a leanwheel project — a coworker's repo, a scripts directory, a fresh clone, an experiment. If `docs/prd.md` **and** `docs/architecture.md` exist, this is a leanwheel project: recommend `/quick-dev` instead (it keeps those docs current — this skill deliberately does not) and proceed here only if the user confirms they want the doc-free lane. ## Activation Nothing is required to exist. Read what happens to be there, silently skip what isn't: 1. Read `CLAUDE.md` / `AGENTS.md` if present (project conventions override defaults). 2. If `docs/architecture.md` + `docs/prd.md` exist → say the one-line `/quick-dev` recommendation above, then follow the user's choice. 3. Detect the toolchain from files (`*.xcodeproj`/`*.xcworkspace`/`Package.swift`, `package.json`, `pyproject.toml`, `go.mod`, `Makefile`, …) — this drives the Build & Test Gate later. No toolchain is fine; note it. 4. Identify the goal. If the user hasn't stated one, ask: "What should this do — user-facing outcome?" **Scope check:** single goal = one deliverable (cross-layer work OK if serving one goal). Multi-goal → ask which to do first; each goal is its own run. ## Phase 1 — Grill **Classify complexity first — it scales everything below:** - **Stateful / multi-st