team-featurelisted

Orchestrates a full vertical slice for one feature: feature-spec check → API contract (GraphQL/REST) → data model → backend → frontend/game → tests → security review → code review, spawning the right leads and engineers in parallel where independent. Use to deliver a feature end-to-end.
gonimar/claude-web-studio · ★ 0 · Web & Frontend · score 76

Install: claude install-skill gonimar/claude-web-studio

# Team: Feature Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. Orchestration. File writes and any mutation (git, deploy) happen only after an explicit "May I write?" / "Proceed?" — each one `AskUserQuestion` (proceed (Recommended) · show the draft/diff first · not now) → "yes"; delegated agents follow the same protocol. A partial report on BLOCKED at any stage is mandatory. After the "write" answer: `touch .claude/.write-consent` (rule 7 — the consent-guard hook checks the marker). ## Phase 1: Readiness A feature spec with criteria (missing → run `/feature-spec`); technical-preferences; review mode. ## Phase 2: Contract and data (in parallel) `api-designer` (SDL/OpenAPI changes) ‖ `database-engineer` (schema/migrations). Results to the user for agreement; then codegen. ## Phase 3: Implementation Backend (`go-engineer`/`php-engineer`/`node-engineer` + `graphql-engineer`) → once the contract is ready, in parallel frontend (`angular-engineer`/`vue-engineer`, `css-engineer`) and game (`threejs-engineer`/`web-game-engineer`) — the frontend may start on mocks from the contract. Engineers write the tests; e2e — `test-engineer`. ## Phase 4: Verification `appsec-engineer` (mandatory for sensitive work, else per mode) ‖ `accessibility-specialist` (UI) ‖ `performance-engineer` (budget risk) — in parallel; then `/code-review --diff`. ## Phase 5: Summary Table criteria ↔ tests ↔ results; open findings