メニュー
Create standardized git commits at phase and increment boundaries. Defines commit procedures, message formats, and state bundling. Use when committing after phase completion, increment delivery, or slice implementation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create Domain-Driven Design proposals from product specs or brownfield extraction outputs. Define bounded contexts, ubiquitous language, aggregates, context maps, and Mermaid-based domain and database diagrams. Use when domain boundaries, business rules, or data ownership need to be explicit before planning, implementation, or modernization.
Identify, research, and resolve every technology needed by the application. Evaluate data storage, caching, AI/ML, authentication, real-time, search, infrastructure, and library choices. Use when resolving technology decisions, comparing framework options, or documenting the tech stack before implementation begins.
Write application code to make failing tests pass using contract-driven, slice-based architecture. Implement API slice (Express routes, services), Web slice (Next.js pages, components), and Integration slice (wire API+Web via Aspire). Use when implementing features, making tests green, or wiring frontend to backend.
Generate a Product Requirements Document (PRD) from analyzed codebase extraction data. Reverse-engineer the product vision, user personas, and feature list from what the code actually implements. Used in brownfield workflows to produce a spec2cloud-compatible PRD that drives downstream FRD generation, increment planning, and implementation.
Review PRDs and FRDs through product and technical lenses. Identify gaps, ambiguities, edge cases, and conflicts. Break approved PRDs into FRDs. Use when refining specifications, reviewing PRDs, creating FRDs, or validating spec quality before downstream phases.
Extract API contracts from existing code — routes, endpoints, request/response schemas, authentication patterns. Output in the same OpenAPI-compatible YAML format used by the contract-generation skill. Pure extraction — document the API surface that exists in code without judgment or suggestions.
| name | commit-protocol |
| description | Create standardized git commits at phase and increment boundaries. Defines commit procedures, message formats, and state bundling. Use when committing after phase completion, increment delivery, or slice implementation. |
At key checkpoints, create commits that bundle artifacts produced. This gives a clean, resumable history in git log.
After a step or phase completes (and human gate approved, where applicable):
1. Stage all changes:
git add -A
2. Commit with an appropriate tag (see table below).
3. Update state.json to reflect the new state.
4. Append an entry to audit.log.
5. Commit the state update:
git add .spec2cloud/ && git commit -m "spec2cloud: state update"
| Event | Commit Message |
|---|---|
| Shell setup | [phase-0] Shell setup complete |
| Product discovery | [phase-1] Product discovery complete — N FRDs, N screens, N increments, tech stack resolved |
| Increment tests | [increment] {id}/tests — test scaffolding complete |
| Increment contracts | [increment] {id}/contracts — contracts generated |
| Increment slice | [impl] {id}/{slice} — slice green |
| Increment all tests green | [impl] {id} — all tests green |
| Increment delivered | [increment] {id} — delivered |
| All increments complete | [release] All increments delivered — product complete |
Each increment is a self-contained delivery. Commits at increment boundaries mean:
git log --oneline --grep="\[increment\]" shows the delivery timelineThe orchestrator MUST verify ALL of the following for every commit:
.spec2cloud/state.json is included in the commit.spec2cloud/audit.log is included in the commit.env files, or node_modules are stagedBLOCKING: A commit without state.json and audit.log breaks resume capability. The orchestrator must include them before finalizing the commit.