メニュー
Use after the project brief is agreed, to produce a phased, multi-file implementation plan with a hard human sign-off gate, before any build work begins. Establishes the decision log and durable state files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when building or structuring a Python backend on FastAPI + SQLAlchemy 2.0 (async) + Alembic + Pydantic v2. Provides the opinionated project layout, the standard kit (auth, async jobs, caching, storage, observability), and best practices.
Use near the end of a project to generate CI and make the app deploy-ready. Produces a polyglot GitHub Actions workflow (lint, typecheck, test, build) and multi-stage Dockerfiles. The finish line is CI-green and container-ready, not an actual deploy.
Use when starting a frontend or working on its look and feel, to establish and enforce a DESIGN.md-driven custom design system as the single source of truth for tokens, components, and icons. Make any generated UI (including 21st.dev Magic output) conform to DESIGN.md.
Use when setting up local development services or running the project locally. Establishes the "stateful services in Docker, app runs native" pattern with Postgres, Redis, MinIO, and Mailpit.
Use after the plan is signed off, to drive the autonomous, plan-gated build to completion. Orchestrates per-task implementation, review, and verification in customer-experience-first order, stopping only on genuine blockers.
Use when building or structuring a React/Next.js + TypeScript + Tailwind frontend, choosing libraries, or wiring design tokens. Provides the opinionated blessed-library stack and the React-vs-Next decision, all on-token to DESIGN.md and accessible to WCAG AA.
| name | plan-project |
| description | Use after the project brief is agreed, to produce a phased, multi-file implementation plan with a hard human sign-off gate, before any build work begins. Establishes the decision log and durable state files. |
Announce at start: "I'm using claude-engineer:plan-project to produce the phased plan."
NO BUILD WORK BEFORE THE USER SIGNS OFF ON THE PLAN. Violating the letter is violating the spirit.
superpowers:writing-plans - turn the agreed brief into bite-sized, testable tasks; map the file structure first; right-size tasks; bake in DRY/YAGNI/TDD.project-conventions, monorepo-and-tooling, docker-dev-environment).design-system: DESIGN.md is the source of truth).frontend-development, on-token, WCAG AA).backend-development).testing-and-quality, ci-cd-pipeline).docs/plan/ - 00-overview.md plus one file per phase (01-design-system.md, 02-frontend.md, …), each with goals, tasks, file targets, and the per-phase "definition of done" (the four quality gates).docs/plan/decisions.md (every non-obvious choice + why).claude-engineer:project-memory (creates .claude-engineer/memory.md, progress.md, current-phase.txt).claude-engineer:execute-build until they do.Tests + coverage · Playwright E2E with zero console errors · WCAG AA · strict types + lint clean.
(See claude-engineer:testing-and-quality.)
docs/plan/* so it survives and stays scannable.