Clarify feature requests and convert them into structured EARS-style requirements.
npx skills add https://github.com/etr/groundwork --skill product-design-etr
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
Product teams often struggle to translate vague feature ideas into structured, cross-functional PRDs and EARS-ready requirements, leading to misalignment and rework.
Quickly start the clarification process for a new feature request and begin drafting the PRD.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
nicograefGenerate structured product requirements documents through iterative clarification and codebase analysis.
cvillamarp-lgtmTranslate product goals into testable specs and design documents.
heyramziEnforce alignment, spacing, typography, and token consistency in UI reviews.
heykvnzhaoRefactor AGENTS.md into a minimal root file with linked category docs.
