Designer Drift Report — 2026-08-04
Summary
2 drift items found across 2 categories: incomplete network ecosystem mapping and missing new frontmatter fields in the generation template.
Drift Items
View Drift Items by Category
Network Ecosystem Coverage
- Source:
.github/aw/network.md
- Missing from:
SKILL.md (designer.md) network mapping table
- Details: The network mapping table in the Decision Heuristics section covers most ecosystem identifiers but never lists the invalid-shorthand corrections documented in network.md:
npm -> node, pypi/pip -> python, cargo -> rust, gem/gems -> ruby, nuget -> dotnet, maven/gradle -> java, composer -> php, docker -> containers, localhost -> local. Users who prompt with these common shorthand terms are not guided to the correct identifier.
- Suggested fix: Add an "Invalid Shorthands" quick-reference note or row set to the Network Mapping table in designer.md mirroring network.md's shorthand-correction table, so the designer catches and corrects common wrong terms like
npm, pip, cargo, docker, etc.
Frontmatter Field Coverage
- Source:
.github/aw/syntax.md (index -> syntax-tools-imports.md, skills.md, lsp.md, evals.md)
- Missing from: both
SKILL.md (designer.md) and the agent file
- Details: syntax.md indexes three newer top-level frontmatter fields --
skills:, lsp:, and evals: (BinEval binary evaluations) -- none of which appear anywhere in designer.md's Interview Framework, Decision Heuristics, or Generation Template. The designer has no phase or heuristic that surfaces these fields to users, and the Generation Template skeleton does not include them as optional entries.
- Suggested fix: Add a brief heuristic row (e.g. "uses inline skills for delayed instructions" ->
skills:, "needs code navigation via LSP" -> lsp:, "needs binary evaluation gating" -> evals:) and mention these as optional Generation Template fields when relevant, with a reference link to skills.md/lsp.md/evals.md.
No Drift
- ✅ Trigger coverage — all trigger types from triggers.md are represented in the designer trigger mapping table
- ✅ Safe output coverage — all safe-output operation types from safe-outputs.md and all-safe-output-types.txt are represented (mapped by intent phrase, covering add-comment through noop/missing-tool/missing-data/report-incomplete)
- ✅ Tool mode coverage —
gh-proxy, local, cli-proxy, and bounded-queries tool modes are represented
- ✅ Pattern coverage — all 19 named patterns from patterns.md (MonitorOps, BatchOps, ChatOps, DailyOps, DispatchOps, LabelOps, MultiRepoOps, Orchestration, ProjectOps, ResearchPlanAssignOps, CorrectionOps, SideRepoOps, SpecOps, TrialOps, WorkQueueOps, DeterministicOps, CentralRepoOps, Monitoring with Projects) are referenced
- ✅ Stale references — no references to removed docs/fields found in designer.md
- ✅ Recent changes sync — the most recent reference doc commit (87b330e, opencode integration refactor) is also the most recent designer file commit, so no unsynced recent change was detected
Methodology
Compared outlines of 8 reference docs against both designer files (.github/aw/designer.md and .github/agents/interactive-agent-designer.agent.md).
Reference doc commits (last 7 days): 1
Designer file commits (last 7 days): 1
Generated by 🔍 Designer Drift Audit · auto · 54.6 AIC · ⌖ 2.31 AIC · ⊞ 7.4K · ◷
Designer Drift Report — 2026-08-04
Summary
2 drift items found across 2 categories: incomplete network ecosystem mapping and missing new frontmatter fields in the generation template.
Drift Items
View Drift Items by Category
Network Ecosystem Coverage
.github/aw/network.mdSKILL.md(designer.md) network mapping tablenpm->node,pypi/pip->python,cargo->rust,gem/gems->ruby,nuget->dotnet,maven/gradle->java,composer->php,docker->containers,localhost->local. Users who prompt with these common shorthand terms are not guided to the correct identifier.npm,pip,cargo,docker, etc.Frontmatter Field Coverage
.github/aw/syntax.md(index -> syntax-tools-imports.md, skills.md, lsp.md, evals.md)SKILL.md(designer.md) and the agent fileskills:,lsp:, andevals:(BinEval binary evaluations) -- none of which appear anywhere in designer.md's Interview Framework, Decision Heuristics, or Generation Template. The designer has no phase or heuristic that surfaces these fields to users, and the Generation Template skeleton does not include them as optional entries.skills:, "needs code navigation via LSP" ->lsp:, "needs binary evaluation gating" ->evals:) and mention these as optional Generation Template fields when relevant, with a reference link to skills.md/lsp.md/evals.md.No Drift
gh-proxy,local,cli-proxy, andbounded-queriestool modes are representedMethodology
Compared outlines of 8 reference docs against both designer files (
.github/aw/designer.mdand.github/agents/interactive-agent-designer.agent.md).Reference doc commits (last 7 days): 1
Designer file commits (last 7 days): 1