agent-adoption-triagelisted
Install: claude install-skill shimo4228/agent-adoption-triage
# Agent Adoption Triage
Most "should we build an agent?" conversations start from the architecture ("we'll use a ReAct loop") and work backwards to the justification. This skill inverts that: **route the work first, pick the architecture second.** The question is not whether an agent *can* do the work — current models usually can. The question is whether **accountability can still be distributed after you deploy it**, and that is decided by which quadrant the work belongs to, not by model capability.
This skill is the "how" counterpart to two ADRs and the quadrants navigator in the [Agent Attribution Practice (AAP)](https://github.com/shimo4228/agent-attribution-practice) research line (concept DOI [10.5281/zenodo.19652013](https://doi.org/10.5281/zenodo.19652013)):
- [AAP ADR-0009 Triage Before Autonomy](https://github.com/shimo4228/agent-attribution-practice/blob/main/docs/adr/0009-triage-before-autonomy.md) — the problem-space triage (Q1–Q4)
- [AAP ADR-0010 Phase Separation](https://github.com/shimo4228/agent-attribution-practice/blob/main/docs/adr/0010-phase-separation.md) — the design/operation Phase axis (Q0)
- [AAP `docs/quadrants/`](https://github.com/shimo4228/agent-attribution-practice/tree/main/docs/quadrants) — decision tree, governance mapping, case studies, anti-patterns
The ADRs cover the "why." This skill is the runnable version: walk the five questions, land on a quadrant, apply that quadrant's governance set, and record the answers.
---
## The Business