Defame1297
dac9cad912
skill-audit loaded roughly 4,268 words of rubric on every run, most of it criteria for findings a clean skill never triggers. The auditing guidance moves into finding-criteria.md, read only when a finding is actually raised, cutting a clean audit to about 999 words. The named-skill exemption is replaced with properties, so the rubric stops carrying a list that ages the moment a skill is renamed. apm-workflow's `type:` trap sat in one flow while biting several, so it is promoted to a common gate reachable from all of them; its claim to be self-contained was untrue once it started routing to apm-install. skill-author's contract had drifted from body-discipline.md and is realigned, and agent-audit's field inventory is brought in line with the same split.
41 lines
3.0 KiB
Markdown
41 lines
3.0 KiB
Markdown
# forge
|
|
|
|
Guided entry point for building or improving something in any plugin of this repo when the target artifact type isn't decided yet.
|
|
|
|
## What it does
|
|
|
|
Grills the user's intent via `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. `apm-workflow` routes (plugin, marketplace entry) get no recheck: they have no audit counterpart, and no automatic terminal check either — `apm audit` is a separate `apm-workflow` action, not a closing step of the configure or marketplace flow — so forge verifies those routes by reading the written manifest back against the grilled intent.
|
|
|
|
## 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`, `/apm-workflow`) when you already know the artifact type.
|
|
|
|
## Files
|
|
|
|
| File | Loaded when |
|
|
|------|-------------|
|
|
| `SKILL.md` | Always — Gotchas, the grill step, the classification dispatch table, and the gates common to every route |
|
|
| `references/author-routes.md` | The intent classifies as a skill or an agent/subagent definition — fork-vs-inline judgment and the two-tier verification loop |
|
|
| `references/apm-routes.md` | The intent classifies as a plugin or a marketplace entry — always-inline invocation, why these routes get no clean-context recheck, and the manual read-back that stands in for one |
|
|
| `references/version-bump.md` | A finished route left the owning package's version unbumped — walk-up rule and the clean-context bump brief |
|
|
| `references/sources.md` | Never loaded at runtime — provenance chain for the research sources that informed this skill |
|
|
|
|
## Routes to
|
|
|
|
| Artifact type | Skill |
|
|
|---|---|
|
|
| Skill | `skill-author` |
|
|
| Agent / subagent definition | `agent-author` |
|
|
| Plugin | `apm-workflow` (configure) |
|
|
| Marketplace entry | `apm-workflow` (marketplace) |
|