stakeholder-challenge

Coordinate three-perspective challenges among PO, Tech Lead, and Architect.

Updated Mar 24, 2026

Search Tags:#architecture #prioritization #feasibility #backlog #stakeholder #challenge

Ready to run

npx skills add https://github.com/foutoucour/guitar-match --skill stakeholder-challenge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stakeholder-challenge
Source: https://github.com/foutoucour/guitar-match/tree/main/.claude/skills/stakeholder-challenge
Command: npx skills add https://github.com/foutoucour/guitar-match --skill stakeholder-challenge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structure critical dialogue between Product Owner, Tech Lead, and Architect to challenge assumptions, priorities, and feasibility, ensuring alignment across teams.

Core Features & Use Cases

Facilitates three-way challenge sessions to surface assumptions, dependencies, and risks.
Evaluates backlog items for feasibility, priority, and scope, producing actionable insights.
Generates a Stakeholder Challenge Report to guide decision-making and planning.

Quick Start

Start a stakeholder-challenge session using backlog.yaml or problem.yaml to surface misalignment and drive consensus.

Frequently Asked Questions about stakeholder-challenge

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

FAQPage Schema

What is a stakeholder challenge session and when do I need one for backlog prioritization?▼

A stakeholder challenge session is a structured dialogue between the PO, Tech Lead, and Architect to surface assumptions and dependencies. You need it when evaluating backlog items for feasibility, priority, and scope to ensure cross-team alignment.

How do I facilitate a three-way challenge pass using a backlog.yaml file?▼

To facilitate a three-way challenge pass, input your backlog.yaml into the session to coordinate structured perspectives from the PO, Tech Lead, and Architect. This process evaluates prioritization, feasibility, and tech debt, ultimately producing a structured Stakeholder Challenge Report.

Can I use problem.yaml and architecture.yaml as inputs for stakeholder dialogue?▼

Yes, you can use problem.yaml and architecture.yaml as inputs for stakeholder dialogue. The session evaluates these files to coordinate three challenge passes among key roles, assessing scope and estimation to produce actionable insights.

What's the best way to evaluate technical debt and feasibility during product planning?▼

The best way to evaluate technical debt and feasibility is through a structured three-perspective challenge among the PO, Tech Lead, and Architect. This surfaces hidden dependencies and risks, generating a Stakeholder Challenge Report to guide decision-making.

Does the stakeholder challenge process work for evaluating estimation and scope misalignment?▼

Yes, the stakeholder challenge process works for evaluating estimation and scope misalignment. It coordinates three challenge passes across key roles to critically evaluate assumptions and dependencies, driving consensus and producing a structured report.