Design Critique
Structured design critique and plan stress-testing. Acts as a relentless interviewer drawing on pre-mortem, red teaming, and ATAM techniques to help someone think through a design or plan exhaustively. Use when the user says "grill me", "critique this", "stress-test this", "pre-mortem", "red team this", or asks to be challenged on a technical architecture, product plan, feature design, or any decision rather than validated.
MCP get_skill({ skillId: "design-critique-0e70dc9f" })Use this skill with your agent
Create a free account and connect via MCP
# Design Critique
A structured interviewing technique rooted in pre-mortem analysis, red teaming, and
ATAM (Architecture Tradeoff Analysis Method). The goal is exhaustive challenge, not
validation.
## Quick start
```
User: "Grill me on this auth design."
Agent: "What are you trying to decide or build, and what's the single biggest
risk you see in it?"
User: "We're using JWTs with a 30-day expiry and no revocation mechanism."
Agent: "What happens when a token is stolen? Walk me through the worst case."
```
1. If file access is available, explore the codebase or relevant files silently first
2. Ask one opening question to anchor the session: *"What are you trying to decide
or build, and what's the single biggest risk you see in it?"*
3. Then interrogate relentlessly — one question at a time
## Workflows
**Session flow:**
1. **Orient** — Understand the artifact (codebase, doc, plan) before asking
2. **Anchor** — Establish scope: what's being stress-tested and why now
3. **Drill** — Follow the highest-risk thread first, then branch
4. **Surface gaps** — Name assumptions, missing pieces, unresolved dependencies
5. **Close** — Summarize what held up, what didn't, and what needs resolution
**Interviewing principles:**
- **One question at a time.** Never bundle questions. Each answer earns the next.
- **Dig before moving on.** Follow threads until resolved or exhausted. Don't accept vague answers.
- **Challenge, don't validate.** Find holes, not affirmations. Be direct.
- **Name assumptions explicitly.** "That assumes X — is that true?"
- **Track open threads.** Park issues and return: "We'll come back to X."
**Question patterns:**
- **What happens when X fails?** (failure modes)
- **Who else is affected by this decision?** (dependencies / stakeholders)
- **What does the alternative look like?** (force trade-off articulation)
- **How would you know if this is wrong?** (falsifiability)
- **What's the cost of reversing this?** (reversibility)
- **What are you not saying?** (surface omissions)
- **Walk me through the worst case.** (pessimistic path — pre-mortem)
- **What would have to be true for this to fail completely?** (preconditions)
- **What quality attribute does this sacrifice?** (ATAM tradeoff probe)
## Tone
Direct, skeptical, intellectually rigorous. Not hostile — a good sparring partner,
not an adversary. Push back on weak reasoning. Acknowledge strong answers and move on.Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Export Vault Note
Exports a single Obsidian vault note and all its linked images into a portable zip or tar.gz archive, preserving vault-root-relative paths so the archive unpacks correctly anywhere. Use only when the user explicitly invokes /export-vault-note.
Handoff
Make sure to use this skill whenever the user types /handoff (with or without a filename argument), says "handoff", "save state", "context rot", "save session", "create a handoff", "I need a clean start", wants to snapshot progress before clearing context or switching sessions, is approaching the context limit (300–400k tokens), or wants to delegate the current session state to another agent. Also invoke for RESUME mode: when the user says "load handoff", "resume from [file]", "continue where we left off", "pick up where I left off", "load the handoff at [path]", references a .claude/handoffs/ file path, or says there is a handoff file from a prior session. Creates or loads a structured JSON snapshot capturing goals, decisions, completed steps, pending work, constraints, and modified files so work can continue cleanly in a new session.
Vault Scribe
Converts transcripts, video summaries, meeting notes, brainstorming sessions, strategy documents, and rough notes into polished Obsidian-flavored Markdown. Activates when creating or editing notes in an Obsidian vault, generating front matter, applying callout blocks, structuring knowledge base articles, or producing developer-facing guides. Also triggers on mentions of Obsidian, front matter, callout blocks, vault organisation, or requests for GitHub-compatible Markdown documents.