메뉴
Create a Product Requirements Document (PRD) by interviewing the user about their feature or problem, exploring the codebase, and producing a structured plan. Use when the user wants to plan a feature, write a PRD, or document a proposed change.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | make-a-prd |
| description | Create a Product Requirements Document (PRD) by interviewing the user about their feature or problem, exploring the codebase, and producing a structured plan. Use when the user wants to plan a feature, write a PRD, or document a proposed change. |
This skill will be invoked when the user wants to create a PRD. You should go through the steps below. You may skip steps if you don't consider them necessary.
Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
Once you have a complete understanding of the problem and solution, use the template below to write the PRD. The PRD should be submitted as a GitHub issue.
Write the completed PRD to disk:
date +%s to get the current UTC timestamp.user-auth-refresh, bulk-export-api)..local/prds/${timestamp}-${slug}.md in the current working directory (create the directory if it does not exist).The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
This list of user stories should be extremely extensive and cover all aspects of the feature.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this PRD.
Any further notes about the feature.
Manage Obsidian markdown notes — add new information, update existing notes, and continuously improve vault organization (links, tags, index files). Use when the user wants to remember something, update their notes, improve their knowledge base, or organize their vault.
Create a detailed implementation plan with deep codebase research followed by a structured plan document. Use ONLY when the user specifically asks to "make a plan". More rigorous than make-a-prd — includes deep research and specific implementation details.
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.