Add an optional activationKey to the feature role of capability.json — the dotted config key that gates the whole capability (e.g. graphify.enabled). gen-capability-registry validates it (non-empty string, reserved-name guard, must be declared in the capability's own config slice, feature-only) and emits it per-capability in the generated registry. Declared on graphify + intel. No runtime consumption yet (resolver wiring lands in #1305). Part of #1302. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
31 lines
833 B
JSON
31 lines
833 B
JSON
{
|
|
"id": "graphify",
|
|
"role": "feature",
|
|
"title": "Knowledge graph",
|
|
"description": "Build, query, and inspect the project knowledge graph in `.planning/graphs/`; exposes graphify CLI subcommands (build, query, status, diff) and the /gsd-graphify skill.",
|
|
"tier": "full",
|
|
"requires": [],
|
|
"runtimeCompat": { "supported": ["*"], "unsupported": [] },
|
|
"skills": ["graphify"],
|
|
"agents": [],
|
|
"activationKey": "graphify.enabled",
|
|
"config": {
|
|
"graphify.enabled": {
|
|
"type": "boolean",
|
|
"default": false,
|
|
"description": "Enable the graphify knowledge-graph command + skill."
|
|
}
|
|
},
|
|
"commands": [
|
|
{
|
|
"family": "graphify",
|
|
"module": "graphify-command-router.cjs",
|
|
"router": "routeGraphifyCommand"
|
|
}
|
|
],
|
|
"hooks": [],
|
|
"steps": [],
|
|
"contributions": [],
|
|
"gates": []
|
|
}
|