メニュー
Comprehensive PRD (Product Requirements Document) management skill for creating, planning, and implementing PRDs. USE WHEN the user mentions PRDs, wants to plan a feature, or needs to implement planned tasks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Test NixOS configuration changes using the feedback ladder — from instant syntax checks to full system builds. USE WHEN the user wants to verify, test, or check NixOS changes before deploying.
Review and fix documentation surprises discovered by the surprise hook. USE WHEN the user wants to fix documentation issues, review surprises, or address items in .claude/surprises/.
Query systemd journal logs, check service status, diagnose failed units, and analyze boot performance. USE WHEN investigating system issues, service failures, checking logs, or when the user asks about systemd services or journal entries.
Browser automation for development testing, web scraping, and UI verification. USE WHEN you need to interact with web pages, verify UI changes, take screenshots, or extract data from websites.
Systematically explore and test a web application to find bugs, UX issues, and other problems. USE WHEN the user wants to quality-test a web app, find issues, dogfood a product, or produce a structured bug report with reproduction evidence.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) via Chrome DevTools Protocol. USE WHEN the user needs to interact with an Electron desktop app, automate a native app, connect to a running Electron app, or test an Electron application.
| name | PRD |
| description | Comprehensive PRD (Product Requirements Document) management skill for creating, planning, and implementing PRDs. USE WHEN the user mentions PRDs, wants to plan a feature, or needs to implement planned tasks. |
| model | opus |
You manage PRDs (Product Requirements Documents) through their complete lifecycle. Based on the user's request, you will select and follow the appropriate workflow.
Read PRD Spec: You MUST read the PRD specification completely before proceeding: @./reference/prd-spec.md
Gather Context: If a PRD name is mentioned or implied:
claude-PRD-list-prds to verify the PRD existsclaude-PRD-task-status <prd-name> to understand current stateDetermine Intent: Analyze the user's request to identify:
Select Workflow: Select the appropriate workflow based on the user's intent and trigger words:
Execute Workflow: Report to the user "Running using the PRD skill..." You MUST read the workflow document completely before proceeding, then follow the workflow's process completely
Report Results: Summarize what was accomplished and suggest next steps
| Workflow | Trigger Words | When to Use |
|---|---|---|
| CreatePRD | "create", "new", "start", "begin", "draft", "write" | User wants to create a new PRD from scratch, define a new feature, or start planning something new |
| PlanPRD | "plan", "analyze", "research", "refine", "complete", "fill out", "detail" | User has an existing PRD that needs analysis, research, task generation, or refinement |
| WorkPRD | "work", "implement", "build", "execute", "do", "code", "develop" | User wants to implement tasks from a planned PRD |