stakeholder-interview

Capture stakeholder decisions and convert them into traceable engineering constraints.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill stakeholder-interview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-interview
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/stakeholder-interview
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill stakeholder-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Capture authoritative stakeholder decisions and convert them into traceable engineering constraints.

Core Features & Use Cases

  • Structured interviews to elicit decisions and ownership boundaries.
  • Templates and logs to document decisions, conflicts, and follow-ups.
  • Guidance for publishing auditable summaries and downstream requirements.

Quick Start

Conduct a structured stakeholder interview and store the outcomes using the provided templates in assets.

Frequently Asked Questions about stakeholder-interview

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

FAQPage Schema
How do I document stakeholder decisions to unblock engineering delivery?

Document stakeholder decisions by conducting structured interviews and converting the outcomes into auditable decision records and traceable engineering constraints. This process resolves blocked projects by establishing clear policy ownership and cross-functional alignment.

What is the best way to capture unresolved stakeholder decisions for project governance?

The best way to capture unresolved stakeholder decisions is using structured interview templates to elicit ownership boundaries. This generates conflict logs and decision confirmations, creating an auditable summary of downstream requirements for project governance.

How do I conduct a structured stakeholder interview for cross-functional alignment?

Conduct a structured stakeholder interview by applying provided templates to guide the conversation, elicit ownership boundaries, and log conflicts. You then publish auditable summaries to ensure cross-functional alignment and establish traceable engineering constraints.

Can I use templates to track stakeholder conflicts and decision follow-ups?

Yes, you can use the provided templates to track stakeholder conflicts and decision follow-ups. The templates support creating auditable decision records and conflict logs to manage unresolved decisions and convert them into traceable engineering constraints.

When do I need auditable decision records for engineering constraints?

You need auditable decision records when projects are blocked by unresolved stakeholder decisions or policy ownership issues. Capturing these decisions converts them into traceable engineering constraints, enabling cross-functional alignment and clearing delivery blockers.

Does the stakeholder-interview Skill require any specific dependencies or prior setup?

No specific dependencies are required to use the stakeholder-interview Skill. You simply need to conduct your structured stakeholder interview and store the outcomes using the provided templates in the assets folder to generate traceable engineering constraints.