psenger/design-critique
skills/design-critique/SKILL.md
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.
testing
Updated Apr 18, 2026
$ install --global
skillsauthnpx skillsauth add psenger/ai-agent-skills design-critiqueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 5:01 AM53.6s1 file scanned
SKILL.md
- name:
- design-critique
- description:
- >
- allowed-tools:
- Read Grep Glob
- argument-hint:
- [topic, file, or artifact to critique]
- compatibility:
- No external tools required. File access is optional — enhances context when available.
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."
- If file access is available, explore the codebase or relevant files silently first
- 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?"
- Then interrogate relentlessly — one question at a time
Workflows
Session flow:
- Orient — Understand the artifact (codebase, doc, plan) before asking
- Anchor — Establish scope: what's being stress-tested and why now
- Drill — Follow the highest-risk thread first, then branch
- Surface gaps — Name assumptions, missing pieces, unresolved dependencies
- 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
psenger/export-vault-note
testing
VerifiedTrustedCommunity
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.
3SKILL.mdUpdated May 24, 2026
psenger/agent-os-profile-critique
development
VerifiedTrustedCommunity
Provides the audit checklists, severity criteria (blocking/warning/suggestion), and artifact patterns needed to properly review Agent OS profiles and standards. Always invoke this skill before auditing - without it you can only give generic feedback, not structured severity-tagged findings. Invoke when the user pastes a standard and asks if it is good or what is wrong with it; when the user asks to review, audit, validate, or critique an agent-os profile or standard; or when the user mentions "agent-os profile", "agent-os standard", or "my agent-os setup" in a review or validation context.
3SKILL.mdUpdated May 11, 2026
psenger/vault-scribe
development
VerifiedTrustedCommunity
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.
3SKILL.mdUpdated Apr 18, 2026
psenger/git-commit-pr-message
documentation
VerifiedTrustedCommunity
Generate git commit messages, PR titles/descriptions, and changelog entries. Analyzes staged changes, enforces Conventional Commits, scans for sensitive content, links tickets (GitHub Issues / Jira), and updates CHANGELOG.md. Triggers on: "commit", "create a PR", "push", "changelog", "release", or when the user is ready to commit or open a pull request.
3SKILL.mdUpdated Apr 18, 2026