메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
Use to review cap4k plan evidence, generated output ownership, conflict policies, template IDs, addon artifacts, generation drift, and the stop point before handwritten implementation.
| name | cap4k-generator-inputs |
| description | 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. |
Use this after the technical design contract exists and before plan review.
../shared/rules/generator-input-source-of-truth.md../shared/workflows/skeleton-generation-gate.mdworkflows/project-generator-inputs.md| Task | Read | Workflow |
|---|---|---|
| Choose the generator input surface | references/input-surfaces.md | workflows/project-generator-inputs.md |
Update design/design.json or registered design JSON fragments | references/input-surfaces.md, then references/design-json-contract.md | workflows/project-generator-inputs.md |
| Update DB/schema DDL comments | references/input-surfaces.md, then references/db-schema-annotations.md | workflows/project-generator-inputs.md |
| Update enum or value-object manifests | references/input-surfaces.md, then references/manifest-contracts.md | workflows/project-generator-inputs.md |