菜单
Use to review cap4k plan evidence, generated output ownership, conflict policies, template IDs, addon artifacts, generation drift, and the stop point before handwritten implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when projecting an approved cap4k technical design into generator inputs such as DB/schema, design JSON, manifests, Gradle extension settings, addons/options, or template override decisions.
Route cap4k business-authoring work through the self-contained cap4k skill system. Use when the user asks to discover a business slice, model DDD boundaries, write cap4k technical design, author generator inputs, review plan or generated output, implement handwritten business logic, design service integration, or verify cap4k work.
Use when a coherent cap4k business brief needs tactical DDD decisions mapped to cap4k carriers, generator input expectations, rollback notes, and the next technical design phase.
Use for cap4k business service interaction design and implementation: Open Host Service entries, Published Language, external capability clients, external fact entries, inbound/outbound integration events, callbacks, message listeners, and command/query routing across service boundaries.
Use when implementing cap4k handwritten business logic inside approved generated skeletons after human generated-output review: command handlers, query handlers, subscribers, jobs, controllers, factories, specifications, domain services, Repository access, Mediator routing, and UoW persistence.
Use for cap4k verification and audit claims: static review, focused local evidence, full evidence, generated-versus-handwritten ownership checks, skipped-check disclosure, rollback targeting, and final evidence summaries.
| name | cap4k-generation-review |
| description | Use to review cap4k plan evidence, generated output ownership, conflict policies, template IDs, addon artifacts, generation drift, and the stop point before handwritten implementation. |
Use this after coherent generator inputs exist and before handwritten implementation.
rules/generation-stop-policy.md../shared/references/output-ownership-taxonomy.mdworkflows/review-plan-and-generate.md| Task | Read | Workflow |
|---|---|---|
| Review plan evidence before generation | references/plan-review-gotchas.md | workflows/review-plan-and-generate.md |
| Review generated output ownership or drift | references/plan-review-gotchas.md | workflows/review-plan-and-generate.md |