requirements-expert

Convert vague project descriptions into structured Behavior Contracts with prioritized clarifying questions.

1|Updated Dec 5, 2025

Search Tags:#scoping #specification #requirements #product-management #stakeholders #clarifying questions #behavior-contract

Ready to run

npx skills add https://github.com/shawndeggans/claude-code-saddle --skill requirements-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-expert
Source: https://github.com/shawndeggans/claude-code-saddle/tree/main/saddle/experts/requirements
Command: npx skills add https://github.com/shawndeggans/claude-code-saddle --skill requirements-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineering groups convert vague or partial project descriptions into structured Behavior Contracts that guide implementation and testing, surfacing ambiguities early.

Core Features & Use Cases

Clarifying questions prioritized by impact to resolve critical gaps
Behavior Contract drafting from gathered information
Open questions management and risk notes to support handoffs

Quick Start

Describe your project briefly and share any known constraints to receive a Behavior Contract draft and clarifying questions.

Frequently Asked Questions about requirements-expert

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

FAQPage Schema

What is a Behavior Contract in product management?▼

A Behavior Contract is an implementation-agnostic specification focused on outcomes, success criteria, and clearly defined behaviors. It surfaces ambiguities early and guides both engineering implementation and testing processes.

How do I identify gaps and ambiguities in partial project requirements?▼

To identify gaps and ambiguities in partial project requirements, the system analyzes your description and generates prioritized clarifying questions. These questions target unstated assumptions and critical gaps to resolve issues before implementation begins.

Can I use this for scoping projects with multiple stakeholders?▼

Yes, you can use this for scoping projects with multiple stakeholders. It supports handoffs by managing open questions and risk notes, ensuring all stakeholders have clarity on defined behaviors and success criteria before development starts.

What is the best way to draft implementation-ready requirements from partial descriptions?▼

The best way to draft implementation-ready requirements is to submit your partial project descriptions to the system. It transforms them into a structured Behavior Contract while providing prioritized clarifying questions to resolve remaining critical gaps.