v1.0 to v1.0

- description: >-

- Systematic plan stress-testing through relentless one-question-at-a-time decision-tree

- interviewing

- allowed-tools: Read Grep Glob Bash Write Edit

- Works for any plan, design, or architectural proposal. Pairs with grill-with-docs

- when domain documentation should be updated during the session, and with to-issues

- when the vetted plan should be converted to tickets.

- tags: design-review, stress-testing, planning, architecture, questioning, validation

- Thoroughly vet plans and designs through systematic, relentless questioning.

-

- ## When to use this skill

-

- - Before committing to an architectural decision

- - When a design feels right but hasn't been challenged

- - Stress-testing assumptions before implementation begins

- - Exploring edge cases and failure modes in a proposal

-

- ## When not to use this skill

-

- - Quick clarifying questions → just ask directly

- - Validating against domain docs → use `grill-with-docs`

- - Writing implementation tickets → use `to-issues`

-

- ## Process

-

- Interview relentlessly about every aspect of the plan until shared understanding is reached. Walk down each branch of the decision tree, resolving dependencies between decisions one by one.

-

- **Rules:**

- - Ask one question at a time

- - Wait for feedback before continuing

- - Provide a recommended answer with each question

- - Explore the codebase instead of asking when the answer is findable there

- - Keep going until all branches of the decision tree are resolved

-

- ## What gets covered

-

- The grilling session explores:

-

- - **Why this approach?** — What alternatives were considered and rejected?

- - **What breaks first?** — Edge cases, failure modes, error states

- - **What are the dependencies?** — What must be true for this to work?

- - **What changes later?** — Which parts are likely to evolve?

- - **What can't change?** — Which decisions are load-bearing and hard to reverse?

- - **Who is affected?** — Callers, consumers, downstream systems

-

- ## Output

- By the end of the session:

- - Every major decision point has been examined

- - Dependencies between decisions have been resolved in order

- - Remaining open questions are documented

- - Shared understanding exists about trade-offs made

- ## Activation

- User says: "grill me", "stress-test this plan", "challenge my design", "ask me hard questions about this"

- 1. Identify the task trigger and expected output.

- 2. Follow the workflow steps in this skill from top to bottom.

- 3. Validate outputs before moving to the next step.

- 4. Capture blockers and fallback path if any step fails.

- - Example: Apply this skill to a small scope first, then scale to full scope after validation passes.

- - Keep outputs deterministic and auditable.

- - Prefer small reversible changes over broad risky edits.

- - Record assumptions explicitly.