cdd-analyst

Draft atomic requirements using EARS notation from informal ideas.

Updated Mar 12, 2019
One-click install
npx skills add https://github.com/gustavofsantos/dot-files --skill cdd-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdd-analyst
Source: https://github.com/gustavofsantos/dot-files/tree/main/.agents/skills/cdd-analyst
Command: npx skills add https://github.com/gustavofsantos/dot-files --skill cdd-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams capture clear, testable requirements by using EARS notation, avoiding ambiguity.

Core Features & Use Cases

  • EARS-based requirement drafting: generates clear, atomic requirements using the five EARS templates.
  • Guided elicitation: aligns with plan.md grounding and analysis steps to ensure consistent specs.
  • Use case: converts informal ideas into structured spec.md ready for review.

Quick Start

Open spec.md and draft atomic requirements using EARS patterns.

Frequently Asked Questions about cdd-analyst

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

FAQPage Schema
What is EARS notation for requirements drafting?

EARS notation is a structured approach using five templates to draft clear, atomic, and testable requirements. It imposes grounding and intent analysis to ensure unambiguous specifications during product planning and feature definitions.

How do I convert informal ideas into structured specifications?

To convert informal ideas into structured specifications, apply guided elicitation aligned with plan.md grounding. This analyzes initial intent and drafts EARS-based requirements directly into a spec.md file ready for review.

Can I use EARS for writing acceptance criteria?

Yes, you can use EARS for writing acceptance criteria. The notation generates atomic requirements that fit naturally within acceptance criteria workflows, ensuring each condition is testable and free of ambiguity.

What is the best way to avoid ambiguity in product requirements?

The best way to avoid ambiguity in product requirements is drafting with EARS templates. This structured method forces intent analysis and grounding, converting vague ideas into precise, atomic specifications.

Do I need a specific format to start drafting EARS requirements?

You need a spec.md file to start drafting EARS requirements. The workflow uses this file to apply guided elicitation and structured grounding steps, transforming informal ideas into testable definitions.