intent-interview

Coordinate structured interviews to produce decisions.md and INTENT.md specifications.

15|5|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ArcBlock/idd --skill intent-interview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent-interview
Source: https://github.com/ArcBlock/idd/tree/main/skills/intent-interview
Command: npx skills add https://github.com/ArcBlock/idd --skill intent-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague ideas into implementation-ready product specifications through a structured interviewing process that yields decisions.md in Phase A and INTENT.md in Phase B.

Core Features & Use Cases

  • Two-phase model: Phase A outputs decisions.md; Phase B composes INTENT.md under budget constraints.
  • Anchor-based questioning to capture design decisions with scope guards and readiness checks.
  • Traceability from initial questions to final INTENT.md, enabling clear documentation and alignment.

Quick Start

Begin Phase A by interviewing the stakeholder to capture decisions in decisions.md, then switch to Phase B to compose INTENT.md when requested.

Frequently Asked Questions about intent-interview

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

FAQPage Schema
How do I turn vague product ideas into executable specifications?

To turn vague ideas into executable specifications, use a structured interview process that captures stakeholder decisions in a decisions.md file, then composes a final INTENT.md document with full traceability from initial questions to output.

What is the best way to capture design decisions during stakeholder interviews?

Capturing design decisions during stakeholder interviews is best handled through an anchor-based questioning approach with scope guards and readiness checks, ensuring rigorous decision capture that prevents scope creep and validates requirement completeness.

How does a two-phase interview model work for product requirements gathering?

A two-phase interview model works by splitting requirements gathering into Phase A, which outputs a decisions.md file capturing stakeholder choices, and Phase B, which composes the final INTENT.md specification under budget constraints based on those captured decisions.

Can I enforce budget constraints when composing product specifications?

Yes, you can enforce budget constraints when composing product specifications during the Phase B composition stage, ensuring the generated INTENT.md document aligns with predefined resource limitations and project scope boundaries.

When do I need traceability from interview questions to the final spec?

You need traceability from interview questions to the final spec when aligning diverse stakeholders on implementation-ready requirements, as it enables clear documentation by linking every output in decisions.md and INTENT.md back to original design decisions.