product-design

Clarify feature requests and convert them into structured EARS-style requirements.

41|4|Updated Jan 28, 2026

Search Tags:#workflow #design #requirements #clarification #prd #ears

Ready to run

npx skills add https://github.com/etr/groundwork --skill product-design-etr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-design
Source: https://github.com/etr/groundwork/tree/main/skills/product-design
Command: npx skills add https://github.com/etr/groundwork --skill product-design-etr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams often struggle to translate vague feature ideas into structured, cross-functional PRDs and EARS-ready requirements, leading to misalignment and rework.

Core Features & Use Cases

Interactive clarification workflow to resolve stakeholder intent and detect contradictions before drafting requirements.
End-to-end PRD drafting with EARS-aligned requirements, traceability scaffolding, and cross-feature consistency checks.
Load and align with existing project context (architecture, design system, product specs) to ensure feasibility and coherence.

Quick Start

Quickly start the clarification process for a new feature request and begin drafting the PRD.

Frequently Asked Questions about product-design

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

FAQPage Schema

How do I turn vague feature ideas into structured PRDs?▼

To turn vague feature ideas into structured PRDs, use an interactive clarification workflow to resolve stakeholder intent and detect contradictions before drafting EARS-style requirements. This ensures cross-functional alignment and produces precise, testable product specifications.

What is the EARS syntax for writing product requirements?▼

EARS syntax for writing product requirements structures requests into precise, testable, and traceable conditions. It applies across product discovery and PRD drafting to avoid contradictions and ensure context is loaded from project specs for cross-functional alignment.

How do I ensure my PRD captures testable and traceable requirements?▼

To ensure your PRD captures testable and traceable requirements, draft using EARS-aligned syntax with traceability scaffolding and cross-feature consistency checks. This workflow prevents contradictions and verifies feasibility against existing architecture and design systems.

Can I load existing project architecture and design specs into the PRD workflow?▼

Yes, you can load existing project architecture, design system, and product specs into the PRD workflow. Loading this project context ensures your drafted EARS requirements maintain coherence and feasibility across cross-functional teams.

What is the best way to manage stakeholder intent and detect contradictions during product discovery?▼

The best way to manage stakeholder intent and detect contradictions during product discovery is through an interactive clarification workflow. This process resolves ambiguities upfront, ensuring your PRD drafting phase produces aligned and contradiction-free EARS requirements.

Does this PRD drafting workflow handle change-management and UX considerations?▼

Yes, this PRD drafting workflow handles change-management and UX considerations. It applies across product discovery and change-management workflows, capturing precise EARS-style requirements while ensuring alignment with architecture and UX design contexts.