メニュー
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 職業分類に基づく
Generate Playwright end-to-end test specs and Page Object Models from UI/UX flow walkthroughs. Create complete user journey tests that exercise navigation, forms, and interactions. Use when scaffolding e2e tests, creating POMs, or generating Playwright specs for user flows.
Generate comprehensive Gherkin scenarios from approved FRDs. Produce feature files with acceptance criteria coverage, edge cases, and error handling scenarios. Use when creating BDD scenarios, writing feature files, or mapping FRD requirements to testable Gherkin specifications.
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 BDD test code from Gherkin scenarios. Create Cucumber step definitions with real test code (HTTP calls, Playwright interactions) and Vitest unit tests. Produce a red baseline where all tests compile and fail. Use when scaffolding BDD tests, creating step definitions, or generating unit tests from feature files.
Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results. Use during Phase 3 (e2e test verification), Phase 4 (red baseline verification), Phase 5 (contract type compilation), Phase 6 (API/Web/integration slices), Phase 7 (smoke tests against deployment), and on resume (re-validate test state). Trigger when running tests, checking test status, or verifying test baselines.
Lightweight entry point for fixing bugs with full traceability. Takes a bug report, links to the relevant FRD, generates a failing test, fixes the code, and ships. Tracked as a micro-increment. Use when fixing bugs with test-first methodology and spec2cloud pipeline traceability.
| 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 timeline