メニュー
Registers and organizes custom artifact kinds in DNA. Use when the built-in template kinds do not cover a domain concept, or when setting up a new project with custom truth categories.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interactive conversation for deliberate truth changes. Acts as a truth guardian that searches DNA, surfaces conflicts, debates proposals, and only applies changes with explicit human reasoning. Use via text or voice mode in Claude Code.
Assembles DNA truth artifacts into a self-contained specification that an autonomous agent can execute against without further human guidance. Use when handing off a well-defined deliverable to an agent for extended autonomous execution.
Consults DNA truth artifacts during task planning to understand system identity before designing an implementation approach. Use at the start of any non-trivial task before choosing an architecture or decomposing work into steps. Searches for intents, contracts, and constraints that shape the solution space.
Creates escalation artifacts that define when an agent should stop autonomous work and involve a human. Use when encoding decision boundaries for agent autonomy -- the guard rails on what agents can decide alone.
Creates tradeoff artifacts that encode which concern wins when competing concerns clash. Use when two valid goals, constraints, or intents conflict and agents need to know which to prioritize.
Stores truth artifacts in DNA with correct kind, format, metadata, and semantic context. Use when codifying decisions, contracts, intents, or constraints that should persist across code changes, team transitions, and framework evolutions.
| name | managing-kinds |
| description | Registers and organizes custom artifact kinds in DNA. Use when the built-in template kinds do not cover a domain concept, or when setting up a new project with custom truth categories. |
Kinds categorize truth artifacts. The intent template provides 11 kinds, the agentic template provides 5. You can register additional kinds for domain-specific needs.
dna kind list
dna kind add <slug> "<description>"
The slug must be:
The description should follow the pattern of built-in kinds: state what this kind captures in one sentence, then give an example with Ex:.
dna kind add runbook \
"Operational procedure for a specific failure mode. Ex: 'Database failover: promote read replica, update DNS, verify replication'"
Create a new kind when:
--kindDo NOT create a new kind when:
--label type=runbook on an existing kind)Use a singular noun that describes what the artifact IS:
runbook (not runbooks or operational-procedures)sla (not service-level-agreements)decision (not architectural-decisions)When kinds are registered, the MCP server automatically generates tools for each kind:
dna_<kind>_search -- semantic search within this kinddna_<kind>_add -- store a new artifact of this kinddna_<kind>_list -- list all artifacts of this kindHyphens in slugs become underscores in tool names.