refinement-questionnaire

Analyze requirement documents to generate a prioritized 20-question clarifying questionnaire.

3|2|Updated Jun 25, 2024
One-click install
npx skills add https://github.com/Hopin-inc/civicship-api --skill refinement-questionnaire
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refinement-questionnaire
Source: https://github.com/Hopin-inc/civicship-api/tree/main/.claude/skills/refinement-questionnaire
Command: npx skills add https://github.com/Hopin-inc/civicship-api --skill refinement-questionnaire

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

要件定義の不明点・抜け漏れを質問形式で洗い出し、プロダクトオーナーやステークホルダーがスコープの合意を迅速に得られるよう支援します。要件定義の精緻化を通じて、仕様の認識ずれによる開発リスクを低減します。

Core Features & Use Cases

  • 要件定義書を分析し、曖昧さ・不足点を洗い出す質問を自動生成します。
  • ステークホルダーとプロダクトオーナーの合意形成を促進します。
  • Use Case: 要件定義書の要点を整理し、開発チームが遵守すべき確認事項を体系的に提示します。

Quick Start

Invoke the skill with a requirements path or feature name to generate a structured refinement questionnaire.

Frequently Asked Questions about refinement-questionnaire

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

FAQPage Schema
How do I clarify requirement gaps and align stakeholder scope before development?

Clarifying requirement gaps involves analyzing requirement documents to generate a prioritized 20-question questionnaire that reveals ambiguiances and aligns stakeholder scope. This structured refinement process exposes missing specifications and supports rapid agreement on project decisions.

What is the best way to generate clarifying questions for stakeholder interviews?

Generating clarifying questions for stakeholder interviews is best achieved by analyzing requirement documents or feature names to systematically extract ambiguities. This produces a structured questionnaire with response guidance to align stakeholder expectations and refine specifications.

How can I reduce specification misalignment risks during requirement refinement?

Specification misalignment risks are reduced by identifying unclear points and omissions through an automated questionnaire. This structured questioning method highlights specification gaps early, enabling product owners and stakeholders to reach a rapid consensus on development scope.

Can I use a feature name to extract missing requirements instead of a full document?

Yes, you can use a feature name to extract missing requirements instead of a full document. The skill analyzes feature names to generate a comprehensive set of clarifying questions that reveal scope gaps and support requirement refinement without needing a complete specification.

Does the requirement questionnaire provide guidance on how stakeholders should respond?

Yes, the requirement questionnaire provides guidance on how stakeholders should respond to each inquiry. Alongside the prioritized 20 questions, it delivers structured response instructions to ensure stakeholders provide the necessary information for requirement agreement.