-
Notifications
You must be signed in to change notification settings - Fork 0
improvement: add disable-model-invocation to all 13 conductor skills #446
Copy link
Copy link
Open
Labels
P2High / next-up, important but not blockingHigh / next-up, important but not blockingenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersroadmap:automation-hardeningv0.7 automation contract — registry, verify tiers, agent checks, Zod runtime validationv0.7 automation contract — registry, verify tiers, agent checks, Zod runtime validationtrack:specorator-improvementImprovement to the Specorator template itselfImprovement to the Specorator template itself
Description
Metadata
Metadata
Assignees
Labels
P2High / next-up, important but not blockingHigh / next-up, important but not blockingenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersroadmap:automation-hardeningv0.7 automation contract — registry, verify tiers, agent checks, Zod runtime validationv0.7 automation contract — registry, verify tiers, agent checks, Zod runtime validationtrack:specorator-improvementImprovement to the Specorator template itselfImprovement to the Specorator template itself
Context
Part of the plugin audit in #444 (§4, R3). Zero of 37 skills currently declare
disable-model-invocation: true. The 13 conductor skills are always invoked explicitly (e.g./orchestrate,/issue:tackle) — they should never auto-trigger on casual keyword matches. Adding this flag also recovers each skill's description-budget slot (~100 tokens each × 13 = ~1,300 chars freed for other skills).Affected skills (13)
discovery-sprint,orchestrate,sales-cycle,stock-taking,project-run,project-scaffolding,portfolio-track,roadmap-management,issue-breakdown,issue-draft,tackle-issue,project-review,quality-assuranceChange
Add one line to each skill's YAML frontmatter:
Definition of Done
disable-model-invocation: truein frontmatterReferences