Cycle 2.5 Framing-Drift Acknowledgment: The initial framing of this epic incorrectly assumed we needed to retain the triggers: field for backwards compatibility. A 4-layer contract-correction audit (V-B-A) revealed that retaining it causes contract drift. This ticket has been amended in-place to mandate the removal of the triggers: field.
Context
Per Discussion #11419 (AGENTS.md Progressive Disclosure) Cycle 2.5 graduation, Phase B shifts focus to description-router hardening. Empirical Antigravity V-B-A revealed that only the name and description fields from SKILL.md frontmatter are loaded into the agent context; the triggers: field is silently dropped. To safely remove the §21 Workflow Skills table from AGENTS.md (Phase C) without causing "agent amnesia," the routing information must be salient in the description field.
The Problem
The triggers: field in .agents/skills/**/*.md cannot be relied upon by cross-harness agents (specifically Antigravity and Codex) to know when to invoke a skill. If we delete §21 from the L1 anchor, agents will stop invoking critical skills like ticket-create or pull-request.
The Architectural Reality
- We must REMOVE the dead
triggers: field and codify description as the cross-harness router (per Antigravity/Codex/Claude V-B-A: only name + description are loaded).
- We must HARDEN the
description: field by explicitly merging the trigger criteria into it, making it "trigger-aware" for cross-harness loading.
The Fix
- Iterate over all 25 skills in
.agents/skills/.
- Update the
description: field in the YAML frontmatter to include the specific trigger conditions (e.g., "Use this skill when...").
- Remove the
triggers: field.
Discussion Criteria Mapping
- Maps to Discussion #11419, Phase B (Cycle 2.5 Refinement).
Acceptance Criteria
Out of Scope
- Phase C (deletion of §21 from
AGENTS.md) is excluded until Phase B post-merge verification confirms salience.
Origin Session ID
188acb85-b41e-435c-94ee-0cc9944d4c97
Context Per Discussion #11419 (AGENTS.md Progressive Disclosure) Cycle 2.5 graduation, Phase B shifts focus to description-router hardening. Empirical Antigravity V-B-A revealed that only the
nameanddescriptionfields fromSKILL.mdfrontmatter are loaded into the agent context; thetriggers:field is silently dropped. To safely remove the §21 Workflow Skills table fromAGENTS.md(Phase C) without causing "agent amnesia," the routing information must be salient in thedescriptionfield.The Problem The
triggers:field in.agents/skills/**/*.mdcannot be relied upon by cross-harness agents (specifically Antigravity and Codex) to know when to invoke a skill. If we delete §21 from the L1 anchor, agents will stop invoking critical skills liketicket-createorpull-request.The Architectural Reality
triggers:field and codifydescriptionas the cross-harness router (per Antigravity/Codex/Claude V-B-A: onlyname+descriptionare loaded).description:field by explicitly merging the trigger criteria into it, making it "trigger-aware" for cross-harness loading.The Fix
.agents/skills/.description:field in the YAML frontmatter to include the specific trigger conditions (e.g., "Use this skill when...").triggers:field.Discussion Criteria Mapping
Acceptance Criteria
SKILL.mdfiles have theirdescription:field updated to include invocation triggers.triggers:field is removed across all 25SKILL.mdfiles.Out of Scope
AGENTS.md) is excluded until Phase B post-merge verification confirms salience.Origin Session ID 188acb85-b41e-435c-94ee-0cc9944d4c97