Defame1297
1e8f0571cf
- reach the MCP ${VAR} secrets rule from the compile flow
- restore the Gotcha remedy for type: coverage
- route .apm/instructions and .apm/prompts to primitive-author
- agent-author: add the primitive-author boundary and the already-bumped
skip, bump to 1.0.4
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi
2.1 KiB
2.1 KiB
name, description, metadata
| name | description | metadata | |||||||
|---|---|---|---|---|---|---|---|---|---|
| apm-workflow | Use when authoring, installing or publishing an apm package, its apm.yml and dependencies, or a marketplace, even if "apm" goes unsaid. Not the apm binary or an agent runtime -> apm-install. Not a hook, instruction or prompt file -> primitive-author. |
|
Gotchas
apm experimental enable registriesmust run before aregistries:block orregistry.*config takes effect in any flow; without it they silently do nothing.apm.yml'stype:is never checked against.apm/, soapm installandapm compilecan exit 0 shipping none of the expected primitives. Settype:to cover every primitive shipped; confirm the deployed output, not the exit code (references/configure.md).
Step 1 — Dispatch
| Condition | Flow | Reference |
|---|---|---|
Author or edit apm.yml, or scaffold a new package (apm plugin init); skill, agent, hook, instruction or prompt content goes to the matching author skill |
configure | references/configure.md |
Resolve or fetch the dependencies apm.yml declares (apm install, apm install [PACKAGE_REF]) |
install | references/install.md |
Build a marketplace, register a package into it (local: hand-edit apm.yml; remote: apm marketplace package add), or register someone else's as a consumer (apm marketplace init/check/package add/add) |
marketplace | references/marketplace.md |
Generate per-target output, bundle, or publish (apm compile, apm pack, apm publish) |
compile | references/compile.md |
Validate integrity/policy or wire a CI gate (apm audit, apm audit --ci) |
audit | references/audit.md |
Read the reference file matching the resolved flow — it carries that flow's own traps, and names a sibling file wherever one flow genuinely depends on another's detail.
Step 2 — Execute
Follow the matched reference file's instructions. Report back which apm command(s) were run (or drafted, if the user asked for a plan rather than execution) and their outcome.