Convert a problem statement into a structured PRD with goals and success metrics.
npx skills add https://github.com/niconiahi/ethernauta --skill write-spec-niconiahi
Please help me install this Agent Skill. Skill: write-spec Source: https://github.com/niconiahi/ethernauta/tree/main/.claude/skills/write_spec Command: npx skills add https://github.com/niconiahi/ethernauta --skill write-spec-niconiahi
This Skill helps you transform a vague feature idea or user request into a clear, stakeholder-ready feature specification that defines what you will build, why it matters, and how success will be measured.
Use the write-spec skill to produce a PRD for your feature by describing the feature or problem statement in one sentence.
High-intent search queries and answers about installing and using this skill.
PRD generation from a problem statement requires a single-sentence feature description to produce a structured product requirements document. This output includes goals, non-goals, categorized requirements, and acceptance criteria for product and engineering alignment.
A product spec should include goals, non-goals, categorized requirements with acceptance criteria, and success metrics. Establishing these structured scope definitions prevents scope creep by clearly defining what you will build.
Defining success metrics and user stories involves structuring your feature spec around a clear problem statement. This process drafts actionable user stories and plans success metrics to measure why the feature matters and how it performs.
You can generate a decision-ready PRD without related documents by proceeding solely from user-provided details. The output will still include open questions and timeline considerations to guide execution and cross-functional alignment.
The best way to structure requirements for engineering alignment is to categorize them by priority and pair each with clear acceptance criteria. This creates a decision-ready document outlining goals, non-goals, and success metrics for execution.
IcekoleGuide PRD creation through user interviews, codebase analysis, and module design.
davzuckyGenerate a structured Product Requirements Document and save it to /tasks/prd-[feature-name].md.
anthropicsGenerate structured PRDs and feature specifications from problem statements.
UnicornDesign UI patterns, components, and design systems for web and mobile applications.
