meta-theory
Installation
SKILL.md
Meta Arsenal — Smallest Governable Unit Methodology
⛔ TWO HARD GATES — Execute These Before ANYTHING Else
Gate 1: Clarity Check (STOP-AND-ASK)
Before selecting a Type flow, score the user's request on these 4 dimensions:
| Dimension | Clear (skip) | Ambiguous (MUST ask) |
|---|---|---|
| Scope | User specifies what files/agents/areas are involved | "Help me improve the system" / "Make it better" |
| Goal | User states the desired end state | "I want to do X" but X has multiple interpretations |
| Constraints | User mentions what NOT to change, or trade-offs | No constraints mentioned for a complex task |
| Architecture type | Clearly meta-architecture or clearly technical | Says "architecture" without specifying which kind |
Rule: If ≥2 dimensions score "Ambiguous" → you MUST ask clarifying questions before proceeding. Do NOT guess.
Ask 2-3 focused questions maximum. Example patterns:
- "You said 'improve the agents' — which agents specifically? All 8 or a subset?"