From angelo-skills
Self-interrogation that resolves the technical forks in a plan YOU must decide, using the user's documented engineering principles/mantras as the adjudicator. Use when the user delegates a technical decision ("you decide", "decide singur", "the technical part is yours", "grill yourself"), or when a design session hits a technical branch the user can't adjudicate.
How this skill is triggered — by the user, by Claude, or both
Slash command
/angelo-skills:grill-yourselfThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<what-to-do>
You play BOTH roles: interrogator and respondent. Walk down every branch of the design tree and resolve each fork yourself, using the user's principles as the decision authority — do not ask the user to adjudicate technical merit. You grill yourself; the principles own the answers.
Escalate to the user only when a fork is genuinely a product/business call, or when two principles irreconcilably conflict. Otherwise: decide, cite the principle, move on.
The principles ("mantras") are the adjudicator, so load them before grilling. They are user-defined, per project/company — never bundled with this skill. Resolution order:
Principles doc: docs/PRINCIPLES.md)
— explicit override wins.docs/PRINCIPLES.md (or PRINCIPLES.md at repo root) — canonical, numbered principles.docs/adr/ — decisions that already instantiate a principle. Default to standing — don't
relitigate them casually. But they are versioned law, not bedrock: see the lex
posterior rule at the end of §1.CONTEXT.md — domain glossary (terms must stay consistent).Never duplicate the principle text into this session or the plan — reference PRINCIPLES §N.
If no documented principles exist, stop and say so: ask the user to supply or confirm the
authority (a principles doc, or ad-hoc rules for this session). Do not invent house principles.
For each unresolved fork in the plan, in dependency order:
adversarial-debate skill is installed, invoke it (Optimist vs Devil's Advocate
subagents, independently researched, points of clash surfaced). If not installed — or for a
cheap, already-clear fork — steelman the strongest opposing case inline yourself. Either
way: if you can't make the opposing case, you haven't understood it.decision → chosen → PRINCIPLES §N / evidence → discarded alternative + why.Lex posterior — a newer, better-adjudicated decision repeals an older ADR. ADRs are versioned decisions, not laws of nature; the whole point of continuing to decide is to supersede what no longer holds (like statute: lex posterior derogat priori). So an existing ADR is evidence and default, never a veto. When your fresh adjudication — same principles, more context — lands on a more correct / more normalized answer than an accepted ADR, supersede or amend it; do not defer to it and fragment the better model to "respect" the old one. That deference is a failure mode: it produces incoherent compromises that satisfy neither the old decision nor the right one. The bar is merit, not age — if the older ADR is still the best answer, keep it; if your new one is better under the principles (esp. coherence/single-SoT, correctness-over-cost, fix-the-shape), repeal it. When you do repeal:
supersedes ADR-NNNN §DX → because <principle> + <new context>.Status: line with a dated "amended/superseded by
ADR-MMMM §DX" pointer and cross-link both ways. Never silently contradict a live ADR; never
rewrite its body (the historical decision stays legible — you repeal, you don't falsify).Escalate the repeal to the user (§2) only if it's also a product/business call — not merely because the old ADR was "already accepted."
Bundle escalations; don't drip one trivial question at a time. Everything else: decide.
PRINCIPLES §N.Every branch is resolved, the decision log is complete, and hard-to-reverse calls have ADRs. Don't keep grilling resolved branches; don't leave a fork silently unmade.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub angeloneacsu/skills --plugin angelo-skills