メニュー
Generate a Product Requirements Document (PRD) in Markdown. Use when the user asks to create a PRD, write product requirements, define a new feature, or mentions /create-prd. Cowork-ready.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-prd |
| description | Generate a Product Requirements Document (PRD) in Markdown. Use when the user asks to create a PRD, write product requirements, define a new feature, or mentions /create-prd. Cowork-ready. |
Generate a clear, actionable PRD suitable for a junior developer to understand and implement.
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Receive initial prompt
- [ ] Step 2: Determine save location
- [ ] Step 3: Ask clarifying questions
- [ ] Step 4: Generate PRD
- [ ] Step 5: Iterate based on feedback
The user provides a brief description of a new feature or functionality.
If the user's prompt includes a path (e.g., "save in Docs/Voting/"), use that. Otherwise, ask where to save the PRD within the Docs/ directory.
Filename: prd-[feature-name].md
Before writing the PRD, ask clarifying questions to understand the "what" and "why" — not the "how." Adapt questions to the prompt, drawing from these areas:
Based on the prompt and answers, generate a PRD with these sections:
Target audience: junior developer. Requirements must be explicit, unambiguous, and avoid unnecessary jargon.
Present the PRD to the user. Incorporate feedback and refine.
Use this skill to apply the PDD framework to a specific project. Triggers whenever a user wants to: review a project through a PDD lens, check how PDD principles apply to their work, get tool recommendations for a project, audit a project against PDD, or understand what PDD means in practice for a specific brief or context. Also trigger when the user says "apply PDD", "which tools should we use", "how does PDD apply here", "what should we do next", or "map this project to PDD" — even if they don't explicitly name a skill. Cowork-ready.
Use this skill to create Purpose-Driven Design (PDD) Archetype documents from user interview data. Trigger whenever a user wants to: synthesize interview data into archetypes or personas, generate archetype documents with goals/frustrations/needs/habits/quotes/demographics, or analyze user research to identify audience segments. Also trigger when the user says "archetypes", "PDD archetypes", "persona documents", or "synthesize interviews into archetypes" — even if they don't call it a skill. (To build a participant summary spreadsheet, use the pdd-interview-summary skill.) Cowork-ready with the Figma remote MCP connector enabled — it builds the FigJam board via `create_new_file` + `use_figma`, both remote-server (write-to-canvas) tools reached over the agent's MCP transport rather than the local Dev Mode bridge; pending live verification.
Use this skill to run a Purpose-Driven Design (PDD) Competitive Analysis. Triggers whenever a user wants to: compare competitors, benchmark a client's product or website against rivals, evaluate market landscape, score competitors on UX or business criteria, or create a competitive analysis spreadsheet. Also trigger when the user says "competitive analysis", "compare competitors", "benchmark", "landscape review", "audit competitors", "score products against each other", or asks "how does our client compare to X" — even if they don't explicitly call it a skill. The output is a formatted .xlsx file matching the Infinum/ETR competitive analysis template (IBM Plex Sans font, blue header bar, grey category rows, 1–3 scoring with rationale columns). Cowork-ready.
Use this skill to plan a discovery workshop for a client project. Reads the project information (goals, scope, stakeholders, time available) and recommends a plan — a warm-up plus 1–2 longer exercises (sessions are usually 1–2 hours) from the Infinum/ETR activity library, sequenced to fit the time. Triggers whenever a user wants to: plan or design a discovery workshop, build a workshop agenda or run-of-show, choose workshop activities, prepare a kick-off / alignment / ideation session with a client, or set up a FigJam facilitation board. Also trigger when the user says "discovery workshop", "workshop plan", "workshop agenda", "kickoff workshop", "facilitation board", "which exercises should we run", or "plan a session with the client" — even if they don't call it a skill. Output is a formatted .docx run-of-show plus a FigJam board scaffold (one section per activity). Cowork-ready — the .docx run-of-show uses Cowork's built-in docx toolchain, and the FigJam board builds via the Figma remote MCP connector (`cre
Use this skill to build a project estimate on the standard ETR/Infinum estimate template. It reads the project brief or RFP, benchmarks against past estimates in the team's Estimates drive, proposes a feature list with draft hours per department (Discovery, Content/SEO, UX, Design, Dev, PM), and fills the official estimate spreadsheet — keeping all of its built-in formulas. Estimates are in hours only; it never outputs dollar amounts. Triggers whenever a user wants to: estimate a project, scope hours, build an hours estimate, fill out the estimate template/sheet, price an RFP, or figure out how long a build will take. Also trigger when the user says "estimate", "estimate sheet", "scope this", "how many hours", "price this RFP", or "fill out the estimate" — even if they don't call it a skill. Output is a filled .xlsx (hours only, no dollar amounts) with all formulas intact (a local file; nothing is written to Drive). Cowork-ready.
Use this skill to build a Participant Summary spreadsheet from user-interview data — a reference table with one row per participant mapped across key dimensions (Audience Type, Goals, Habits, Frustrations, Needs, and any custom columns). It's a useful synthesis step before identifying archetypes or running a rainbow analysis. Triggers whenever a user wants to: summarize interview participants, build a participant summary/grid/matrix, map participants across dimensions, or create a per-participant reference table from transcripts or notes. Also trigger when the user says "participant summary", "participant grid", "summarize the participants", or "map participants across goals/frustrations/needs" — even if they don't call it a skill. Output is an `.xlsx` spreadsheet. Cowork-ready.