메뉴
Break a feature into phased, verifiable tasks with acceptance criteria and verification metadata. Use at the start of a non-trivial feature, before implementation. Produces features/<name>/EXECUTION_PLAN.md.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run the full quality gate for a completed feature phase and produce a verification report before advancing or opening a PR. Use after /phase-start finishes a phase.
Execute all tasks in a feature phase autonomously — explore, write tests, implement, verify. Use after /feature-plan produces an EXECUTION_PLAN.md. Stops and escalates when stuck.
Write unit/integration tests for API services & resolvers, web logic, and mobile utils, plus E2E flows. Use when writing tests, adding coverage, or reviewing test quality in MotoVault.
Autonomously researches real, cited source data and publishes one high-quality SEO blog article to the MotoVault blog CMS (Supabase). Alternates between auto-published informational GUIDES targeting real Search Console demand, and maintenance-SPEC drafts (researched from official manuals, staged for human verification). Every article records its sources and carries a verify-against-official-docs disclaimer plus an app-download conversion CTA. Trigger when asked to write a blog post, run the daily blog job, expand the blog, or publish an article.
Create social media content for MotoVault — the AI-powered motorcycle learning & diagnostics app. Generates Instagram carousels, single posts, and story-format content using real app screenshots and the established dark-theme brand style. Can suggest post ideas based on app features or execute a specific idea from the user. Use this skill whenever the user mentions creating social media posts, Instagram carousels, marketing visuals, promotional content, or social graphics for MotoVault. Also trigger when the user says "create a post", "promote a feature", "marketing content", "social media", "carousel", or "Instagram" in the context of MotoVault.
Autonomously adds 5–10 new motorcycle route templates to the MotoVault Supabase database. Queries existing coverage, selects the most underrepresented famous riding region from 8 priority destinations, and inserts real routes with verified GPS coordinates and properly structured multi-day waypoints. Trigger when asked to add routes, expand the route library, grow the trip database, run the daily route job, or populate routes for a specific country or region.
| name | feature-plan |
| description | Break a feature into phased, verifiable tasks with acceptance criteria and verification metadata. Use at the start of a non-trivial feature, before implementation. Produces features/<name>/EXECUTION_PLAN.md. |
| argument-hint | <feature-name> |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
Turn a feature idea into an EXECUTION_PLAN.md that /phase-start can execute and
/phase-checkpoint can verify. Adapted for MotoVault's stack (Turborepo, NestJS+GraphQL,
Supabase+RLS, Expo mobile, Next.js web).
features/$1/EXECUTION_PLAN.md — phases, each a small set of tasks. Every task carries
testable acceptance criteria tagged with a verification type (below).
Do NOT plan in a vacuum. First:
Grep/Glob across apps/ + packages/.supabase/migrations/) + RLS policies — every new table needs RLSpnpm generate:types → Zod schemas in packages/typesapps/api (map snake_case → camelCase at the service layer).graphql operations + pnpm generateapps/mobile) and/or web (apps/web), using @motovault/graphql typesRecord the integration points found, so tasks reference real files, not guesses.
| Tag | Meaning | How it's verified |
|---|---|---|
TEST | Automated test proves it | pnpm --filter <pkg> test (Vitest/jest — see /write-tests) |
TYPE | Type-level guarantee | pnpm typecheck |
GATE | Full quality gate | pnpm precheck (api-bans, router, arch, lint, typecheck, test) |
BROWSER | Web UI behavior | Playwright (apps/web/e2e/) or Chrome DevTools MCP against :3000 |
DEVICE | Mobile UI behavior | XcodeBuildMCP + axe on the simulator (ad-hoc), or a Maestro flow (E2E) |
E2E | Committed end-to-end regression | Playwright (web) / Maestro (mobile) |
MANUAL | Human judgment (copy, brand, feel) | Reviewer confirms |
Commands come from .claude/verification-config.json — keep criteria expressed in terms of it.
# Feature: <name>
## Context
- Problem / goal (1–3 sentences)
- Integration points found: <files, existing patterns to reuse>
- Out of scope: <deferred items>
## Phase 1: <slice>
Each phase is independently shippable and ends green on `pnpm precheck`.
- [ ] Task 1.1: <what>
- Files: <paths>
- Acceptance:
- `TEST` <observable behavior a test asserts>
- `TYPE` <type guarantee>
- Requirement: REQ-XXX (optional)
## Phase 1 Checkpoint
- `GATE` pnpm precheck passes
- `E2E`/`DEVICE`/`BROWSER` <user-facing criteria, if any>
- `MANUAL` <anything needing human eyes>
pnpm precheck and is reviewable in one sitting.pnpm generate before any API code depends on the shape.DEVICE/BROWSER or E2E criterion, not just TEST.Next: /phase-start 1 $1.