spec-ask-questions

Guide structured one-question-at-a-time interviews to clarify ambiguous project specifications.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pascalandy/dotfiles --skill spec-ask-questions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-ask-questions
Source: https://github.com/pascalandy/dotfiles/tree/main/dot_config/opencode/skill/spec-ask-questions
Command: npx skills add https://github.com/pascalandy/dotfiles --skill spec-ask-questions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to quickly resolve unclear requirements by guiding a structured, one-question-at-a-time interview that yields concrete choices.

Core Features & Use Cases

  • One-question-at-a-time Interview Flow: Guides the user through up to 7 questions, ensuring concise, high-signal clarifications.
  • Structured Multiple-Choice Options: Presents choices like 1) ..., 2) ..., with the recommended answer shown in parentheses to accelerate decisions.
  • Auto-Update & Alignment: After the interview, updates relevant documentation and spec files to reflect decisions.
  • Use Case: When requirements are ambiguous or conflicting, use this Skill to rapidly align stakeholders and lock in specifications.

Quick Start

Use the skill to run a clarifying interview when requirements are unclear. Start by asking one question, present options as 1) ..., 2) ..., 3) ..., show your recommended answer in parentheses, stop at 7 questions, and update the relevant files after completion.

Frequently Asked Questions about spec-ask-questions

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

FAQPage Schema
How do I clarify ambiguous product requirements with stakeholders?

Clarify ambiguous product requirements by running a structured, one-question-at-a-time interview that presents predefined multiple-choice options, highlights a recommended answer, and stops at 7 questions to rapidly align stakeholders.

What is the best way to resolve conflicting project specifications during early discovery?

The best way to resolve conflicting project specifications is a rapid-spec interview that guides stakeholders through up to 7 structured questions with numbered choices, locking in concrete decisions to update relevant files.

How do I scope product features when requirements are unclear?

Scope product features by conducting a focused interview that surfaces high-signal clarifications through structured multiple-choice options, ensuring teams lock in concrete choices and automatically update spec files upon completion.

Can I use structured interviews to align cross-functional teams on requirements?

Yes, you can align cross-functional teams by guiding them through a structured interview with predefined answer choices, yielding concrete decisions that automatically update documentation and ensure stakeholder alignment.

Does the interview process limit how many questions I can ask to scope a feature?

Yes, the interview process limits the session to a maximum of 7 questions to ensure concise, high-signal clarifications, presenting structured options with a recommended answer before updating relevant spec files.

How do I guide a stakeholder interview to lock in concrete specification choices?

Guide a stakeholder interview by asking one question at a time, presenting options as numbered choices with the recommended answer shown in parentheses, then updating documentation to reflect the locked-in specifications.