You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(architecture): add a conventions lens to /architecture:improve #11126
Type: Feature Summary:/architecture:improve gains a conventions lens that derives the codebase's building blocks, owners and feature blueprints and proposes rules, recording none without a yes.
Current behavior:
plugins/architecture/skills/improve/SKILL.md has two lenses, deepening and boundaries (actions/deepening.md, actions/boundaries.md). Its "Adding a lens" section says a new lens is an actions/<lens>.md playbook, a research/<lens>/ folder and one Actions row.
A conventions lens, added per "Adding a lens": it derives building blocks, owners and feature blueprints from the code and proposes rules.
It records no rule without the person's yes. Routing of what it finds: boundary rules to the architecture concern file; findings to /corrections:codify; structural paved-path entries to /discipline:reuse-or-replace.
Done when
/architecture:improve documents the conventions lens: an Actions row, actions/conventions.md and research/conventions/.
Eval cases cover: a proposal made and nothing written without a yes; a boundary rule routed to the architecture concern file; a finding routed to /corrections:codify; a paved-path entry routed to /discipline:reuse-or-replace.
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: add a conventions lens to /architecture:improve, following the "Adding a lens" steps. That means an Actions row, actions/conventions.md and research/conventions/. The lens proposes rules and records none without a yes. It routes boundary rules to the architecture concern file, findings to /corrections:codify, and paved-path entries to /discipline:reuse-or-replace. The done-when items are checkable, and the intended outcome is clear from the issue. I found no likely duplicates among the open issues.
Activity
github-actions commentedon Oct 30, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: add a
conventionslens to/architecture:improve, following the "Adding a lens" steps. That means an Actions row,actions/conventions.mdandresearch/conventions/. The lens proposes rules and records none without a yes. It routes boundary rules to the architecture concern file, findings to/corrections:codify, and paved-path entries to/discipline:reuse-or-replace. The done-when items are checkable, and the intended outcome is clear from the issue. I found no likely duplicates among the open issues.Automated triage, applied by the lanes App.