Defame1297
7e3cb90359
Grills intent, classifies target artifact type (skill/agent/plugin/marketplace entry) against a fully descriptive table, then routes to the matching author skill via fork subagent (falling back to inline when fork is unavailable or the flow needs live interaction). Adds an independent clean-context audit recheck after each skill/agent route, looping author-then-audit until the recheck comes back clean, since the author skill's own inline audit shares context with the work it verifies. Updates CONTEXT.md's Skill composition entry to describe this recheck loop and adds forge's provenance chain (references/sources.md). Refs Defame1297/holocron#61 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
forge
Guided entry point for building or improving something in kyberforge when the target artifact type isn't decided yet.
What it does
Grills the user's intent via bin:grill-with-docs (inline, interactive) against this repo's CONTEXT.md and docs/adr/, classifies the target artifact type (skill, agent/subagent definition, plugin, or marketplace entry), announces the classification, then routes to the matching author skill — chaining more than one, in dependency order, if the intent spans multiple artifact types.
Author-skill invocation defaults to a fork subagent (inherits the grilled-intent context) and falls back to inline when forking isn't possible or the routed flow needs live user interaction (clarifying questions, a HITL gate). After a skill-author or agent-author route finishes — each already closes out with its own inline audit — forge spins up a separate clean-context subagent to independently re-run the matching audit skill (skill-audit / agent-audit) as a distinct check on the finished artifact, not a duplicate of the inline one. If that clean audit turns up any unresolved finding, forge loops — re-invoke the author skill to resolve it, re-run the clean audit — until the clean audit comes back with nothing unresolved. plugin-author and marketplace-author routes get no recheck: they have no audit counterpart, and their real terminal check (claude plugin validate) is already part of their own flow.
Before you start
Have a rough idea of what you want to build or change. forge doesn't require you to already know whether it's a skill, agent, plugin, or marketplace entry — that classification is its job.
Usage
/forge
Skip forge and call the target skill directly (/skill-author, /agent-author, /plugin-author, /marketplace-author) when you already know the artifact type.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
references/sources.md |
Provenance chain — research sources that informed this skill |
Routes to
| Artifact type | Skill |
|---|---|
| Skill | kyberforge:skill-author |
| Agent / subagent definition | kyberforge:agent-author |
| Plugin | kyberforge:plugin-author |
| Marketplace entry | kyberforge:marketplace-author |