spec

Generate FeatureSpec JSON and markdown specs from product descriptions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/kelsi-andrewss/capstone-toolkit --skill spec-kelsi-andrewss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/kelsi-andrewss/capstone-toolkit/tree/main/skills/spec
Command: npx skills add https://github.com/kelsi-andrewss/capstone-toolkit --skill spec-kelsi-andrewss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stops teams from guessing at requirements by turning a product name and natural description into a comprehensive feature spec that includes objective, stories, requirements, constraints, integration notes, and FeatureSpec JSON for Claude Code workflows.

Core Features & Use Cases

  • Clarified objectives: Extracts the what and why of a feature, scopes product versus feature work, and ensures every spec section is grounded in the user’s intent before generation.
  • Interactive refinement loop: Runs clarification rounds to resolve coverage gaps, offers suggested answers, and tracks which sections have been covered so Claude builds the spec responsibly.
  • Generated outputs: Produces markdown specs ready for /factory with decision pre-checks, integration recommendations, and FeatureSpec JSON, ensuring every merge gate has a contract before implementation.

Quick Start

Ask Claude Code to run /spec MyProduct with the natural-language description so it builds the spec and FeatureSpec JSON for review.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn a product idea into a structured feature spec?

To turn a product idea into a structured feature spec, provide a natural-language product name and description. The skill extracts objectives, stories, requirements, constraints, and integration notes to align teams.

What is a FeatureSpec JSON file and when do I need it for Claude Code?

A FeatureSpec JSON file is a structured data format representing feature requirements. You need it for Claude Code workflows to ensure every merge gate has a contract before implementation.

How do I resolve missing requirements when generating feature specs?

To resolve missing requirements when generating feature specs, use an interactive clarification loop. This process runs refinement rounds, identifies coverage gaps, and suggests answers.

Does the spec skill work with markdown outputs for product planning?

Yes, the spec skill produces markdown outputs for product planning. These generated markdown specs are ready for /factory workflows and include decision pre-checks and integration recommendations.

Can I scope product versus feature work using acceptance criteria generation?

Yes, you can scope product versus feature work during acceptance criteria generation. The skill clarifies the what and why of a feature, ensuring every spec section grounds itself in user intent.

Why does my feature spec lack decision memory for integration notes?

Your feature spec lacks decision memory for integration notes if decision pre-checks are skipped. The skill tracks decision checks and integration recommendations to build a comprehensive specification.