メニュー
Append structured entries to .spec2cloud/audit.log for every significant action. Never overwrite, always append. Use when logging task execution, increment transitions, human gate events, or errors.
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 | audit-log |
| description | Append structured entries to .spec2cloud/audit.log for every significant action. Never overwrite, always append. Use when logging task execution, increment transitions, human gate events, or errors. |
Append every significant action to .spec2cloud/audit.log. Never overwrite — always append.
[ISO-timestamp] phase=PHASE action=ACTION result=RESULT
[2026-02-09T14:15:00Z] increment=resource-crud step=implementation slice=api iteration=1 action=write-code result=tests-3pass-2fail
[2026-02-09T14:30:00Z] increment=walking-skeleton action=increment-delivered result=transition-to-resource-crud
[2026-02-09T14:35:00Z] increment=resource-crud step=tests action=human-gate result=gherkin-approved
[2026-02-09T14:35:00Z] phase=discovery step=specs action=human-gate result=rejected feedback="missing error states for auth"
[2026-02-09T14:40:00Z] phase=deployment action=azd-provision result=error message="quota exceeded in eastus"
Every audit log entry MUST contain ALL of the following fields:
2026-02-09T14:40:00Z)phase= or increment= (what work is being done)action= field (what specific action was taken)result= field (outcome: done, error, approved, rejected, etc.)message= field for errors and rejections (human-readable detail)BLOCKING: An audit entry missing any required field makes the audit trail incomplete. The orchestrator must ensure every append follows this schema.