メニュー
Execute a sprint plan by reading task files, dispatching subagents per task, and managing review cycles. Uses subagent-driven-development pattern.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | execute-sprint |
| description | Execute a sprint plan by reading task files, dispatching subagents per task, and managing review cycles. Uses subagent-driven-development pattern. |
Read a sprint plan, extract tasks, and dispatch subagents to implement each task with review cycles.
/execute-sprint <plan-file-path>
Example: /execute-sprint docs/superpowers/plans/2026-04-11-gap-closure-multi-sprint.md
Read the specified plan file and extract:
Before executing:
npm run typecheck passes on current branchgit status --porcelain)For each wave (group of independent tasks):
superpowers:dispatching-parallel-agents skill to spawn one agent per task in the wavenpm run lint && npm run typecheckAfter each wave completes:
feat(<sprint>): complete wave <N> — <task summaries>After all waves complete:
npm run lint && npm run typecheck && npm run buildFor each task, spawn an agent with:
Task: <task name>
Description: <from plan>
Files to modify: <from plan>
Acceptance criteria: <from plan>
Rules:
- Read CLAUDE.md before writing code
- Use @ui primitives — never raw HTML
- Run `npx eslint <changed-files>` and `npx tsc --noEmit` before reporting done
- Commit changes to your branch when complete
The plan should contain tasks in this structure:
### Task N: <name>
- **Wave:** <number>
- **Depends on:** <task numbers or "none">
- **Files:** <list of files to create/modify>
- **Description:** <what to implement>
- **Acceptance criteria:** <what "done" looks like>
Navigate the ADC codebase by domain name. Use when finding, locating, or tracing files for any domain (auth, tasks, visualization, github, etc.), when asked 'where is X', when needing to understand how a feature connects across layers, or when starting work on any domain. Also use proactively before reading/searching files to resolve the right paths first.
Scaffold a new Feature Slice Design domain. Generates all 8 layers (channels, contract, schema, service, handlers, hooks, components, barrel) from a domain name.
ADC-specific QA review skill for wave-scoped task review. Use when reviewing code changes from agent-team tasks — runs incremental lint/typecheck on changed files only, validates against ADC architecture and design system rules. Replaces full-codebase npm run lint/typecheck/build with targeted checks.
Core Tailwind CSS patterns, gotchas, and fixes for layout, alignment, spacing, and responsive design. Use when debugging visual layout issues or writing Tailwind classes.
Build distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, dashboards, React components, HTML/CSS layouts, or styling/beautifying any web UI. Avoids generic AI aesthetics. Uses shadcn UI MCP for components.
shadcn/ui component patterns for Next.js 16 applications. This skill should be used when adding UI components, customizing component styles, composing primitives, or integrating forms with react-hook-form. Covers installation, customization, composition patterns, and Atlas-specific conventions using Tailwind CSS v4.