메뉴
Explore and validate feature design before writing specs. Uses Socratic questioning to refine the idea, compares 2-3 approaches with trade-offs, and produces a design summary approved by the user before handing off to /spec.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
Implement a feature. Supports resuming interrupted work and team mode (--team flag). Reads spec/feature/[name]/spec.md and design.md, generates PLAN.md inside the feature directory, waits for user confirmation, then implements and verifies the feature.
Generate or update MSW mock handlers and fixtures from feature spec API contracts. Use to set up mock infrastructure, generate feature-specific mocks, or check mock status.
AI-driven browser testing against feature specs. Default mode reads spec REQs and autonomously tests in a real browser via Playwright MCP. Also supports running existing Playwright test files, visual regression, and accessibility audits.
Check how well the current implementation matches the feature spec and evaluate code quality. Runs spec compliance review followed by code quality review. Optionally runs unit/integration test audit, logging audit, and security audit when strategy files exist. Does not modify code.
| name | brainstorm |
| description | Explore and validate feature design before writing specs. Uses Socratic questioning to refine the idea, compares 2-3 approaches with trade-offs, and produces a design summary approved by the user before handing off to /spec. |
| argument-hint | [feature description] |
| context | fork |
Brainstorming always requires reasoning and design judgment → spawn brainstormer with model: sonnet.
Spawn brainstormer agent (sonnet) with the following prompt:
[HANDOFF]
TO: brainstormer (sonnet)
TASK: Brainstorm feature design based on the following description
DONE-WHEN:
- User has approved the final design summary
- A concise spec-ready summary has been presented
MUST-NOT:
- Write or modify any source code
- Write spec.md or design.md (that is /spec's job)
- Proceed past any phase without user approval
READS:
- spec/ARCHITECTURE.md
- spec/PROJECT.md
- spec/feature/ (scan existing features)
[/HANDOFF]
$ARGUMENTS