{'>'}_
English 繁體中文 日本語 한국어 Deutsch Español Français
Login

Comprehensive skill for Product Managers to create organize and manage Product Teams, Strategy, PRDs, release plans, user stories, and standalone issues with high-quality acceptance criteria. Supports both full documentation workflows (PRD → Plan → Stories) and quick issue creation (standalone stories, tasks, bugs). All documentation follows design-driven development principles with functional, testable acceptance criteria based on visual designs and user flows.

9 stars
2 forks
18 views
View on GitHub Add to Favorites

SKILL.md

name: product-spec-kit description: Comprehensive skill for Product Managers to create organize and manage Product Teams, Strategy, PRDs, release plans, user stories, and standalone issues with high-quality acceptance criteria. Supports both full documentation workflows (PRD → Plan → Stories) and quick issue creation (standalone stories, tasks, bugs). All documentation follows design-driven development principles with functional, testable acceptance criteria based on visual designs and user flows.

Overview

This skill helps Product Managers produce structured, high-quality documentation for product development. It supports both comprehensive documentation workflows (PRD → Plan → Stories) and standalone quick issues (individual stories, tasks, or bugs).

Always use the language of the user interaction to create the final files, including headings and default content of templates. If the user explicitly requests a different language, use it.

When to use?

Use this skill when user asks to:

  • Create a PRD specification
  • Create an epic and your stories/tasks
  • You need to create or clarify a product specification, such as a Product Requirements Document (PRD), a Release Plan, or a User Story.
  • It can also be used to create standalone PRD, Plan, Story, Task or Bug.

Core Principles Constitution

All documentations need to follow the constitution defined in rules/product-speckit-constitution.md. This constitution is a set of non-negotiable principles that govern all product documentation created with this skill. These principles apply regardless of language, workflow type (full or quick), or document format.

Principle I: Complete & Unambiguous Requirements

Every requirement must be clear enough that a reader with no prior context can understand what's needed and why.

Principle II: Design-Driven Acceptance Criteria

Acceptance criteria should be based on visual designs, user flows, and specific UI elements - never written from assumptions.

Principle III: Functional Over Descriptive

Criteria must describe what the system does, not what it looks like. Focus on behavior, actions, and outcomes.

Principle IV: Right Level of Detail

  • PRDs: Macro-level requirements and general rules
  • Stories: Detailed, functional acceptance criteria
  • Each document serves its purpose without overlap

Principle V: Never Assume, Always Validate

When information is missing or ambiguous:

  • Ask specific questions
  • Request designs/mockups
  • Reference previous discussions
  • Mark uncertain items for validation
  • Wait for confirmation before finalizing

Workflows or Commands

  • Starting the interaction - how to start a new specification: If the user don't provide the type of specification want to build, always ask for it, using the workflows/prod-start.md instructions. Ignore the start step if the user provide the type of specification want to build.
  • Creating a PRD: When the user want to create a PRD, use the workflows/prod-spec-prd.md instructions.
  • Clarifying an specification: When the user want to clarify an specification (such as PRD, Plan, Story, Task or Bug), use the workflows/prod-clarify.md instructions. If the user doesn't provide an existing specification, ask for it.
  • Breakdown specs: When the user want to break the PRD in smaller parts such as Epics -> Stories / Tasks, use the workflows/prod-spec-breakdown.md instructions. You need to validate an existing PRD or create the PRD before breaking it down. If the user doesn't provide an existing PRD, ask for it.
  • Creating a Story: When the user want to create a story, use the workflows/prod-spec-story.md instructions.
  • Creating a Task: When the user want to create a task, use the workflows/prod-spec-task.md instructions.

README

date_modified: 2025-11-13

README

A comprehensive framework for creating and managing product documentation with AI assistance. Perfect for both new projects and existing products, helping teams maintain high-quality specifications from concept to implementation.

Focused on the specification phase, this kit empowers Product Managers and Designers to create clear, actionable specs for AI applications and standard processes.

Compatible with any LLM platform supporting Projects or Claude Skills, with a file structure that follows standard IDE conventions for easy integration.

✨ Why Use This Kit?

  • AI-Powered Documentation: Leverage AI to create, refine, and maintain your product specifications
  • Structured Workflows: Clear processes for every stage of product development
  • Time-Saving Templates: Ready-to-use templates for all your documentation needs
  • Consistent Quality: Built-in validation ensures high standards across all documents
  • Seamless Integration: Works with your existing tools and workflows

Installation

  1. Download this repository.
  2. For Claude Skills: follow the official instructions.

For other LLM platforms

  1. unzip the repository;
  2. Open your preferred LLM and create a new project;
  3. Copy the following files to the new LLM project:
    • SKILL.md file
    • Copy all markdown files from the workflows, rules, templates, and example of respository folders
    • Add the following instructions to your project configuration:
You will help managers and product teams to create and maintain high-quality product specifications. You will use the all the guidelines and instructions, step by step described in the SKILL.md located in the project base knowledge.

Some descriptions may reference files using relative paths (e.g., `templates/prd-template.md` or `workflows/create-prd.md`). The content of these files is available in the project's base knowledge; you can safely ignore the file paths.

Before proceeding, carefully review the SKILL.md file. This is your primary reference that centralizes all instructions and rules for the Product Spec Kit. Reading this file first is essential for proper implementation.

Quick Start

After installation, you can start using the Product Spec Kit by using the following prompts. If you are using Claude Skills, try:

I want to create a PRD using Product Spec Kit instructions, with following informations:

We will build a simple to-do list product called *Awesome Todo List*. Build the PRD following this informations:

- The want to benefit users who have problems with an effective organization using tasks to direct the main objectives of their day and week.
- We want to create a simple frictionless product, without bureaucracy, so people can organize themselves without large bureaucracies. 
- The flow is simple: The user enters the page, add to-dos, without having to login or signup.

- Some functional criteria:
    - The to-do list doesn't have login/signup
    - The todos are saved locally in the browser. If the user change the browser or device, the todos is not saved or synced.
    - user can add a due date
    - user can add title and description of the todo
    - user can add labels, separated by comma, starting with #
    - user can delete a todo
    - user can mark as done a todo
    - user can edit the todos.
    - user can mark priority of high, medium and low in todos
    - It doesn't need bulk actions.
    - Export/Import and notifications will be for future evolutions. Just like filters, sorting and project folders.

When using with other LLM Projects, don't forget to add the instructions above in LLM Project Instructions.

Other examples:

  • "I want to create a PRD for push notifications, using following informations to create it and guide me through the process."
  • "Breakdown a PRD into epics and stories"
  • "Breakdown a Epic into stories / tasks"
  • "Help me clarify my PRD"

Built with ❤️ for product teams who believe in the power of great documentation to potentialize value for business and users.

Contributing

This project evolves based on user needs. We welcome your feedback and contributions!

Special thanks to the spec-kit team for their inspiring work that helped shape this project.

📄 License

Open source - use freely for your product documentation needs.