write-spec

Translate vague ideas into structured feature specifications and PRDs.

Updated Apr 18, 2026

Search Tags:#specification #requirements #goals #prd #product-management #user-stories #open-questions

Ready to run

npx skills add https://github.com/Srujan0798/NRG --skill write-spec-srujan0798

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/Srujan0798/NRG/tree/main/.claude/skills/write-spec
Command: npx skills add https://github.com/Srujan0798/NRG --skill write-spec-srujan0798

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams convert vague ideas and user requests into formal PRDs and feature specifications, reducing ambiguity and aligning stakeholders.

Core Features & Use Cases

Structured PRD generation: Create Problem Statement, Goals, Non-Goals, User Stories, and Requirements in a single document.
Staged planning guidance: Provide timeline considerations and phased delivery options.
Open questions and success metrics: Generate a living set of questions and measurable success metrics to guide execution.

Quick Start

Provide a concise PRD-style specification for a given problem statement or feature idea.

Frequently Asked Questions about write-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn a vague product idea into a structured PRD?▼

Turn a vague idea into a structured PRD by translating problem statements into defined sections like Goals, Non-Goals, User Stories, and Requirements. It guides scoping and aligns stakeholders to reduce ambiguity.

What should be included in a product requirements document for feature specifications?▼

A product requirements document should include a Problem Statement, Goals, Non-Goals, User Stories, Must-Have and Nice-to-Have Requirements, Open Questions, and Timeline considerations to ensure complete feature specifications.

How do I write user stories and acceptance criteria from a rough problem statement?▼

Write user stories and acceptance criteria by processing a rough problem statement through structured scoping. This guides the extraction of specific user needs and translates them into measurable requirements.

Can I generate phased delivery plans and timeline considerations for a new feature?▼

Generate phased delivery plans and timeline considerations for a new feature directly within the PRD. It provides staged planning guidance and timeline options to map out the execution strategy.

What is the best way to define non-goals and open questions during product scoping?▼

Define non-goals and open questions during product scoping by enforcing a strict PRD structure. This ensures boundaries are explicitly set and unresolved queries are tracked as a living set of open questions.