Skip to content

Planning & Building

Claude Kit provides a structured workflow for turning ideas into working code: Brainstorm > Plan > Execute > Verify.

"I need to add user authentication"
┌─────────────────┐
│ Brainstorming │ Explore requirements, ask questions,
│ │ evaluate approaches, validate design
└────────┬────────┘
┌─────────────────┐
│ Writing Plans │ Break into tasks, exact file paths,
│ │ code samples, verification steps
└────────┬────────┘
┌─────────────────┐
│ Executing Plans │ Fresh subagent per task, code review
│ │ between tasks, quality gates
└────────┬────────┘
┌─────────────────┐
│ Verification │ Run tests, verify builds,
│ │ evidence before claims
└─────────────────┘

Triggers on: “brainstorm”, “design”, “explore”, “what if”, “how should we”, “trade-offs”

The brainstorming skill uses a three-phase process:

  1. Understanding — Asks one question at a time to clarify requirements. Prefers multiple-choice over open-ended questions.
  2. Exploration — Presents 2-3 approaches with trade-offs, leads with a recommendation.
  3. Design — Presents the validated design in digestible 200-300 word sections.
You: "Let's brainstorm adding real-time notifications"
Claude: "Which delivery mechanism fits your use case best?
a) WebSockets — persistent connection, instant delivery
b) Server-Sent Events — simpler, one-way push
c) Polling — simplest, but higher latency"
You: "b) SSE"
Claude: "## Approach 1: SSE + Redis Pub/Sub (Recommended)
Server pushes events via SSE, Redis coordinates across instances.
- Pros: Simple, works with load balancers, auto-reconnect built in
- Cons: One-way only (client can't push back)
## Approach 2: SSE + PostgreSQL LISTEN/NOTIFY
..."

Triggers on: “plan”, “break down”, “implementation steps”, “task list”

The writing-plans skill creates detailed implementation plans with:

  • Exact file paths for every change
  • Complete code samples (not descriptions)
  • Verification commands with expected output
  • 2-5 minute task granularity
## Task 1: Create User model with email field
**Files**:
- Create: `src/models/user.ts`
- Test: `src/models/user.test.ts`
**Steps**:
1. Write failing test
2. Verify test fails
3. Implement minimally
4. Verify test passes
5. Commit

Triggers on: “execute the plan”, “run the plan”, “implement the plan”

The executing-plans skill runs each task with:

  • Fresh subagent per task — Prevents context pollution
  • Code review between tasks — Catches issues early
  • Quality gates — Critical issues must be fixed before proceeding
Task 1 → Implement → Review → Fix issues → ✓
Task 2 → Implement → Review → Fix issues → ✓
Task 3 → Implement → Review → Fix issues → ✓
Final comprehensive review → ✓

Auto-triggers on: completion claims (“done”, “fixed”, “tests pass”)

The verification-before-completion skill requires evidence before any completion claim:

  • Run the actual test suite and read the output
  • Verify the build succeeds
  • Check that the feature works as intended

These skills activate automatically during planning and building:

SkillWhen It Helps
feature-workflowEnd-to-end feature development
sequential-thinkingComplex decisions needing step-by-step reasoning
languagesPython/TypeScript/JavaScript idioms and patterns
backend-frameworksFastAPI, Django, NestJS, Express patterns
frontendReact, Next.js component architecture
databasesSchema design, queries, migrations
state-managementChoosing between useState, Zustand, TanStack Query
AgentRole
plannerResearch and create implementation plans
brainstormerExplore solutions and evaluate trade-offs
researcherResearch technologies and best practices