メニュー
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.
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 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.
Use at the very start of a new project to turn a rough idea or a draft brief into a refined, agreed project brief. Looks for a user-written draft; refines it by questioning if present, or runs an interactive intake interview to create it if absent.
| name | execute-build |
| description | 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. |
Announce at start: "I'm using claude-engineer:execute-build to drive the autonomous build."
Only run after the user signed off on the plan (claude-engineer:plan-project). If there is no
signed-off plan in docs/plan/, stop and go back.
.claude-engineer/memory.md, progress.md, current-phase.txt). Trust them over recollection.superpowers:using-git-worktrees before writing code.project-conventions, monorepo-and-tooling, docker-dev-environment (scaffold)design-system → frontend-development → backend-developmenttesting-and-quality, ci-cd-pipelinesuperpowers:subagent-driven-development - a fresh implementer subagent per task; each task uses superpowers:test-driven-development. Use superpowers:dispatching-parallel-agents for independent workstreams. Fall back to superpowers:executing-plans only where subagents are unavailable..claude-engineer/progress.md; record decisions in memory.md.superpowers:systematic-debugging (root cause before fixes).superpowers:requesting-code-review + superpowers:receiving-code-review.superpowers:verification-before-completion AND run the four gates via claude-engineer:testing-and-quality.claude-engineer:ci-cd-pipeline then superpowers:finishing-a-development-branch.Plan-gated then autonomous: run to completion without check-ins. Stop only on genuine blockers - ambiguous requirements not covered by the brief, a destructive/irreversible action, missing credentials, or a decision that changes the agreed plan. Surface the blocker crisply with options.
progress.md.