agent-creator · diff
git:20260617.c13a499 to git:20260805.9740c56
13 added, 27 removed. Audit A to A.
---
name: agent-creator
description: >-
- Scaffold a new agent profile under agents/ or verticals/, register it in AGENT_REGISTRY.md and AGENTS.md, and run conformance validation tests.
+ Compatibility alias for the deprecated /agent-creator workflow. Route new agent requests through foundry/agent-forge so persistent autonomy must be justified and independently proven.
---
- # Agent Creator
-
- ## Overview
-
- This skill allows the agent to dynamically create and register new specialist agents inside the Starlight Intelligence System (or custom vertical sub-stacks) while ensuring that the repository's strict symmetry tests remain fully green.
-
- ## Dependencies
-
- - `orchestration/workflow-design`
- - `memory/vault-management`
+ # Agent Creator — Deprecated Alias
- ## Quick Start
+ Use `foundry/agent-forge` for all new work.
- To create a new agent:
- 1. Validate that the agent name matches lowercase + hyphen syntax (e.g., `space-orbit-tracker`).
- 2. Write the profile to `agents/starlight-{name}.md` (or vertical sub-path) using the standard agent template.
- 3. Append the agent metadata row to `agents/AGENT_REGISTRY.md` and root `AGENTS.md`.
- 4. Run `npm test test/v76.test.ts` to ensure no phantoms or orphans are introduced.
+ This alias remains only so explicit legacy invocations do not break. It must not scaffold an agent directly.
- ## Template Standard
+ ## Compatibility flow
- Every agent profile markdown file must contain:
- - YAML frontmatter with `name: starlight-{slug}`, `tier: specialist`, `domain`, and `voice`.
- - Mission statement (explaining their primary purpose).
- - Active skills list.
- - Trigger activation keywords.
+ 1. Translate `/agent-creator <brief>` to `/forge agent <brief>`.
+ 2. Load `foundry/agent-forge`.
+ 3. Apply the durable autonomy-boundary gate.
+ 4. If no persistent decision, memory, tool, ownership, or trigger boundary exists, return a Skill Pack route.
+ 5. Compile and prove before registry changes.
- ## Common Mistakes
+ ## Migration
- - **Incorrect frontmatter keys:** Forgetting `tier:` or `voice:` will break the validation parser.
- - **Phantom references:** Registering an agent in `AGENT_REGISTRY.md` without writing the markdown file to disk.
- - **Unformatted filenames:** Naming files without the `starlight-` prefix for core agents.
+ - Old: `/agent-creator research-director ...`
+ - New: `/forge agent research-director ...`