spec-writer

Generates structured Product Requirements Documents from conversation and repository context.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill spec-writer-bing0116-gif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/BING0116-gif/math-AI-assistant/tree/main/.agents/skills/spec-writer
Command: npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill spec-writer-bing0116-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a clarified product idea into a complete, engineer-ready PRD is time-consuming and often produces inconsistent documents. This Skill guides the AI through a structured workflow—collecting the problem description, verifying assumptions against the actual codebase, exploring alternatives, and defining scope—to produce a thorough PRD with minimal back-and-forth. ## Core Features & Use Cases - Structured PRD Template: Produces a ten-section document covering summary, problem statement, goals, user stories, functional and non-functional requirements, architecture notes, risks, and success metrics. - Repo-Grounded Verification: Inspects the codebase to confirm or correct assumptions about existing modules, APIs, and data models before writing requirements. - Scope Definition: Explicitly separates in-scope work from out-of-scope items and follow-ups, including MVP versus full-feature distinctions. - Use Case: After clarifying a new feature idea, ask for a PRD; the Skill interviews you about flows and edge cases, checks the repo for constraints, and outputs a document ready to file as a GitHub issue or feed into implementation planning. ## Quick Start Ask the assistant to write a PRD for your feature idea and provide a detailed description of the problem, target users, and any constraints.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I write a PRD with AI assistance?▼

Provide a detailed description of the problem, target users, and constraints, then invoke the spec-writer skill. It interviews you about flows and edge cases, inspects the repository for existing behavior, and outputs a structured ten-section PRD.

What sections should a product requirements document include?▼

This skill produces a summary, problem statement, goals and non-goals, numbered user stories, functional and non-functional requirements, implementation notes, out-of-scope items, risks and open questions, and success metrics.

Should I clarify my idea before writing a PRD?▼

Yes. The skill assumes major ambiguities are already resolved, for example with a clarification skill like /grill-me. It can perform lightweight clarification itself, but fuzzy ideas should be refined first for better results.

Does the PRD writer check the actual codebase?▼

Yes. The workflow includes exploring the repository to verify user assertions about current behavior, modules, data models, and APIs, and it notes where the repo agrees, disagrees, or is silent.

What are the limitations of AI-generated PRDs?▼

The output quality depends on the detail provided and repo accessibility. Vague requirements trigger clarification questions rather than guesses, and success metrics may remain directional when precise numbers are unavailable.