القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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 | phase-checkpoint |
| description | 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. |
| argument-hint | <phase-number> <feature-name> |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, Task |
Prove Phase $1 of features/$2 is actually done before advancing. Reads commands from
.claude/verification-config.json — never hardcode them here.
Confirm all Phase $1 tasks are checked in features/$2/EXECUTION_PLAN.md. If any are open, STOP
and say which — the phase isn't complete.
Run the quality gate (quality_gate.command from verification-config = pnpm precheck):
check:api-bans → check:router → check:arch → lint → typecheck → test.
Capture pass/fail per stage. If it fails, report the failing stage + output and STOP — do not advance.
Run the phase's user-facing criteria (from the "Phase $1 Checkpoint" section of the plan):
BROWSER → Playwright (apps/web/e2e/) / Chrome DevTools MCP against :3000DEVICE → XcodeBuildMCP + axe on the simulator (needs Metro + API running)E2E → pnpm --filter @motovault/web exec playwright test (web) / pnpm --filter @motovault/mobile test:e2e (Maestro)MANUAL.Knip (advisory): if the phase added/removed modules, run pnpm knip and note any new unused
files/exports/deps introduced by this phase (don't block on the pre-existing backlog).
Regeneration sanity: if the phase touched .graphql/resolvers/models/migrations, confirm
pnpm generate produces no uncommitted diff (generated files are protected — they must be in sync).
Write features/$2/verification/phase-$1.md:
# Phase $1 Checkpoint — <status: PASS | FAIL>
## Quality gate (pnpm precheck)
- api-bans: PASS/FAIL
- router: PASS/FAIL
- arch: PASS/FAIL
- lint: PASS/FAIL
- typecheck: PASS/FAIL
- test: PASS/FAIL (N passed)
## User-facing criteria
- <criterion> — PASS/FAIL (how verified)
## Advisory
- knip: <new issues this phase introduced, or "none">
- generate: <clean / drifted>
## Verdict
<Ready to advance to Phase N+1 / open a PR> OR <blockers to fix>
MANUAL: report ready. Offer the next phase (/phase-start <N+1> $2) or,
if this was the last phase, offer to commit + open a PR (/ce-commit-push-pr or the repo's PR flow).