Defame1297
239ea41842
skill-audit's cross-plugin path check now also recognizes .apm/skills/ <other-skill>/ as a breaking reference shape, alongside the existing plugins/<plugin>/skills/<other-skill>/ pattern — the APM-native equivalent of the same cache-isolation problem. forge.md's Step 4 plugin-version-bump detection switches from "any directory containing a plugin.json" to the same apm.yml+type: walk-up used elsewhere in this batch, and hands off to apm-workflow (bump the single apm.yml version) instead of the deprecated plugin-author. Refs: #89
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 |