Guide structured research and formal specification for architectural decisions.
npx skills add https://github.com/NooBat/claude --skill pair-brainstorm
Please help me install this Agent Skill. Skill: pair-brainstorm Source: https://github.com/NooBat/claude/tree/main/skills/pair-brainstorm Command: npx skills add https://github.com/NooBat/claude --skill pair-brainstorm
Pair Brainstorm provides a structured, research-first approach to architectural and product decisions, helping teams surface assumptions, challenge weak ideas, and convert discussion into a concrete spec with ADRs.
Initiate Phase 1 research, synthesize findings into a complete spec with ADRs, and prepare for the spec review loop.
High-intent search queries and answers about installing and using this skill.
To document architectural decisions, use a structured, research-first evaluation process that applies adversarial questioning to surface edge cases. This converts design discussions into a concrete specification and creates Architecture Decision Records for long-term justification.
A devil's-advocate design review is an adversarial questioning phase that challenges weak ideas and surfaces hidden assumptions. It refines specifications by forcing a structured evaluation of constraints, edge cases, and alternative approaches before finalizing scope.
Writing MVP user stories from architecture brainstorming requires a phase-driven workflow that synthesizes research into a formal specification. It captures the clear WHAT, constraints, and acceptance criteria necessary for handoff-ready planning and execution.
You need an ADR when alternative architectural approaches warrant long-term justification, while a full specification is required to define the MVP-focused scope, constraints, and acceptance criteria for immediate execution.
Yes, risk analysis is integrated into the adversarial design phase to actively surface assumptions and edge cases. This forces teams to evaluate several options and capture the resulting constraints within a structured specification.
The best way to prepare for a design review handoff is to complete a four-phase workflow: conduct quick research, apply adversarial questioning, generate formal documentation, and produce handoff-ready outputs for planning.
mamu7211Decompose feature ideas into technical specifications through structured design interviews.
greglambExecute implementation plans via isolated subagents with two-stage review gates.
rjroyChallenge user ideas with adversarial questioning to surface hidden assumptions.
HexSleevesChallenges a plan or design to expose weaknesses before execution.
