write-spec

Convert feature ideas into structured PRDs with requirements and success metrics.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill write-spec-ngochuy13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/write-spec
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill write-spec-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you transform a vague feature idea or problem statement into a structured, decision-ready PRD that aligns stakeholders on scope, goals, requirements, and success metrics.

Core Features & Use Cases

  • Structured PRD generation: Produces a complete PRD covering problem statement, goals, non-goals, user stories, requirements (P0/P1/P2), success metrics, and open questions.
  • Scope and prioritization support: Helps prevent scope creep by explicitly defining non-goals and categorizing requirements with acceptance criteria.
  • Decision-ready workflow: Gathers the most important missing inputs first and iterates on the spec after drafting.

Quick Start

Use the command "/write-spec SSO support for enterprise customers who currently struggle with centralized authentication onboarding" to generate a full PRD proposal from your 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 feature idea into a structured PRD with acceptance criteria?

To turn a feature idea into a structured PRD, input your problem statement to generate sections covering goals, non-goals, user stories, MoSCoW-based requirements (P0/P1/P2), success metrics, and acceptance criteria.

What is the best way to write user stories and prevent scope creep during product planning?

The best way to prevent scope creep during product planning is to generate a PRD that explicitly defines non-goals and categorizes requirements using MoSCoW prioritization alongside clear user stories and acceptance criteria.

How to generate success metrics and open questions for feature specification?

You generate success metrics and open questions for feature specification by drafting the initial PRD, which surfaces missing inputs and iterates on the spec to resolve timeline considerations and decision-ready scope.

Can I use MoSCoW prioritization for P0 P1 P2 requirements in my feature specification?

Yes, you can use MoSCoW prioritization to categorize P0, P1, and P2 requirements in your feature specification, ensuring scope management aligns stakeholders on core needs versus deferred items.

Does this PRD generation approach work for enterprise features like SSO onboarding?

Yes, this PRD generation approach works for enterprise features like SSO onboarding by converting centralized authentication problem statements into decision-ready specifications with defined goals and user needs.

What to do when a vague feature idea lacks clear goals and non-goals for a PRD?

When a vague feature idea lacks clear goals and non-goals, the PRD workflow gathers the most important missing inputs first, iterates on the drafted spec, and structures the problem statement into decision-ready sections.