Menu
Generate a Product Requirements Document (PRD) for a new feature with user stories suitable for autonomous implementation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
| name | prd |
| description | Generate a Product Requirements Document (PRD) for a new feature with user stories suitable for autonomous implementation |
Create detailed Product Requirements Documents that are clear, actionable, and suitable for autonomous AI implementation.
Before generating a PRD, ensure the project has a tasks/ directory. If it doesn't exist, create it:
mkdir -p tasks
tasks/prd-[feature-name].mdAsk questions with lettered options for quick answers:
1. What is the primary goal?
A. Improve user experience
B. Increase performance
C. Add new functionality
D. Other: specify
2. Who is the primary user?
A. End users
B. Administrators
C. Developers
D. Other: specify
3. What is the scope?
A. Single component/feature
B. Multiple related features
C. System-wide change
D. Other: specify
Brief description of the feature.
Specific, measurable objectives.
Each story needs:
Critical: Each story must be small enough to complete in ONE context window.
Right-sized:
Too big (split these):
Numbered list: FR-1, FR-2, etc.
What this feature will NOT include.
Any technical considerations, dependencies, or constraints.
tasks/ directory if it doesn't existtasks/prd-[feature-name].md using a slugified feature nameFor a feature called "User Profile Settings":
tasks/prd-user-profile-settings.md