write-spec

Generate a structured PRD template from a problem statement or feature idea.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write clear, structured product requirements documents from a problem statement or feature idea to accelerate alignment and handoffs.

Core Features & Use Cases

  • Gathers context from problem statements, user requests, and vague ideas.
  • Generates a complete PRD template including problem, goals, user stories, requirements, acceptance criteria, and timeline.
  • Produces ready-to-share PRDs suitable for roadmaps, planning sessions, and epic creation.

Quick Start

Create a PRD from a problem statement or feature idea by outlining the problem, goals, scope, user stories, and acceptance criteria.

Frequently Asked Questions about write-spec

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

FAQPage Schema
How do I create a PRD from a rough product idea or user request?

To create a PRD from a rough product idea, you provide a problem statement or feature concept to generate a structured document. The output details the problem, goals, user stories, requirements, success metrics, timeline, and decision criteria for stakeholder review.

What should a product requirements document include for roadmap planning?

A product requirements document for roadmap planning should include the core problem, goals, user stories, requirements, acceptance criteria, success metrics, and timeline. This structure ensures the feature specification is ready for epics and stakeholder alignment.

Can I generate user stories and acceptance criteria directly from a problem statement?

Yes, you can generate user stories and acceptance criteria directly from a problem statement. The Skill transforms vague concepts and feature ideas into a formal PRD template that explicitly outlines these elements for development handoffs.

What is the best way to structure feature specifications for stakeholder review?

The best way to structure feature specifications for stakeholder review is using a formal PRD template. It should clearly define the problem, scope, goals, user stories, requirements, success metrics, and decision criteria to accelerate alignment.

Does this tool work for turning vague feature concepts into ready-to-build epics?

Yes, this tool works for turning vague feature concepts into ready-to-build epics. It gathers context from user requests and ideas to produce a structured PRD suitable for direct integration into your planning sessions and roadmap.