ai-forge-create

AI Forge Create

Write skills and agents that score ≥B on ai-forge-judge out of the box. Every section must earn its tokens.

---

Phase 0 — Dedup

Before anything else, check whether this already exists. Glob the platform roots listed in ai-forge-audit Phase 1 and compare names and descriptions against the request.

• Strong match (same domain and overlapping triggers) — surface it and stop: "<name> already covers this. Options — (u)pdate it via ai-forge-update, (c)reate anyway with a narrower scope, or (q)uit." An explicit "create a skill" request plus a strong match is a reason to challenge, not to comply.
• Partial match — name it, then continue; the new artifact must state how it differs in its own description.
• No match — continue silently.

---

Phase 1 — Discovery

Build understanding through a running recap. Ask questions to fill gaps; after each exchange, show the current recap:

## Discovery Recap

**Domain:** [what the skill/agent covers, or "unknown"]
**Artifact type:** [Skill / Agent / Instruction file]
**Platform:** [Claude Code / GitHub Copilot / OpenAI Codex / Google Gemini — infer from file path: .claude/ → Claude Code, .github/ → Copilot, .codex/ → Codex, .gemini/ → Gemini]
**Decisions:** [non-obvious choices the agent must make, or "unknown"]
**Failure modes:** [what breaks without this artifact, or "unknown"]
**Audience:** [fragile/creative output, or "inferred: ..."]
**Size:** [reference files needed, or "inferred: self-contained"]

Then ask: (a)ccept / (r)evise / (q)uit

• a — recap is complete; proceed to Phase 2
• r — user adds or corrects; update recap and loop
• q — abort

Do not proceed to Phase 2 until the user accepts the recap. Domain, artifact type, and failure modes must be filled before accepting. Platform must also be resolved — it drives frontmatter schema, file location, and invocation constraints for both agents and skills.

Porting an existing artifact to another platform? That's a conversion, not authoring — hand off to ai-forge-update, which runs the target disposition report and steps the judgment calls through approval. The per-field mappings live in references/conversion-guide.md.