design-interrogation

Probe design plans to surface hidden assumptions and generate artifacts.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/I-Synergy/AI --skill design-interrogation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-interrogation
Source: https://github.com/I-Synergy/AI/tree/main/.github/skills/design-interrogation
Command: npx skills add https://github.com/I-Synergy/AI --skill design-interrogation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured design interrogation helps teams identify and resolve architectural and plan-level uncertainties by forcing a methodical, question-driven review.

Core Features & Use Cases

  • Relentless, guided probing of design decisions to surface dependencies and risks
  • Live decision logging and mapping of the decision tree
  • Integration with existing skills (ubiquitous-language, usecase-specification, user-story) to generate artifacts

Quick Start

Initiate a session by naming your plan, stating goals, and let the skill drive a phased, question-driven interrogation.

Frequently Asked Questions about design-interrogation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is structured design interrogation in domain-driven design?

Structured design interrogation is a methodical, question-driven review process that probes architectural plans to surface hidden assumptions, dependencies, and risks before implementation begins.

How do I conduct an architecture review to surface hidden assumptions?

You conduct an architecture review by initiating a phased interrogation session, stating your plan goals, and answering guided questions that systematically challenge your design decisions and log the decision tree.

Can I use design interrogation for migration and extension reviews?

Yes, design interrogation applies to greenfield, migration, and extension review sessions, guiding you through phase-based questions to resolve plan-level uncertainties across various project contexts.

What artifacts are generated during a design interrogation session?

A design interrogation session generates artifacts including ubiquitous language definitions, use-case specifications, and user stories, while simultaneously logging decisions and mapping the decision tree.

How do I start a design interrogation session for my architecture plan?

You start a design interrogation session by naming your plan and stating your goals, which triggers a phased, question-driven interrogation that methodically probes your design decisions.

Why should I use question-driven probing instead of standard architecture reviews?

Question-driven probing forces a relentless, structured review that methodically surfaces dependencies and risks, whereas standard reviews often miss hidden assumptions through unstructured evaluation.