role-skill-boundary-auditlisted

# role-skill-boundary-audit ## Purpose ``` Roles define who is responsible. Skills define how to perform a reusable capability. ``` Diagnostic by default: recommend, do not rewrite, unless the user or active workflow asked for the refactor. ## Conciseness mandate (always) Write the minimum that changes behavior; roles and skills spend context budget every time they load. This applies to every Role.md and skill you write, recommend, or rewrite. - Add only what adds value; cut the rest. - Keep rationale to one line, and only where it guides a judgment the rule itself does not cover. - No restatement: drop "Why" / "How to apply" / examples that repeat a rule without adding information. - `Role.md` is the tightest surface (always loaded). Load-on-demand skills may hold more detail, but still no padding. - When recommending or rewriting, target the smallest, least-verbose change that restores the boundary and preserves operative meaning. ## Classification - Keep in Role: identity, ownership, authority, responsibilities, escalation, durable boundaries for one agent. - Move to Skill: repeatable workflow, checklist, tool procedure, implementation pattern, domain method. - Move to Global Policy: must constrain every agent or session regardless of role. - Move to Workflow Docs: team process, operator/onboarding guide, durable docs humans browse outside startup context. - Move to Memory: project fact, decision, preference, or status that persists but is not a standing instructio