skills.rest
Driving-Teacher
Driving-TeacherOFFICIAL
Explore all skills by this author →
WebsiteGitHub

day3-clarify

Clarify vague requirements into concrete specifications and PRD-ready plans.

1|Updated Mar 30, 2026
Search Tags:#github#plugin#prd#clarify#askuserquestion#ambiguous-requirements
One-click install
npx skills add https://github.com/Driving-Teacher/driving-teacher-ai-native --skill day3-clarify-driving-teacher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: day3-clarify
Source: https://github.com/Driving-Teacher/driving-teacher-ai-native/tree/main/.claude/skills/archive-day3-clarify
Command: npx skills add https://github.com/Driving-Teacher/driving-teacher-ai-native --skill day3-clarify-driving-teacher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Day 3 Clarify enables teams and individuals to resolve ambiguous requirements by applying a structured clarify workflow, producing a concrete specification and PRD ready for GitHub submission.

Core Features & Use Cases

  • Structured ambiguity resolution using AskUserQuestion and the STOP PROTOCOL Phase A/B.
  • Build and customize a personal clarify skill (template-based) and reuse across projects.
  • Create a PRD and submit it to GitHub as a PR, tracking changes over days.

Use Case: A product manager receives vague feature ideas and wants a clear spec and PRD.

Quick Start

Trigger the Day 3 Clarify skill and follow STOP PROTOCOL to turn ambiguous requirements into a concrete spec and PRD, and then submit to GitHub.

Frequently Asked Questions about day3-clarify

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

FAQPage Schema
How do I turn ambiguous product requirements into a concrete specification?▼

To turn ambiguous product requirements into a concrete specification, apply a structured clarify workflow using a STOP PROTOCOL with AskUserQuestion batches to resolve vagueness and generate a PRD-ready plan.

What is the STOP PROTOCOL for clarifying vague requests?▼

The STOP PROTOCOL for clarifying vague requests is a structured Phase A and Phase B workflow that limits AskUserQuestion interactions to batches of up to 4 questions, ensuring thorough ambiguity resolution before PRD generation.

How do I create a PRD and submit it to GitHub as a pull request?▼

To create a PRD and submit it to GitHub as a pull request, use a clarify skill to validate PRD content against ambiguous requirements, then submit the finalized specification directly to GitHub for tracking changes over days.

Can I build and reuse a personal clarify skill across different projects?▼

Yes, you can build and reuse a personal clarify skill across different projects by customizing a template-based workflow that enforces the STOP PROTOCOL and standardizes ambiguity resolution for various feature ideas.

How many questions can the AskUserQuestion protocol ask during requirement clarification?▼

The AskUserQuestion protocol asks up to 4 questions per batch and a total of 5 to 8 questions during requirement clarification to effectively resolve vague feature ideas without overwhelming the user.

Related Skills

Explore More Product & Management Skills→
ranvirsinghranvirsingh

speckit-specify

Convert natural language feature ideas into GitHub Issue-backed specs.

Community
Advanced
ma08ma08
28

yeet

Automate Git staging, commits, branch pushes, and pull requests for GitHub.

Community
Intermediate
gregrickabygregrickaby
58

implement-github-issue

Implement GitHub issues by reading issue text and executing file-level plans.

Community
Advanced
oaustegardoaustegard
137

asking-questions

Identify ambiguous user requests and ask targeted clarifying questions.

Community
Basic