builderlisted

# Builder Build one artifact through the matching type reference. Run inline and inherit the session model; do not fork or override the model unless the artifact being authored has an independently justified need. Arguments received: `$ARGUMENTS` ## Dispatch 1. Treat the first whitespace-delimited argument as `TYPE` and the remainder as the artifact name, request, or path. 2. Accept exactly these types: | Type | Read and follow | |------|-----------------| | `agent` | `references/agent.md` | | `skill` | `references/skill.md` | | `command` | `references/command.md` | | `rule` | `references/rule.md` | 3. If `TYPE` is missing or unknown, or the remaining request is empty or only whitespace, print the following and stop without reading type references or modifying files: ```text Usage: /builder <agent|skill|command|rule> <name-or-request> ``` 4. Read the selected reference completely, then execute its protocol against the remainder of `$ARGUMENTS`. The selected reference is authoritative for artifact shape and type-specific validation. ## Shared protocol Apply these steps for every valid type before the selected reference's type-specific steps. ### 1. Discover local authority - Find and read applicable `AGENTS.md` and `CLAUDE.md` files from repository root through the target directory. More local instructions win; in one directory, `AGENTS.md` is canonical. - Identify the source-of-truth artifact directory. In Open Harness