CassioRoos
- 16 skills
- 0 followers
- 17 hours ago last updated
- ▌ Godfly · cassioroos bundleAdversarial collaborator who pushes back like a senior engineer - the default adversarial reviewer. Surfaces hidden assumptions, grounds every challenge in evidence, presents real counterpoints with proven alternatives, drives toward synthesis, and records settled claims as verdict nodes in docs/verdicts/ so an investigation is never paid for twice. Challenges code, architecture, PRs, incident fixes, product strategy, and plans. Use when user wants to "challenge this", "review this", "stress test", "poke holes", "pushback", "call my bullshit", radical candor, hard review, asks whether a claim was already settled, or types *spar, *review, *assumptions, *alternatives, *fail, *pre-mortem, or *invert. For constructing the case FOR the alternative use devils-advocate; for attack-path launch review use red-blue-review; for "what am I missing" use assumptions-check.
- ▌ Handoff · cassioroos bundleCreate a compact handoff document for another Codex session or agent to continue the work. Use when the user asks for a handoff, next-agent context, continuation note, session summary, resume brief, or wants another agent to pick up without reconstructing the thread.
- ▌ Mean QA · cassioroos bundleAdversarial QA campaigns with persistent .proof evidence and re-runnable cases. Use to QA a feature, test a browser flow, verify a change or staging build, design a test campaign, or prepare a PR verification section. Local evidence is mandatory; publishing is a separate authorized action.
- ▌ Gauntlet · cassioroosEmpirically test whether a skill actually improves model output — before trusting it. Runs a controlled experiment: planted-flaw fixture, no-skill control arm, skill arm(s), optional cross-model arms via installed CLIs, blind judging with shuffled labels, and a pressure test for verdict stability. Produces adopt/fix/reject recommendations and evidence-backed proposed changes; adoption is separately authorized. Use for "test this skill", "validate the skill", "does this skill help", "run the gauntlet", "skill A/B", or "eval this skill". Not a mandatory benchmark for routine edits or a substitute for a setup audit.
- ▌ Morpheus · cassioroos bundleSecond opinion and final verdict for engineering decisions. Challenges a plan, design, PR, claim, fix, or bug theory with cited evidence, steelmans the user's position first, asks when an assumption would flip the verdict, labels how each claim is known, and always lands on a verdict or a recommended option with tradeoffs. Use when the user says "challenge this", "review this", "poke holes", "stress test", "call my bullshit", "second opinion", "should I", "give me options", "what do you think", or when the orchestrator holds a non-trivial recommendation and wants pushback before committing. Includes focused troubleshooting and research guidance; deployment watches are explicit-only. Not for formatting or trivia.
- ▌ Safe Ops · cassioroos bundleSafely perform authorized remote, destructive or security-relevant operations, including Git push/merge, releases, infrastructure and data mutations, credential changes and bulk cleanup. Not required for routine read-only inspection or ordinary scoped repository edits.
- ▌ Toolshed · cassioroos bundleToolshed — durable, model-agnostic working state for ONE coding task (feature, investigation) as docs/work/SLUG/ under docs/, DELETED at close. Seeds STATE + decisions/questions/evidence with grades and reproduction commands. Use for "start a toolshed", "seed the task", "/toolshed start|resume|session-end|close", or "where were we". Session end = thin STATE update. Full packet only when explicitly requested or on close/ship gates. Evidence may also live in PRs, CI, mean-qa, morpheus, monitoring runbooks — toolshed is a state shelf, not the whole environment. Pair with morpheus, handoff, safe-ops, spec-adr-builder.
- ▌ Deep Dive · cassioroosDeep technical investigation for complex systems, unfamiliar codebases, architecture, data flows, and dependencies - when the system works but is not understood. Use when the user asks for a deep dive, investigate deeply, map the system, understand how it works, break down complexity, or produce an evidence-backed technical brief. If something is failing right now use the troubleshooting reference in morpheus; for a past incident timeline and contributing factors use premortem-postmortem.
- ▌ Devils Advocate · cassioroos bundleArgue the opposing position: construct the strongest possible case for the alternative or against a pending decision. Use for make the case for NOT doing this, argue the other side, steelman the alternative, what would critics say. Produces an opposing-counsel brief, not a code review. For evidence-based critique of your own work, plans, or PRs use morpheus; for attack-path and launch-readiness review use red-blue-review; for imagining failure before starting use premortem-postmortem.
- ▌ Red Blue Review · cassioroosExamine concrete attack and failure paths, then design prevention, detection, containment and recovery. Use for red team, blue team, threat models, attack paths or defense plans. General engineering review belongs to morpheus; component failure inventories belong to failure-analysis.
- ▌ Failure Analysis · cassioroos bundleIdentify and prioritize concrete component and dependency failure modes, their consequences, containment and recovery. Use for FMEA, reliability assessment, single points of failure, or "how could this fail". General engineering verdicts belong to morpheus; active debugging to the troubleshooting reference in morpheus; past incident analysis to premortem-postmortem.
- ▌ Spec Adr Builder · cassioroosGenerate or review technical specs and Architecture Decision Records. Use when the user asks for specs, ADRs, RFCs, design docs, decision records, technical requirements, non-goals, alternatives, rollout, or rollback documents. For user-research requirements elicitation use user-research.
- ▌ Assumptions Check · cassioroos bundleBuild and test an explicit inventory of hidden assumptions using the Key Assumptions Check technique. Use for assumption check or what are we assuming. For general engineering review or what am I missing, use morpheus.
- ▌ Incident Validator · cassioroos bundleValidate production-incident artifacts -- investigation handovers, fix PRs, and postmortems -- against the Production Issue Resolution Standard. Runs a gate matrix with live evidence verification, interrogates the author to close gaps, and issues a closure verdict. Use when writing or reviewing an incident handover, a production-fix PR description, or a postmortem, or when asking "can this incident be closed?". Triggers on "validate this incident", "validate handover", "validate postmortem", "incident PR review", "can I close this incident". Ordinary diagnosis or code review does not trigger artifact validation. For adversarial review of the fix itself use morpheus; for causal analysis and writing the postmortem use premortem-postmortem. Verify releases using the project runbook and live read-only evidence.
- ▌ Competing Hypotheses · cassioroos bundleMap the full solution space and evaluate approaches against evidence. Based on the CIA's Analysis of Competing Hypotheses (ACH). Use for DECISIONS - choosing between technologies, architectures, or strategies - or when the user needs counterpoints and alternatives. Triggers on "what are the alternatives", "compare approaches", "which is better", "counterpoint", "other options", or any decision between multiple options. For ranking bug hypotheses during active debugging, use the hypothesis table in morpheus references/troubleshooting.md instead.
- ▌ Premortem Postmortem · cassioroosRun premortems before risky work and postmortems after incidents or failures. Use when the user asks for premortem, postmortem, incident review, retrospective, launch risk, "how will this fail", or "what killed this". Build the causal chain from evidence and produce the premortem/postmortem document with owners and verification.