1  # PRCSS* — Product Design Skill for Claude
  2  
  3  A Claude skill that lets product & UX designers kickstart and run end-to-end design projects using the **PRCSS\*** framework — a 7-phase, Double-Diamond-inspired workflow by Wojciech Pawlak (PRCSS*, Paris).
  4  
  5  Ask Claude for a project scaffold, a phase plan, or a single Design Method card, and you get back a clean Markdown deliverable that follows the PRCSS* conventions (phases, statuses, method card shape) — ready to paste into any tool (wiki, kanban, docs, Figma), with no tool lock-in.
  6  
  7  ---
  8  
  9  ## What it gives you
 10  
 11  - A tracker-agnostic **project scaffold**: Project Info (Brief, Objectives, Stakeholders, Team, Metrics) + Project Workflow grouped by phase + reusable Design Methods library.
 12  - **Phase-level plans** with 3–6 recommended Design Methods each, drawn from the original PRCSS* method set.
 13  - **Canonical Design Methods preserved verbatim** from the source template: More than 36 Design methods.
 14  - An **interactive kickoff**: Claude asks 4 multiple-choice questions (Mode, Phase, Scope, Output) before producing anything, so you don't get a 2,000-word scaffold when you wanted a single method card.
 15  - Hooks into the rest of the `design:*` skill family (research synthesis, accessibility review, UX copy, design critique, developer handoff) while keeping PRCSS* phase/method tagging.
 16  
 17  The 7 phases:
 18  
 19  | | Phase | Intent |
 20  |---|---|---|
 21  | 🔍 | Discover | Understand users, context, and the real problem. |
 22  | 🎯 | Define | Frame the problem, goals, scope. |
 23  | 🧠 | Ideate | Generate divergent solution options. |
 24  | 🧪 | Design | Produce tangible artifacts (IA, wireframes, UI). |
 25  | 🪄 | Test | Validate with users and stakeholders. |
 26  | 📦 | Deliver | Hand off, ship, document. |
 27  | 📏 | Measure | Track KPIs and design metrics post-launch. |
 28  
 29  ---
 30  
 31  ## Install
 32  
 33  Pick the option that matches how you run Claude.
 34  
 35  ### Option A — Cowork desktop app (recommended)
 36  
 37  Open `prcss-product-design.skill` in Finder. Claude for desktop surfaces an **"Install skill"** button. Confirm and the skill is available immediately in any new conversation.
 38  
 39  ### Option B — Claude Code or local skills folder
 40  
 41  ```bash
 42  # Unzip the skill next to your other skills
 43  unzip prcss-product-design.skill -d ~/.claude/skills/prcss-product-design
 44  ```
 45  
 46  Restart your session.
 47  
 48  ### Option C — Cowork plugin (marketplace-ready)
 49  
 50  `prcss-product-design.plugin` bundles the skill with a plugin manifest. Open it in Cowork and click **"Install plugin"**. Useful if you plan to ship this to a team alongside other skills/commands.
 51  
 52  ### Option D — From source (GitHub)
 53  
 54  ```bash
 55  git clone <this-repo>
 56  cd prcss-product-design
 57  # Either zip it into a .skill yourself…
 58  zip -r ../prcss-product-design.skill . -x "*.DS_Store" -x "README.md" -x "LICENSE" -x "NOTICE"
 59  # …or drop the folder directly into ~/.claude/skills/
 60  cp -R . ~/.claude/skills/prcss-product-design
 61  ```
 62  
 63  ---
 64  
 65  ## How to use it
 66  
 67  Once installed, any message that mentions PRCSS or a product design workflow triggers the skill. Claude opens with a single multiple-choice kickoff:
 68  
 69  > **Mode** — Full project scaffold / Brief + Objectives / Single phase plan / Single method card
 70  > **Phase** — Discover / Define / Ideate / Design|Test|Deliver|Measure
 71  > **Scope** — Small (1–2 weeks) / Medium (1–2 months) / Large (quarter+)
 72  > **Output** — One Markdown file / Folder of Markdown files / Paste-ready snippet
 73  
 74  Your answers decide which files Claude loads and what it produces.
 75  
 76  ### Example prompts
 77  
 78  **1. Full project scaffold**
 79  > *Use PRCSS to scaffold a project to redesign the mobile checkout for a B2C marketplace. Deadline end of Q3.*
 80  
 81  Claude asks the 4 kickoff questions, then asks for context/brief, objectives, stakeholders, team, and KPIs. Outputs a Markdown project page with Project Info, a Project Workflow grouped by phase, and a seeded Design Methods library.
 82  
 83  **2. Phase-level plan**
 84  > *Give me a Discover plan for a B2B SaaS onboarding redesign.*
 85  
 86  Claude reads `references/phases/discover.md`, proposes 3–6 Design Methods (stakeholder interviews, desk research, heuristic audit…), and returns them as method cards ready to drop into your plan.
 87  
 88  **3. Single method card**
 89  > *Write me the Brief method for Project Atlas following PRCSS.*
 90  
 91  Claude reads `references/methods/brief.md` (verbatim content from the original Notion template) and fills in the 6 steps with your project's specifics.
 92  
 93  **4. Non-trigger check**
 94  > *Explain OAuth.*
 95  
 96  The skill should NOT load. If it does, sharpen the `description:` frontmatter.
 97  
 98  ---
 99  
