deliverable-interview

Stakeholder Interview

Shared resources

Load on demand from the sibling deliverable/ skill folder: roles/*.md, templates/*.md, sub-agents/*.md, references/*.md.

Generate structured interview templates for real stakeholders. When you don't have the answers, this skill creates the right questions — with context, examples of good answers, and space for responses. Take the template offline, interview the stakeholder, bring it back.

Announce at start: "I'm using the deliverable-interview skill to prepare interview templates for your stakeholders."

When to use

• During any other deliverable skill when the user can't answer a question
• Standalone — user wants to prepare for stakeholder conversations before starting requirements

Flow

flowchart TD
    P1[Who needs to be interviewed?] --> P2[What do we need to learn?]
    P2 --> P3[Select relevant role scripts]
    P3 --> P4[Generate deliverable-interview template]
    P4 --> P5[Save to docs/requirements/interviews/]
    P5 --> P6{More stakeholders?}
    P6 -->|yes| P1
    P6 -->|no| DONE[Done — templates ready]

Step 1: Identify stakeholders

Ask: who needs to be interviewed? Map each person to a role:

• Executive / sponsor → roles/sponsor.md
• Product manager → roles/pm.md
• Technical lead / architect → roles/tech-lead.md
• Designer / UX researcher → roles/designer.md
• QA / test lead → roles/qa.md
• SRE / ops → roles/sre.md
• Legal / security / compliance → roles/security-legal.md

Step 2: Determine what we need to learn

Check context:

• If called from another skill (deliverable-brd, deliverable-srs), use the current phase's open questions
• If standalone, ask what topics need answers

Step 3: Generate template

Use templates/interview.md structure. Pull questions from the relevant role script's question bank. Customize:

• Context for interviewer — 2-3 sentences to set up the conversation
• Each question includes: why we need this, what a good answer looks like, space for the answer
• Follow-up notes section for unexpected insights

Step 4: Save

Write to docs/requirements/interviews/YYYY-MM-DD-<role>-<topic>.md

If called from another skill, also update state.md to record the pause and what's pending.

Multiple stakeholders

Can generate templates for several stakeholders in one session. Each gets its own file.

Template format

# Interview: <role/person> — <topic>

> Generated: YYYY-MM-DD · Project: <name>
> Purpose: <what we need to learn and why>

## Context for interviewer

<2-3 sentences to share with the stakeholder>

## Questions

### Q1: <question>

- Why we need this: <one sentence>
- Good answer looks like: <example>
- Answer: ********\_********

### Q2: <question>

...

## Follow-up notes

<space for anything unexpected>

## When done

Bring this back and run the deliverable skill again —
it will detect this file and resume where you left off.

Tone

• Questions should be clear enough for a non-technical stakeholder
• Include "good answer" examples so the interviewer knows what depth to aim for
• No jargon in the context section

On return

When the user comes back with a filled template, any deliverable skill can read it from docs/requirements/interviews/ and ingest the answers to continue.