Create a product spec

VerifiedSafe

Create a product spec from a feature title, following a project template.

Sby Skills Guide Bot
DocumentationBeginner
7/26/2026
Claude CodeCursorCodex
#product-spec#backlog#requirements#templates#planning

Recommended for

Automated summary

Generates a new product spec from a feature title or description by assigning the next F-NNNN ID and filling in the project's spec template.

Strengths

  • Automatically assigns the next sequential F-NNNN ID by scanning docs/BACKLOG.md
  • Follows the project's layout: docs/specs/, TEMPLATE.md and kebab-case file naming
  • Populates the core sections (problem, requirements, acceptance criteria, out of scope, dependencies) with explicit defaults
  • Reports back the created file path plus a summary of what was written

Limitations

  • Assumes an existing project structure (docs/BACKLOG.md and docs/specs/TEMPLATE.md) specific to Cloud Workstation
  • Content is inferred from the user's prompt, so requirements and criteria still need team review
  • Relies on a manual backlog scan for the next ID, with no locking against concurrent writes
When to use it

Use it when a PO or developer wants to turn a feature idea, bug, or enhancement into a formatted, numbered spec inside the repository.

When not to use it

Avoid it on repositories that don't use this spec template and backlog layout, or for writing technical documentation that isn't a product spec.

Security analysis

Safe
Quality score85/100

The skill only guides reading the backlog, copying a template, and creating/updating a markdown spec file within the project. It does not request destructive commands, network access, secret handling, or obfuscated actions.

No concerns found

How this analysis is made

Examples

New feature spec
Create a product spec for adding dark mode to the Cloud Workstation dashboard.
Bug spec
Write a spec for a bug where the workstation session times out after 5 minutes of inactivity.
Enhancement spec
Draft an enhancement spec that lets users export their usage report as CSV.

name: spec description: Use this skill to Create a new product spec

Create a new product spec

Trigger

Activate this skill with a feature title or description.

Instructions

  1. Determine the next F-NNNN ID — Read docs/BACKLOG.md and scan for the highest existing F-NNNN ID. The next spec gets the next sequential number (e.g., if the highest is F-0041, the next is F-0042)
  2. Create the spec file — Copy docs/specs/TEMPLATE.md to docs/specs/F-NNNN-short-slug.md where:
    • NNNN is the next sequential ID (zero-padded to 4 digits)
    • short-slug is a kebab-case version of the feature title (e.g., "Add dark mode" becomes add-dark-mode)
  3. Fill in the spec — Update the copied template with:
    • Title: The feature title from the user's input
    • Type: Feature, Bug, or Enhancement (infer from the description, default to Feature)
    • Priority: P1 unless the user specifies otherwise
    • Status: Draft
    • Requested by: PO
    • Date: Today's date
    • Problem: Describe the problem or need based on the user's input
    • Requirements: Numbered list of specific, testable requirements
    • Acceptance Criteria: Checkboxes with measurable criteria
    • Out of Scope: Note what is explicitly excluded
    • Dependencies: List any dependencies on other features
  4. Report back — Show the user the path to the new spec file and a summary of what was created

Project Context

  • Project: Cloud Workstation
  • Owner: Your Name (your-email@example.com)
  • Specs directory: docs/specs/
  • Spec template: docs/specs/TEMPLATE.md
  • Backlog: docs/BACKLOG.md

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-a-product-spec-ms1aw4tr' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-a-product-spec-ms1aw4tr/download' --output '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md.part' && mv '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md.part' '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md' && test -s '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/spec' && cp -R '.skill-downloads/create-a-product-spec-ms1aw4tr' '.claude/skills/spec'

Cursor
test -f '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md' && test -s '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/spec' && cp -R '.skill-downloads/create-a-product-spec-ms1aw4tr' '.cursor/skills/spec'

Codex
test -f '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md' && test -s '.skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/spec' && cp -R '.skill-downloads/create-a-product-spec-ms1aw4tr' '.agents/skills/spec'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/create-a-product-spec-ms1aw4tr'

openskills read 'create-a-product-spec-ms1aw4tr'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-a-product-spec-ms1aw4tr/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills