stakeholder-interview
Stakeholder Interview
Overview
Use this skill to extract authoritative decisions from internal stakeholders and convert them into traceable engineering constraints.
Scope Boundaries
- Requirements or architecture choices are blocked by missing policy or ownership decisions.
- Teams disagree about constraints and need documented decision authority.
- Cross-functional alignment is required before implementation commitments.
Templates And Assets
- Interview note template:
assets/stakeholder-interview-template.md
- Decision conflict log:
assets/decision-conflict-log-template.md
Inputs To Gather
- Decision questions and why each question is blocking progress.
- Stakeholder map with authority boundaries and fallback approvers.
- Existing assumptions, unresolved conflicts, and time constraints.
Deliverables
- Interview records with source, date, authority level, and explicit decision statement.
- Constraint catalog (policy, compliance, operational, budget, timeline).
- Conflict log with owner, escalation route, and required resolution date.
Workflow
- Define interview goals as decision questions, not open brainstorming topics.
- Prioritize stakeholders by decision authority and delivery criticality.
- Conduct structured interviews and separate facts from preferences.
- Confirm decisions in writing with explicit scope and expiry assumptions.
- Record conflicts and escalate unresolved items with options and impacts.
- Publish an auditable summary that downstream requirement skills can consume.
Quality Standard
- Every key claim has a named source and explicit authority level.
- Ambiguous statements are converted into verifiable constraints.
- Conflicts are visible with an assigned owner and deadline.
- Outputs are specific enough to drive requirement and implementation decisions.
Failure Conditions
- Stop when no stakeholder with decision authority is available.
- Stop when interview outputs mix assumptions and approved policy.
- Escalate when blocking conflicts remain unresolved past agreed deadlines.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9