Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

design-product

Create detailed product requirements document (PRD) for a feature. Usage /groundwork:design-product

etr · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add etr/groundwork --skill design-product

About this skill


name: design-product description: Create detailed product requirements document (PRD) for a feature. Usage /groundwork:design-product argument-hint: "[product-name]" allowed-tools: ["Read", "Edit", "Write", "Glob", "Grep", "Task", "Skill"]

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. If you are not Opus (1M context), you MUST show the recommendation prompt - regardless of model.

Otherwise → use AskUserQuestion:

{
  "questions": [{
    "question": "Do you want to switch? Cross-spec contradiction detection across PRD, architecture, and design system benefits from deeper reasoning.\n\nTo switch: cancel, run `/model opus[1m]` and `/effort high`, then re-invoke this skill.",
    "header": "Recommended: Opus (1M context) at high effort",
    "options": [
      { "label": "Continue" },
      { "label": "Cancel — I'll switch first" }
    ],
    "multiSelect": false
  }]
}

If the user selects "Cancel — I'll switch first": output the switching commands above and stop. Do not proceed with the skill.

Step 0: Resolve Project Context

Before anything else, resolve the project context:

  1. Monorepo check: Does .groundwork.yml exist at the repo root?
    • If yes → Is {{project_name}} non-empty?
      • If empty → Invoke Skill(skill="groundwork:select-project") to select a project, then restart this skill.
      • If set → Project is {{project_name}}, specs at {{specs_dir}}/.
    • If no → Continue to item 3.
  2. CWD mismatch check (monorepo only):
    • Skip if not in monorepo mode or if the project was just selected in item 1 above.
    • If CWD is the repo root → fine, proceed.
    • Check which project's path CWD falls inside (compare against all projects in .groundwork.yml).
    • If CWD is inside the selected project's path → fine, proceed.
    • If CWD is inside a different project's path → warn via AskUserQuestion:

      "You're working from <cwd> (inside [cwd-project]), but the selected Groundwork project is [selected-project] ([selected-project-path]/). What would you like to do?"

      • "Switch to [cwd-project]"
      • "Stay with [selected-project]" If the user switches, invoke Skill(skill="groundwork:select-project").
    • If CWD doesn't match any project → proceed without warning (shared directory).
  3. Check {{specs_dir}}/: Does a specs directory exist?
    • If yes → Single-project repo, proceed normally.
    • If no → Ask the user: "Is this a single-project repo or a monorepo with multiple projects?"
      • Single project → Proceed normally (specs will be created at {{specs_dir}}/)
      • Monorepo → Invoke Skill(skill="groundwork:setup-repo") to create .groundwork.yml, then continue.

Step 0a: Feature-Project Mismatch Check (monorepo only)

Skip this check if:

  • Not in monorepo mode (no .groundwork.yml)
  • The project was just selected as part of Step 0 above (the user explicitly chose)
  • The CWD mismatch check in Step 0 triggered a project switch

If in monorepo mode with a previously selected project:

  • Evaluate whether the requested feature "sounds like" it belongs to the selected project
  • If a mismatch is detected (e.g., user asks to design "push notifications for mobile" but web-app is selected):

    "This feature sounds like it might belong to [other-project] rather than [current-project]. Continue with [current-project] or switch?"

  • If the user confirms the current project, proceed normally
  • If the user wants to switch, invoke Skill(skill="groundwork:select-project") and then continue

Step 0b: Do we have context?

If the user called the skill without any context, ask them to provide context on what feature they want to add, modify or remove.

Step 0c: Load Project Context

Before clarifying the request, load existing specs so you can detect contradictions and understand constraints:

Check for and read (if they exist):

  • {{specs_dir}}/architecture.md (or {{specs_dir}}/architecture/ directory) — technology choices, component boundaries, decision records. Use to catch architecturally infeasible requirements early.
  • {{specs_dir}}/design_system.md — design principles, brand decisions, UX patterns. Use to ensure new features align with established design language.
  • {{specs_dir}}/product_specs.md (or {{specs_dir}}/product_specs/ directory) — already loaded implicitly by the contradiction check, but read it explicitly here for full cross-feature context.

For each, check single file first, then directory. If a directory, aggregate all .md files.

If none exist, that's fine — proceed without them.

Step 1: Understand the Request

Invoke the groundwork:understanding-feature-requests skill to clarify the feature and check for contradictions.

If architecture and design system were loaded in Step 0.5, provide them as context so the clarification can als

Read the complete source ↗