Skip to content

refactor(architecture): give the nine map-* skills distinct, trimmed descriptions #12490

Description

@kyle-sexton

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.md descriptions share a first clause, and /skill-quality:check passes on each.
  • Each changed description passes a two-labeler /docs-hygiene:compress compare meaning diff before any paid run.
  • Triggering is re-measured on plugins/architecture/probes before 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 -l is still 9, and scripts/validate-plugins.sh passes.

Out of scope

Related

Activity

  1. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 2, 2026
  2. github-actions commented on Nov 2, 2026

    @github-actions
    Contributor

    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

    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.

    [quote truncated; the full decision is at the link]

    #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.

  3. added
    status: needs-decisionAwaiting a human or maintainer judgment call.
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 2, 2026
  4. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    The latest triage verdict holds nothing: admission moved the issue to status: confirmed; its comment says why.

  5. removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 2, 2026
  6. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    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

    1. Which consolidation target: (1) one architecture:map router with nine actions, (2) grouped skills along C4 levels, or (3) keep the leaves with distinct first clauses?
      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.
    2. Does the owner accept the plan comment choosing the target from the #​11954 measurement and eval baselines, or must the owner fix the target now?
      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
    3. What count should ls -d plugins/architecture/skills/map-* | wc -l reach?
      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

    • plugins/architecture/skills/map-*/SKILL.md: nine map skills exist (components, containers, context, data, dependencies, deployment, events, flow, landscape)
    • refine-data/context.json: no Decision recorded comment; triage recommends option 1 but marks it as needing an owner answer

    To answer, post a comment that starts with this line:

    **Decision recorded.** <answer>
    

    Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.

  7. 15 remaining items

  8. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    and removed
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 3, 2026
  9. changed the title [-]refactor(architecture): consolidate the nine map-* skills (plan sized waves first)[/-] [+]refactor(architecture): give the nine map-* skills distinct, trimmed descriptions[/+] on Nov 3, 2026
  10. kyle-sexton commented on Nov 3, 2026

    @kyle-sexton
    MemberAuthor

    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).

  11. self-assigned this
    on Nov 4, 2026
  12. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor
    No description provided.
  13. added
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    and removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Nov 4, 2026
  14. kyle-sexton commented on Nov 7, 2026

    @kyle-sexton
    MemberAuthor

    Probe result record (for #7555 criterion 2). The Q186 map-* description probe result was recorded in PR #13011's body before it merged at 2026-11-04T02:11:13Z; this posts it on its slice issue.

    Results (trigger rate / false-trigger rate / case mean; 30 runs per arm per skill; every pass VALID except as noted):

    skill before after control after vs before (noise report) control vs before verdict
    map-components 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 0.40 / 0.00 / 0.70 non-inferior, no case drop 3 case drops (1.00 to 0.00) ships new
    map-containers 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 0.73 / 0.00 / 0.87 non-inferior, no case drop 2 case drops (one 1.00 to 0.00) ships new
    map-context 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 0.53 / 0.00 / 0.77 non-inferior, no case drop 3 case drops ships new
    map-dependencies 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 0.40 / 0.00 / 0.70 non-inferior, no case drop 3 case drops (1.00 to 0.00) ships new
    map-landscape 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 0.60 / 0.00 / 0.80 non-inferior, no case drop 2 case drops (1.00 to 0.00) ships new
    map-deployment 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 0.87 / 0.00 / 0.93 non-inferior, no case drop 2 drops of one run each; did not reproduce keeps before
    map-data 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 non-inferior no detection keeps before
    map-events 0.93 / 0.00 / 0.97 (INVALID, see below) 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 non-inferior no detection keeps before
    map-flow 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 1.00 / 0.00 / 1.00 non-inferior no detection keeps before
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.priority: mediumReal value, no hard deadline; normal backlog flow.status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.

Type

Fields

Work status

confirmed

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions