Generate a structured markdown PRD from a feature prompt.
npx skills add https://github.com/tech-with-seth/iridium --skill prd-tech-with-seth
Please help me install this Agent Skill. Skill: prd Source: https://github.com/tech-with-seth/iridium/tree/main/.github/skills/prd Command: npx skills add https://github.com/tech-with-seth/iridium --skill prd-tech-with-seth
This Skill helps teams transform vague ideas into concrete, actionable PRDs, reducing ambiguity and aligning stakeholders before implementation.
Provide a feature description, and the skill will generate a PRD skeleton and a filled example at tasks/prd-example.md.
High-intent search queries and answers about installing and using this skill.
To turn a feature idea into a structured product requirements document, provide a brief feature description and the skill generates a markdown PRD with sections for Introduction, Goals, User Stories, and Functional Requirements. It asks 3-5 clarifying questions first to resolve ambiguity.
A PRD for new feature planning should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions. This structure ensures stakeholders align on scope and constraints before implementation.
You can generate a PRD skeleton quickly by providing a feature prompt to the skill, which outputs a filled markdown example at tasks/prd-example.md. This creates an immediate baseline document for stakeholder review.
Yes, you can document product initiatives across teams without writing a PRD from scratch by supplying the initial concept to the skill. It automatically structures the initiative into a standardized markdown document at tasks/prd-[feature-name].md.
Yes, the PRD generator asks 3-5 essential clarifying questions before creating the requirements document to surface key trade-offs and constraints. This reduces ambiguity and aligns stakeholders on the final feature scope.
The best way to reduce ambiguity when planning new product features is to answer 3-5 automated clarifying questions before generating the PRD. This surfaces key trade-offs and constraints early, ensuring stakeholders align before implementation.
openyidaConvert DingTalk flash notes into structured PRD markdown files.
tech-leads-clubPlan and execute software projects through four specification-driven phases.
phuakyGenerate structured PRD sections with testable acceptance criteria from product ideas.
YH-05Create project directories, documentation, and GitHub project boards.
