decision-conflict-questioning

Prompts concrete alternatives for phase planning conflicts with named types and stop rules.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill decision-conflict-questioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-conflict-questioning
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/decision-conflict-questioning
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill decision-conflict-questioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conflict-driven clarification during phase discussions helps keep planning focused by surfacing tensions and prompting concrete alternatives rather than generic why-prompts.

Core Features & Use Cases

  • Surface explicit tensions and name the conflict type to ensure shared understanding.
  • Provide 3-4 concrete alternatives with different tradeoffs and a clear fallback path.
  • Apply stop rules to prevent over-questioning and scope drift in planning sessions.

Quick Start

Use this skill during phase planning to surface concrete alternatives when tensions arise.

Frequently Asked Questions about decision-conflict-questioning

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

FAQPage Schema
How do I resolve conflicts during phase planning discussions?

Resolve phase planning conflicts by surfacing explicit tensions, naming the conflict type, and prompting concrete alternatives with different tradeoffs and a clear fallback path. This replaces generic clarifications with structured decision gates for shared understanding.

What is the best way to surface tradeoffs when decision tensions arise?

Surface tradeoffs by defining clear paths and providing 3-4 concrete alternatives with different tradeoffs. This ensures teams choose from actionable options rather than generic why-prompts during planning conversations.

How do I prevent scope drift when questioning decisions in alignment meetings?

Prevent scope drift by applying structured stop rules and anti-pattern guards within the phase planning workflow. These mechanisms prevent over-questioning and keep planning sessions focused on the original decision gates.

When do I need structured questioning for phase-level decisions?

Structured questioning is needed when phase-level tensions arise in planning conversations targeting intent, requirements, prior decisions, and tradeoffs. It clarifies decision gates by defining clear paths and alternatives to choose from.

Can I use this approach to align on requirements before finalizing tradeoffs?

Yes, you can align on requirements by targeting decision gates in planning conversations. The structured triggers and named conflict types ensure shared understanding of intent and requirements before evaluating tradeoffs.

Why does questioning prior decisions help with phase alignment?

Questioning prior decisions helps with phase alignment by surfacing tensions and prompting concrete alternatives rather than generic why-prompts. It enforces structured triggers to define clear paths and alternatives to choose from.