design-product SKILL.md skillA
design-product from etr/groundwork is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add etr/groundwork/design-product@git:20260716.aaea421Pins git:20260716.aaea421 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- etr/groundwork
- Path
skills/design-product/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260716.aaea421, committed Jul 16, 2026
- First version recorded
- Jun 22, 2026
- Size
- 16,444 bytes
- Repository stars
- 44
- License
- MIT
Create detailed product requirements document (PRD) for a feature. Usage /groundwork:design-product.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Product Design Skill
Interactive workflow for iteratively designing and documenting product requirements in EARS format.
## Workflow Overview
1. **Understand** - Clarify the feature/change request through targeted questions
2. **Design** - Draft EARS requirements and check for contradictions
3. **Approve** - Present draft for user approval
4. **Commit** - Edit the PRD document when requirements are approved
5. **Next Step** - Ask user what to do next (architecture, UX, or another feature)
If you are in plan mode, you MUST still complete the full workflow (Steps 0–4). Your plan output MUST describe ONLY the PRD file edits from Step 4.
- Which file to create or edit
- Where to insert the new feature block
- The EARS requirements content
## Pre-flight: Model Recommendation
**Your current effort level is `{{effort_level}}`.**
Skip this step silently if effort is `high`, `xhigh`, or `max` (the scale is `low` < `medium` < `high` < `xhigh` < `max`, so `xhigh` and `max` are already above `high`) AND you are Opus (1M context).
If effort is `low` or `medium` (i.e. below `high`), you MUST show the recommendation prompt — regardless of model.
…Read the whole file at its exact version.
How to install
mdr add etr/groundwork/design-product@sha256:6ae74617a680e3e2The line at the top of this page pins the label git:20260716.aaea421, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bznu6ofqz3ievcq3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 22, 2026 and Jul 16, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260716.aaea421 latest | 2026-07-16 | aaea421 | 16,444 B | A | view · diff |
| git:20260624.e533827 | 2026-06-24 | e533827 | 16,475 B | A | view · diff |
| git:20260622.e142476 | 2026-06-22 | e142476 | 16,335 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16444 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
etr/groundwork · 44 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bznu6ofqz3ievcq3 GET https://markdownregistry.com/api/v1/resolve?ref=etr/groundwork/design-product GET https://markdownregistry.com/api/v1/blob/6ae74617a680e3e2a370de1da80fcee972180ccd01bcf49f9304254f8990703f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.