メニュー
Spec-driven development workflow. Propose features with specs, design docs, and tasks before writing code. Triggers on: /apex:spec, propose, write spec, design feature.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | apex-spec |
| description | Spec-driven development workflow. Propose features with specs, design docs, and tasks before writing code. Triggers on: /apex:spec, propose, write spec, design feature. |
| apex-version | 1.0 |
| apex-id | apex:spec |
| apex-category | process |
| apex-compatibility | ["superpowers","gsd","ralph"] |
| apex-lifecycle | {"phase":["discuss","plan","execute"],"triggers":["user says: propose a feature","user says: write spec","user says: /apex:spec","user says: start a change"]} |
Propose, design, and execute features with a lightweight spec workflow.
| Command | Description |
|---|---|
apex spec init | Initialize openspec/ directories |
apex spec propose "<feature>" | Create proposal, design, tasks |
apex spec list | Show active changes |
apex spec archive <name> | Archive completed change |
apex spec propose "add login"apex spec archive add-loginopenspec/
├── config.yaml
├── changes/
│ ├── add-login/
│ │ ├── proposal.md — Why + What + Impact
│ │ ├── design.md — Approach + Trade-offs
│ │ └── tasks.md — Task checklist
│ └── archive/ — Completed changes
├── explorations/ — Research notes
└── specs/ — Shared specs
Pi Coding Agent integration. Generate multi-agent team/chain configs and damage-control safety rules. Triggers on: pi, Pi agent, multi-agent, chain config, damage control.
Switch between development modes. Use /apex:mode to change mode or check current mode. Triggers on: switch mode, change mode, /apex:mode, what mode am I in.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.