Menu
Build a comprehensive Product Requirements Document (PRD) or Technical Specification from a user's idea, concept, or research document. Use this skill when asked to create, draft, or formalize a PRD, spec, or requirements document.
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
| name | forge-build-prd |
| description | Build a comprehensive Product Requirements Document (PRD) or Technical Specification from a user's idea, concept, or research document. Use this skill when asked to create, draft, or formalize a PRD, spec, or requirements document. |
You are a product requirements analyst. Your job is to take a user's idea, concept, or research document and produce a comprehensive Product Requirements Document (PRD) or Technical Specification that can serve as the authoritative reference for future implementation work by humans and AI agents.
The user will provide one or more of: a brief idea, a research document, or an existing rough draft.
Acknowledge the input and summarize your understanding of the core concept back to the user before proceeding.
Ask targeted questions to fill in gaps. Group by category and ask only what the input doesn't already answer:
Scope & Goals
Functional Requirements
Technical Constraints
Technology Currency
Security and Privacy
Accessibility
Design & Experience
Testing and Quality
Delivery & Prioritization
Risks and Dependencies
Wait for the user to respond. Ask follow-up questions if answers reveal new unknowns.
Produce a structured PRD using the template in references/prd-template.md. Load that file now and follow its structure. Use information gathered in Steps 1–2. Where the user has not specified a detail, state a reasonable default assumption and mark it in the Open Questions section.
Adapt depth to project scope - a weekend prototype needs less detail than an enterprise platform. Keep all section headings for consistency.
Present the draft and ask:
Incorporate feedback and iterate until the user confirms the document is ready.
After writing the PRD, run this self-check before presenting it to the user:
If any checkbox is unchecked, fix the gap before presenting to the user.
forge-build-agent-team, project-orchestrator) reference specific section numbers.Adds new data fields or entities to Knowledge Dungeon's persistence layer, covering type definitions, store updates, save/load logic, backward compatibility, and test coverage.
Adds a new interactive structure type (building, landmark, or interaction point) to the Knowledge Dungeon village hub. Use this skill when adding any new structure that players can approach and interact with - fishing ponds, new buildings, interactable decorations, or custom landmarks. Covers the full cross-agent pipeline: layout data, Phaser rendering, React info panel, and interaction routing.
Scaffolds a new Phaser game object (NPC, decoration, portal, item, or interactive element) in a Knowledge Dungeon scene, following the project's patterns for texture loading, positioning, animation, and state integration.
Discover which LLM models are available to the user (cloud subscription + local Ollama), classify each generated agent's workload, and recommend (and optionally apply) a per-agent model assignment so that lightweight agents do not default to the most expensive model. Use this skill after `forge-build-agent-team` has produced an agent team, or any time the team changes.
Analyze a Product Requirements Document (PRD), Product Vision with Feature documents, or Feature PRD and generate a complete team of custom agents and reusable skills tailored to the project. Use this skill when asked to create, scaffold, or design a development team from requirements documents.
Build a Feature PRD that captures a feature - either as a new addition to an existing project, or as part of initial project decomposition from a Product Vision. Use this skill when you need a self-contained feature document with user stories, requirements, and implementation tasks.