Skip to content
TrustedSkillsbeta
Back to all skills

Product Spec Kit

Checked
diegoeis·vlatest·writing

Generates a comprehensive product specification kit, streamlining requirements gathering and ensuring consistent documentation for successful projects.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add diegoeis/product-spec-kit --skill product-spec-kit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

diegoeis

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned diegoeis/product-spec-kit at 1b4e84ed0c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1b4e84ed0c
Manifest
SKILL.md
Scanned
14 files, 2,092 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Product Spec Kit skill assists Product Managers in generating structured, high-quality documentation for product development. It supports both comprehensive workflows (Product Requirements Document [PRD] → Plan → User Stories) and standalone document creation like individual stories or bug reports. The tool ensures consistency by adhering to a defined constitution and mirroring the user’s language in generated documents.

When to use it

  • Creating a Product Requirements Document (PRD).
  • Generating an epic and associated user stories/tasks.
  • Clarifying existing product specifications like PRDs, Release Plans, User Stories, Tasks or Bugs.
  • Producing standalone documentation for individual items such as a PRD, Plan, Story, Task, or Bug.

Key capabilities

  • Generates Product Requirements Documents (PRDs).
  • Creates epics and associated user stories/tasks.
  • Supports clarification of existing product specifications.
  • Adheres to a defined constitution for consistent documentation principles.
  • Uses the language specified by the user in generated documents.

Example prompts

  • "Create a PRD for our new mobile app feature."
  • "Can you help me break down this PRD into smaller stories and tasks?"
  • “I need to clarify some acceptance criteria for an existing User Story.”

Tips & gotchas

  • The skill operates according to a constitution (rules/product-speckit-constitution.md) that dictates principles like clear requirements, design-driven acceptance criteria, and functional descriptions over visual details. These principles are non-negotiable.
  • If you don't specify the type of specification you want to create initially, the skill will ask for clarification.
  • To break down a PRD into smaller parts (Epics/Stories), you must first either validate an existing PRD or create one.