New Entry

Create New Registry Entry

Guide the user through creating a properly structured registry entry.

Arguments

• $1 - Element type: component, software-system, data-concept, data-aggregate, data-entity, domain-event, api-endpoint, etc.
• $2+ - Element name (can have spaces)

If arguments not provided, ask the user:

1. What type of element?
2. What is the element name?
3. Which domain does it belong to?

Element Type to Folder Mapping

Do NOT hardcode paths. Always discover dynamically:

1. Read models/registry-mapping.yaml
2. Find the element type under elements:
3. Use the folder: field for that type to determine the target directory
4. Prepend registry-v2/ to the folder path

This ensures the skill works even if users rename layers, types, or restructure folders.

Workflow

1. Determine element type and target folder
2. Read _template.md in the target folder for structure
3. Read 1-2 existing entries in target folder for pattern reference
4. Create filename: kebab-case of name (e.g., "Payment Record" -> "payment-record.md")
5. Fill frontmatter:
   • name: [provided name]
   • owner: TBD
   • status: draft
   • [type-specific fields and relationships from template]
6. Write file to correct folder
7. Run validation: python scripts/validate.py

Response Format

**Created:** registry-v2/<layer>/<type-folder>/element-name.md

**Frontmatter:**
---
type: <element-type>
name: <Element Name>
owner: TBD
status: draft
<type-specific fields from template>
---

**Next Steps:**
1. Fill in TBD fields
2. Add description in the body
3. Run /validate to verify

Would you like me to help fill in any of the TBD fields?

Domain-Specific Fields

For data elements (concepts, aggregates, entities), also include:

• Relationship to parent element (data concept -> aggregate -> entity chain)
• classification: internal/business-confidential/pii

For software elements (systems, subsystems), also include:

• sourcing: in-house/vendor/hybrid
• vendor: (if vendor)
• realizes_component: Which component this system supports

Notes

• Always use kebab-case for filenames
• Mark unknown fields as TBD rather than guessing
• Run validation after creation to catch issues early
• Suggest wiring relationships as a follow-up action