full-stack-build

name

full-stack-build

description

Multi-step workflow for building complete features end-to-end. Use when starting a new feature, building a side project from scratch, or coordinating multiple technical skills in sequence. Chains brainstorming → API design → database schema → React implementation → deployment with explicit gates between each step. Triggers on: /fullstack, "build feature end-to-end", "full stack feature", "new feature workflow".

Full-Stack Build Workflow

Orchestrates a complete feature build by chaining specialized skills in sequence. Each step produces a documented output that the next step reads before proceeding. Do not skip steps.

Skill Chain

brainstorming
    ↓
api-design-principles        [Gate: api.md must exist]
    ↓
supabase-postgres             [Gate: schema.md must exist]
    ↓
react-best-practices
+ vercel-composition-patterns [Gate: components/ must exist]
    ↓
deploying-to-github          [Gate: env vars + tracking verified]

---

Step-by-Step Execution

Phase 0 — Brainstorm

Before touching code, clarify:

1. One-sentence feature description (user, action, outcome)
2. Explicit non-goals (what this iteration does NOT do)
3. Success metric (what number changes if this works?)

Output: docs/features/YYYY-MM-DD-[feature]/implementation-notes.md (header section)

---

Phase 1 — API Design

Load skill: api-design-principles

Define all endpoints or server actions for this feature before writing any implementation:

• Resource names (plural nouns)
• HTTP methods and paths
• Request/response TypeScript types
• Error codes as string constants
• Auth requirements per endpoint

Gate: docs/features/YYYY-MM-DD-[feature]/api.md must exist and be reviewed before proceeding to Phase 2.