100  ## What's in the box
101  
102  ```
103  prcss-product-design/
104  ├── SKILL.md                          # Skill entry point + kickoff logic
105  ├── README.md                         # You are here
106  ├── LICENSE                           # MIT — covers this skill packaging
107  ├── references/
108  │   ├── framework-overview.md         # 7 phases + rules + loop logic
109  │   ├── project-template.md           # The canonical Project page structure
110  │   ├── phases/
111  │   │   ├── discover.md · define.md · ideate.md
112  │   │   ├── design.md · test.md · deliver.md
113  │   │   └── measure.md
114  │   └── methods/                      # Design Methods library (35 cards)
115  │       ├── README.md                 # Index by phase
116  │       ├── brief.md · objectives.md  # Canonical (verbatim from source)
117  │       └── …                         # 33 more methods across the 7 phases
118  └── templates/
119      ├── project-skeleton.md           # Fill-in-the-blanks Markdown scaffold
120      └── method-card-template.md       # Shape of a Design Method card
121  ```
122  
123  ---
124  
125  ## Design principles behind the skill
126  
127  - **Tracker-agnostic.** Outputs are plain Markdown — no Notion or Jira dependency. Paste where you like.
128  - **Progressive disclosure.** `SKILL.md` stays under 3k words; detailed knowledge lives in `references/`. Claude only loads what the current mode needs.
129  - **Preserve the original voice.** Callouts, section titles, and the two canonical methods (Brief, Objectives) are reproduced verbatim from the original PRCSS* template.
130  - **Loopable, not waterfall.** Phases are tags, not steps. The framework assumes Discover ↔ Define ↔ Ideate ↔ Test cycles.
131  
132  ---
133  
134  ## Credits
135  
136  Framework and skill by **Wojciech Pawlak (PRCSS\*)** — Paris. Version 0.5.1. Licensed MIT (see `LICENSE`).
137  
138  > **v0.5.1 fix**
139  > - Kickoff uses `ask_user_input_v0` (available in all Claude environments: Chat, app Mac, Cowork). `AskUserQuestion` is explicitly banned — it's Cowork-only and causes "Tool result could not be submitted" everywhere else.
140  >
141  > **v0.5.0 highlights**
142  > - **Design Actions → Design Methods** rename (aligns with IDEO / NN/g vocabulary; the Notion source still uses "Actions").
143  > - Method card template adds a project-instance metadata block, numbered steps, and a feedback footer.
144  
145  ## Feedback
146  
147  - About the **framework** (phases, methods, conventions): [prcss.design@gmail.com](mailto:prcss.design@gmail.com).
148  - About the **skill** (install, triggers, output format): open an issue on this repository.