Skip to content

skill-quality/plugin-philosophy: aihero course lane 8: invocation-mode doctrine and evidence-driven fleet re-grade #2910

Description

@kyle-sexton

Context

Steering-section extension of the AI Hero course vetting effort — contract in docs/topics/pocock-course-lanes/PLAN.md (branch claude/plan-mode-discussion-55kszx); lanes 1–6 are #2899#2904; sibling steering lane is #2909. Owns the third gap from the 2026-08-17 writing-for-agents re-evaluation: invocation-choice doctrine is absent, and our de facto posture is the opposite of upstream's default, with neither ever argued.

Fleet reality (measured 2026-08-17): 211 top-level skills — 137 disable-model-invocation: false, 17 missing the key entirely, 57 true (almost entirely the setup skills plus a few maintainer-only skills). The setup convention is enforced by convention, documented nowhere. The skill-quality:check listing-budget instrument measures the aggregate description cost, but no decision rubric exists for choosing a skill's invocation mode. Upstream's SKILL-MECHANICS.md default is the inverse: user-invoked unless the agent must reach the skill autonomously or another skill needs it. The router-skill pattern was rejected only as the ask-matt port ("marketplace shape differs") — never evaluated as a pattern for our 57+ user-invoked skills.

Session decision (user-confirmed 2026-08-17): evidence-driven rubric. Neither upstream's user-invoked default nor our model-invoked default is assumed correct. The rubric weighs: autonomous-reach need, cross-skill reach (invocation-reach invariant), real trigger-hit evidence, listing-budget data, cognitive load on the human, and surface coverage.

Evidence that must feed the rubric:

Scope constraint: ADR 0005 (bound instruction-surface work by question, not population). Shape as rubric-first + question-bounded application, not an unbounded 211-skill sweep. Reconcile with docs/topics/context-engineering-claude-5/ prior art (its design/skill-inventory.md population-derivation traps and the discipline:sweep-all router precedent).

Proposed work

  • Open with /planning:interview me per contract; lane discusses and decides — implementation leaves as filed work items
  • Write the invocation-mode decision rubric and pick its one home (PLUGIN-PHILOSOPHY component stances, a convention-registry owner doc, or playbooks:skill-authoring — decide, don't duplicate)
  • Document the existing setup-skill convention (currently undocumented)
  • Decide the 17 skills missing the disable-model-invocation key (explicit value or documented default)
  • Evaluate the router-skill pattern on its merits (cognitive-load relief for user-invoked skills; claude-ops:inventory and docs/SKILL-CHEAT-SHEET.md as existing partial answers)
  • Apply the rubric question-bounded (e.g. per plugin or per workflow stage), using skill-quality:check listing-budget before/after as the measurement
  • Verify and disposition the invocation-reach invariant tracked strand

Acceptance criteria

  • Adopt/reject-with-reason/track-on-event decision rows in docs/upstream/aihero-course.md for lessons 3 (What Are Agent Skills), 4 (Write A Skill — invocation half), 5 (User Vs Project Skills, incl. the cloud-scope caveat)
  • Rubric written, homed in exactly one place, and cross-linked from the surfaces that need it
  • Setup-skill convention documented; 17 missing-key skills decided
  • Router-skill pattern verdict recorded (adopt/reject-with-reason)
  • Invocation-reach invariant verified against official docs; SSOT tracked-strand disposition recorded
  • Fleet re-grade scoped and either executed question-bounded or filed as follow-on work items

References

Metadata

Field Value
Category unspecified
Area skill-quality, docs (philosophy, conventions), all plugins (fleet)
Ecosystem unspecified

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.priority: mediumReal value, no hard deadline; normal backlog flow.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions