scaffoldlisted

Scaffold a new feature end-to-end: API contract → database schema → backend service/controller → frontend. Use when building something new from scratch across multiple layers. More opinionated than /implement — always runs the full vertical slice in the correct dependency order. Trigger this when someone says: build this feature from scratch, scaffold a new endpoint, I need a full-stack feature, new feature end-to-end, build the whole thing. Do NOT use when the task is already partially built or only one layer needs changes — use /implement instead.
chuckplayer/claude-agent-pack · ★ 2 · API & Backend · score 75

Install: claude install-skill chuckplayer/claude-agent-pack

# Scaffold New Feature Build a new feature end-to-end across all layers in the correct dependency order. ## 1. Confirm scope Before starting, confirm with the user: - **What** is being built (feature name and one-sentence description) - **Which layers** are needed (API, DB, backend, frontend — not every feature needs all four) - **Any constraints** (naming conventions, existing patterns to follow, related entities) Read `docs/CONVENTIONS.md` if it exists. Check `memory/**/*.md` for any architecture or design decisions relevant to this feature. ## 2. git-engineer — branch setup Always first. Confirm the working branch. If on `main` or `master`, ask the user to name the feature branch before proceeding. Do not start any implementation until the branch is confirmed. ## 3. api-designer — REST contract Always invoke for new features that expose any endpoint. Pass: - The feature description and scope confirmed in step 1 - Any existing API patterns to follow (from CONVENTIONS.md or memory) The api-designer will produce routes, HTTP methods, request/response shapes, status codes, and auth requirements. Present the contract to the user and ask for approval before proceeding to implementation. ## 4. database-engineer — schema and migrations Invoke if the feature requires new or modified tables, columns, indexes, or stored procedures. Pass the approved API contract as context so entity names and field names stay consistent. Use `isolation: "worktree"` for database-engineer.