spec-driven-agentslisted
Install: claude install-skill bankielewicz/DevForgeAI
# Creating Agents
Create DevForgeAI-aware Claude Code subagents through guided specification with framework compliance validation.
**Output:** `.claude/agents/{name}.md` (subagent file) + optional reference file
**Invoked by:** `/create-agent` command
**Delegates to:** `agent-generator` subagent v2.0
---
## Execution Model
See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution contract (expand inline; do not wait passively or offer execution options; honor every step of every phase; Self-Check violation taxonomy; Token-Optimization-Bias prohibition; governed by ADR-076). After invocation, execute Phase 00 Initialization immediately.
---
## Anti-Skip Enforcement Contract
Enforced structurally outside LLM control, not by this prose — by the framework's deterministic gates wired for this workflow: the `devforgeai-validate` phase gates, the `settings.json`-registered `.claude/hooks/` scripts, and `.claude/hooks/phase-steps-registry.json` (ADR-076). Behavioral residue: `.claude/rules/core/anti-skip-behavior.md`.
---
## Parameter Extraction
Extract from conversation context:
| Parameter | Source | Default |
|-----------|--------|---------|
| `$NAME` | First argument after `/create-agent` | null (will ask in Phase 02) |
| `$MODE` | `--template=`, `--domain=`, `--spec=`, or guided | "guided" |
| `$TEMPLATE` | Value from `--template=` flag | null |
| `$DOMAIN` | Value from `--domain=` flag | null |
| `$SPEC_FILE` | Value from `--spec=` flag | null |