f2s-req-clarify

Clarifies PRD requirements through iterative questioning and writes a structured clarification document.

48|6|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-req-clarify-double-coding-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: f2s-req-clarify
Source: https://github.com/double-coding-lab/Flow2Spec/tree/main/.cursor/skills/f2s-req-clarify
Command: npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-req-clarify-double-coding-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous PRDs and requirement descriptions cause AI coding agents to make wrong assumptions. This Skill interrogates the requirement until flows, boundaries, exceptions, and key concepts are unambiguous, then persists a clarification document before any technical design begins. ## Core Features & Use Cases - Ambiguity Detection: Finds vague wording, undefined concepts, missing information, contradictions, and unspecified implementation-relevant points, then asks grouped, answerable questions. - Iterative Clarification: Refines follow-up questions based on user answers until the requirement is fully clear, without making business assumptions on the user's behalf. - Structured Output & Handoff: Writes a Markdown clarification document (background, scope, key flows, boundaries, concept definitions, acceptance criteria, open questions) to .Knowledge/req-docs/ and automatically chains into the f2s-req-tech technical design step. - Use Case: Paste a rough PRD for a review-template feature; the agent asks targeted questions about states, permissions, and edge cases, saves the clarification document, and proceeds to the technical plan. ## Quick Start Ask the agent to clarify this PRD and resolve all ambiguities before producing a technical design.

Frequently Asked Questions about f2s-req-clarify

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

FAQPage Schema
How do I clarify a PRD with an AI coding agent?▼

Provide the PRD text, a requirement description, or a document path as input. The agent identifies vague statements, missing details, and contradictions, asks grouped questions, and iterates until the requirement is unambiguous before writing a clarification document.

What does the requirement clarification document contain?▼

The Markdown document includes background and goals, scope (included and excluded), key flows, boundaries and exceptions, key concept definitions, acceptance criteria, and any unresolved questions. It is saved to .Knowledge/req-docs/ with a recommended naming pattern.

Does clarification automatically continue into technical design?▼

Yes. After the clarification document is saved to disk, the skill outputs a transition line and immediately invokes f2s-req-tech in the same turn. It stops instead if critical open questions remain or the user explicitly asks to pause.

When does requirement clarification stop without a technical plan?▼

It stops when unresolved questions affect core contracts such as tables, interfaces, or state machines, when the user says to only clarify, or when the user specifies a different next action. The pending items are listed for the user to answer.

Can clarification run in a sub-agent or split session?▼

No. The clarification flow always runs in the main session regardless of sub-agent configuration, because iterative questioning depends on continuous conversational context that would break if delegated to a sub-agent.