| name | forge |
| description | Use when a new skill must be created from a decision, verdict, or capability gap — the user says "forge a skill", "turn this verdict into a skill", "build a skill for X", or pantheon/nexus hands over a VERDICT recommending one. Produces a secure, evaluated, quarantined skill package with an AI-BOM. |
| allowed-tools | Read, Grep, Glob, LS, Bash, Edit, Write, Agent, Skill |
forge — verdict → secure, evaluated, registered skill
Eight gated phases; no phase starts until the previous one's criterion is met, and no
skill leaves quarantine without the human. House law applies throughout:
skill-authoring-standard (four gates + frontmatter SSOT) and the Fable-5 restraint
rules already in the estate playbook — minimum skill that closes the gap, nothing
speculative. Australian English in all generated content.
Hard refusals (§A): forge will not emit a skill that executes attacker-controllable
input, ships a destructive default action, contains offensive/exploit code, or whose
purpose is to avoid, weaken, or probe a safeguard. On stop_reason:"refusal" during
any generation subtask: re-dispatch that subtask to Opus 4.8 (Agent with
model: "opus") — fall back, never evade.
Phases
- Discovery. State the capability gap in one sentence + who invokes the skill and
when. Done when: gap + invoker + trigger written down.
- Spec gate. Run
new-spec (grounded spec, not a template) — no skill without an
approved spec.md. Done when: the human has approved spec.md.
- Design. Lightest viable archetype per the authoring standard (command-skill /
agent-role / plain-technique); depth pushed to ; every step gets a
completion criterion. design fits the frontmatter schema and ≤200-line cap.
