write-spec

Generate a structured PRD from a vague problem statement.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill write-spec-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/product-management-write-spec
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill write-spec-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write Spec helps product teams transform vague ideas or problems into a clear, structured PRD that defines scope, success criteria, and deliverables.

Core Features & Use Cases

  • Structured PRD generation: Converts problem statements into a complete PRD with clearly defined sections.
  • Scope and requirements framing: Identifies goals, non-goals, acceptance criteria, and phased delivery plans.
  • User stories and success metrics: Generates prioritized user stories and measurable success metrics to guide implementation.

Quick Start

Provide a problem statement and context to generate a complete PRD.

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?

Generate a structured PRD by providing your problem statement and context, which produces a document with defined goals, non-goals, user stories, success metrics, and a phased delivery scope ready for review.

What sections should be included in a product requirements document for development handoff?

A PRD for handoff should include a Problem Statement, Goals, Non-Goals, User Stories, Requirements (P0-P2), Success Metrics, Open Questions, and a Timeline to ensure development teams have clear scope and deliverables.

How do I define non-goals and acceptance criteria when planning product features?

Defining non-goals and acceptance criteria involves framing the problem statement to explicitly exclude out-of-scope items while setting measurable user stories and prioritized P0-P2 requirements to guide implementation boundaries.

Can I generate user stories and success metrics from a simple problem statement?

Yes, you can generate prioritized user stories and measurable success metrics directly from a simple problem statement by applying structured PRD generation to transform vague concepts into actionable, implementation-ready deliverables.

What is the best way to phase product delivery scope using a PRD?

The best way to phase product delivery scope using a PRD is to categorize requirements into P0-P2 priorities, aligning user stories with a structured timeline to guide implementation and phased delivery.

When do I need to generate a full PRD instead of just writing user stories?

You need to generate a full PRD instead of just writing user stories when your team requires a comprehensive scope definition including non-goals, success metrics, open questions, and a phased timeline for formal review and handoff.