Menu
Generate questions, clarify unknowns, then write a PRD using pyramid principles. Sub-skill of the /dev workflow.
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
Search for a product across multiple retailers in parallel, save pricing data to disk, and produce an HTML report with the best deals and direct product links. Use when the user asks to compare prices, find the best deal, or check prices across stores.
Research a topic across multiple sources using parallel tabs, save raw content and findings to files, then produce an HTML report and PDF. Use when the user asks to research, investigate, or gather information on a topic.
Extract structured data from web pages — tables, lists, product info, pricing — into clean CSV, JSON, or markdown tables. Parallelizes across hidden tabs for multi-source extraction and saves results to disk incrementally. Use when the user asks to scrape, extract, or pull data from a page.
Find alternative products to something the user is looking at or considering. Searches across retailers and review sites, compares options, and delivers a ranked HTML report with ratings, pricing, and direct links. Use when the user asks for alternatives, similar products, or "something like this but..."
Bookmark the current page to a "📚 Read Later" folder and save a PDF copy for offline reading. Use when the user wants to save a page for later, bookmark it for reading, or keep an offline copy.
Save web pages as PDF files for offline reading, archiving, or sharing. Use when the user asks to save, download, export, or archive a page as PDF.
| name | dev3-prd |
| description | Generate questions, clarify unknowns, then write a PRD using pyramid principles. Sub-skill of the /dev workflow. |
| argument-hint | ["feature_name"] |
You are writing a Product Requirements Document (PRD) / design spec. Before writing, you must clarify all unknowns.
.llm/$ARGUMENTS/tmp_context.md for the original feature request.llm/$ARGUMENTS/tmp_exploration.md for codebase exploration findings.llm/$ARGUMENTS/design.md for the chosen designThink about what a staff software engineer would need clarified before writing a design spec. Write your questions to .llm/$ARGUMENTS/tmp_questions.md.
For each question:
[RESOLVED] (you found the answer in the code) or [NEEDS INPUT] (requires human clarification)If there are any [NEEDS INPUT] questions remaining, present ONLY those to the user. Wait for their answers. Update .llm/$ARGUMENTS/tmp_questions.md with the answers.
If all questions were self-resolved, tell the user: "No open questions — all clarified from the codebase. Proceeding to PRD."
Write the PRD to .llm/$ARGUMENTS/prd.md following the pyramid principle in three levels:
For each major component or module in the design:
For each component from Level 2:
Show the user a summary of the PRD (Level 1 only) and ask if they want to review the full document or proceed.
Tell the user the PRD is complete, then immediately invoke /dev4-implement $ARGUMENTS.