Repository navigation
refactor(architecture): give the nine map-* skills distinct, trimmed descriptions #12490
Description
Refs #7582
Outcome
The nine architecture:map-* skills stay separate leaves (components, containers, context, data, dependencies, deployment, events, flow, landscape). Each description opens with a first clause no sibling shares and is trimmed to the repository's description standard, with no loss in triggering.
Scope is option 3, chosen by the owner on 2026-11-03 (decision: #12490 (comment)). Merging into one router skill and its sized waves are dropped.
Done when
- No two
plugins/architecture/skills/map-*/SKILL.mddescriptions share a first clause, and/skill-quality:checkpasses on each. - Each changed description passes a two-labeler
/docs-hygiene:compress comparemeaning diff before any paid run. - Triggering is re-measured on
plugins/architecture/probesbefore and after (plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md, "Cutting text", steps 3 and 4): no lost positive and no new false fire. A description that fails keeps its main text. -
ls -d plugins/architecture/skills/map-* | wc -lis still 9, andscripts/validate-plugins.shpasses.
Out of scope
- Skill bodies, and the
code-metrics:audit-*descriptions (refactor(code-metrics): give the six audit-* skills distinct, trimmed descriptions #12491).
Related
- skill-quality: skill authoring, quality and catalog #7582 (parent), refactor(code-metrics): give the six audit-* skills distinct, trimmed descriptions #12491 (same scope for
code-metrics:audit-*), refactor(plugins): give the three non-prerequisite check skills distinct names so no check leaf remains #12489 (owner: no rename for Cursor), perf(session-flow): run the description trim pilot and measure skill visibility #11954 (trimmed descriptions held triggering).
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
confirmed
Activity
github-actions commentedon Nov 2, 2026
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
#12490 (comment)
This decision settles the open questions. The issue body now matches option 3: it keeps the nine map-* skills and gives each a distinct, trimmed description. The probe re-measurement is a paid run, so it may need a host run. That doesn't block triage of the other done-when items. I found no duplicates.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 2, 2026
The latest triage verdict holds nothing: admission moved the issue to
status: confirmed; its comment says why.melodic-automation-lanes commentedon Nov 2, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: Consolidate the nine architecture:map-* skills, most likely into one architecture:map router skill with nine actions, delivered in waves each under 262144 bytes after a sized wave plan.
Related work
Open questions
RECOMMENDED: Option 1: one architecture:map router SKILL.md plus actions/, so the final map-* directory count is 0 and the done-when count check has a fixed value. Basis: The nine map-*/SKILL.md leaves exist under plugins/architecture/skills; the issue cites the D107 router standard; the #11954 data and eval baselines are not in the issue, so this is judgment.
RECOMMENDED: The owner fixes option 1 now with a Decision recorded comment. The plan then only sizes waves, and the lane can overturn it only if the #11954 data contradicts it. Basis: judgment
ls -d plugins/architecture/skills/map-* | wc -lreach?RECOMMENDED: 0 under option 1, because the router would be named architecture:map, not map-*. Under option 2 it would be the number of grouped skills, and under option 3 it stays at 9. Basis: judgment
Sources read
To answer, post a comment that starts with this line:
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.13 remaining items
kyle-sexton commentedon Nov 3, 2026
Decision recorded. Owner answer, given in the lane 2 session on 2026-11-03: "Go with recommendations."
The recommendation it answers (lane 2, Q2): re-scope both consolidations to option 3. Keep the leaf skills; give each a distinct first description clause and a description trimmed to the repository's description standard; measure triggering for no loss per
plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md. The merge into one router skill (option 1) and its waves are dropped.Basis: the only written reason for consolidating was picker fit in Cursor and Claude Code. The owner ruled Cursor out ("I wouldn't change ours if it's just to accommodate cursor", #12489). Claude Code always lists every skill name and drops only descriptions on budget overflow, which users tune with
skillListingBudgetFractionandskillOverrides(Skill descriptions are cut short, read 2026-11-03). One merged description would also have to carry every view's triggers under a 1,536-character cap. #11954 showed trimmed descriptions hold triggering (0.979 to 0.984).Next on this issue: its body's done-when items still describe the consolidation; they are rewritten to the option-3 scope before work starts.
[-]refactor(architecture): consolidate the nine map-* skills (plan sized waves first)[/-][+]refactor(architecture): give the nine map-* skills distinct, trimmed descriptions[/+]kyle-sexton commentedon Nov 3, 2026
Body and title rewritten to the option-3 scope recorded above. Dropped: the wave plan, the patch-cap sizing and the "Blocked by #12486" line (#12486 is closed, and keeping the leaves no longer depends on it).
kyle-sexton commentedon Nov 4, 2026
refactor(architecture): keep the before text where no control detecte…