specification-writing-skill

Create feature specifications with user stories, FRs, scenarios, and acceptance criteria.

Updated Jan 15, 2026

Search Tags:#specification #requirements #product-management #user-stories #acceptance-criteria #phase-planning #frs

Ready to run

npx skills add https://github.com/SalmanO7/Todo_Full-Stack --skill specification-writing-skill-salmano7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specification-writing-skill
Source: https://github.com/SalmanO7/Todo_Full-Stack/tree/main/.claude/skills/spec-writing
Command: npx skills add https://github.com/SalmanO7/Todo_Full-Stack --skill specification-writing-skill-salmano7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams craft precise, reusable feature specifications for Spec-Driven Development, reducing ambiguity and rework.

Core Features & Use Cases

Structured specs: defines clear FRs, scenarios, entities, and acceptance criteria.
Phase-aligned templates: maps features to project phases and milestones.
Reusability & guidance: provides prompts and phase-based prompts history records to accelerate specification work.

Quick Start

Create a complete feature specification for a new user sign-up flow.

Frequently Asked Questions about specification-writing-skill

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

FAQPage Schema

How do I write feature specifications to prevent scope ambiguity?▼

Feature specifications prevent scope ambiguity by defining clear functional requirements, user stories, scenarios, and acceptance criteria to guide development. Structured specs reduce rework by mapping features to specific project milestones and phase directories.

What is the best way to structure product requirements for multiple project phases?▼

The best way to structure product requirements across phases is using a phase-aligned folder structure with naming conventions for directories. This approach maps features to project milestones, ensuring traceability and organization throughout the development lifecycle.

How do I create user stories and acceptance criteria for a new product feature?▼

Create user stories and acceptance criteria by drafting a feature specification that includes functional requirements and scenarios. This guided process ensures all acceptance criteria align with the defined functional requirements and project phase expectations.

Can I use a phase-based template for drafting functional requirement specifications?▼

Yes, you can use phase-based templates for drafting functional requirement specifications. These templates provide structured prompts and history records, accelerating specification work while ensuring all features map correctly to project phases and milestones.

Why do I need to map user stories to specific project milestones?▼

Mapping user stories to project milestones prevents scope ambiguity by aligning feature development with specific project phases. This phase-based specification approach ensures functional requirements and scenarios are tracked accurately throughout the development lifecycle.

Specification writing is not reducing rework, what am I missing?▼

If specification writing is not reducing rework, ensure your specs include precise functional requirements, scenarios, entities, and acceptance criteria. Adopting a phase-aligned folder structure with defined naming conventions provides the necessary guidance to eliminate ambiguity.