kyberforge: add authoring/audit support for hooks, instructions, and prompt primitives #94
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Defame1297/holocron#94
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Surfaced by a subagent audit comparing kyberforge's authoring primitives (
skill-author,agent-author,apm-workflow,agent-audit,skill-audit) against the apm docs atplugins/kyberforge/docs/research/docs/microsoft-apm/, run as a follow-up to #90's plugin→apm conversion work. Related to but not a duplicate of #90 — that issue is about the repo's ownapm.ymlusage; this one is about gaps in kyberforge's authoring-primitive coverage (what kyberforge can help an author correctly produce).kyberforge has
skill-authorandagent-author, which cover two of apm's primitive types. It has no equivalent support for the other primitive types apm compiles:.apm/hooks/*.json,.apm/instructions/*.instructions.md, and.apm/prompts/*.prompt.md.1. No authoring/audit support for
.apm/hooks/*.jsonplugins/kyberforge/.apm/skills/apm-workflow/references/configure.mdstates hook subdirectories "must be created manually as content is migrated into them" — there is no template, script, or reference doc anywhere in kyberforge for.apm/hooks/*.json.forge/SKILL.mdlists "hook" as a buildable artifact type but routes it to the same genericapm-workflowconfigure step, which has no actual hooks content — so today it silently leads an author into a no-op.plugins/kyberforge/docs/research/docs/microsoft-apm/hooks-primitive-schema.mddocuments real per-target reconstruction gotchas an author would get wrong by hand:version:1/camelCase field naming vs. Claude's shape, plus thebash+powershellscript split${CLAUDE_PLUGIN_ROOT}placeholder rewriting in script pathsRecommended fix: add a minimal
.apm/hooks/*.jsontemplate (nested-wrapper shape) plus a reference doc covering event-name casing and script-path placeholders — or, if hooks authoring is intentionally out of scope for now, say so explicitly inforge/SKILL.mdinstead of silently routing to a step with no actual content.2. No authoring support for
.apm/instructions/*.instructions.mdor.apm/prompts/*.prompt.mdkyberforge has no author skill for these two primitive types at all. This is higher-priority than the hooks gap because Claude's compile step silently drops fields an author wouldn't know about without reading the schema docs closely:
descriptionis dropped entirely for instructions on Claude compiledescription/allowed-tools/model/argument-hint/argumentssurvive compileReference:
plugins/kyberforge/docs/research/docs/microsoft-apm/instructions-primitive-schema.mdandprompt-primitive-schema.md.Minimum fix: document these compile-time field-dropping gotchas in
apm-workflow's configure/compile reference docs so authors aren't surprised.Fuller fix: a dedicated author skill (or an extension of an existing one) for these two primitive types.
Not part of this issue (verified correct in the same audit)
agent-author/agent-audit/ADR-0016's Claude-only-field-stripping allowlist chain — spot-checked against 4 generated.agent.mdfiles across plugins, zero drift..apm/skills/<name>/— confirmed correct peragent-primitive-schema.md.agent-audit/skill-audit's hand-rolled validation — correctly scoped;apm auditexplicitly doesn't cover frontmatter/schema-level checks pertesting-and-validation.md, so this isn't a reimplementation of an existingapmcommand.