holocron/plugins/kyberforge/.apm/skills/apm-workflow/SKILL.md at 5d0f988ed8260d8cf4e9d65b527efdad07760107

Files

Defame1297 965208bddd fix(kyberforge): resolve PR #144 review and audit round 2

- factory-audit: ./ and bare/absolute script checks scoped to command
  position (no false FAILs on ./src or printf); hook sources limited to
  .apm/hooks or package-root hooks/; Kiro-aware lowercase events;
  unfilled template placeholders FAIL; repo-only instructions FAIL at
  any scope; Vale description FAIL documented; bats 367 -> 378
- primitive-author: split-quote/spaced paths and handler-less entries
  promoted to Must; Step 4.2 renders into a scratch consumer instead of
  a no-op dry run; dispatch and gate hand-off trimmed
- apm-workflow 1.0.2: mutual boundary with primitive-author
- forge: no double package bump; gotcha wording
- skill-author: create keeps seeded 0.1.0 (ADR-0022); portable,
  retry-safe new-skill.sh; template and flow consistency fixes
- hook docs: cite the ADR-0019 correction; guard caveat

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi

2026-09-28 20:50:22 +00:00

1.9 KiB

Raw Blame History

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.

version

Gotchas

apm experimental enable registries must run before a registries: block or registry.* config takes effect in any flow; without it they silently do nothing.
apm.yml's type: is never checked against what .apm/ holds, so apm install and apm compile can exit 0 shipping none of the primitives you expected. 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`)	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.

1.9 KiB Raw Blame History

Gotchas

Step 1 — Dispatch

Step 2 — Execute

1.9 KiB

Raw Blame History