skills.rest
smartmarbles
smartmarblesCOMMUNITY
Explore all skills by this author →
GitHub

create-spec

Convert user requests into structured feature specifications with intent capture and checkpoints.

4|Updated Apr 2, 2026
Search Tags:#planning#documentation#specification#requirements#handoff#intent
One-click install
npx skills add https://github.com/smartmarbles/helm --skill create-spec-smartmarbles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/smartmarbles/helm/tree/main/.github/skills/create-spec
Command: npx skills add https://github.com/smartmarbles/helm --skill create-spec-smartmarbles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines how SAGE turns a user request into a complete, structured feature specification, including intent capture, checkpoints, and handoff to planning.

Core Features & Use Cases

  • Intent capture: restate the user request in your own words and surface ambiguities before drafting.
  • Structured spec: produce a full artifact with Overview, User Scenarios (P1, P2), Requirements, Success Criteria, and Edge Cases.
  • Handoff and storage: perform a Spec Checkpoint, then write the spec to disk at the designated artifacts path and pause before planning.

Quick Start

Capture the user request to restate intent, perform research as needed, and write a complete spec to disk at artifacts/spec###-short-name/spec.md.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I turn a feature request into a structured specification for development handoff?▼

To turn a feature request into a structured specification, restate the user intent, resolve ambiguities, and generate a formal spec covering Overview, User Scenarios, Requirements, Success Criteria, and Edge Cases before writing it to disk.

What is the best way to capture user intent before writing feature requirements?▼

The best way to capture user intent is to restate the original request in your own words and actively surface any ambiguities or missing context before drafting the formal specification document.

How do I write a feature specification to disk for downstream planning?▼

You write a feature specification to disk by performing a Spec Checkpoint and saving the completed artifact to a designated path like artifacts/spec###-short-name/spec.md, then pausing before planning begins.

What sections should be included in a complete feature specification artifact?▼

A complete feature specification artifact should include an Overview, User Scenarios prioritized as P1 and P2, Requirements, Success Criteria, and Edge Cases to ensure comprehensive development handoff.

Do I need any external dependencies to generate formal feature specifications?▼

No external dependencies are required to generate formal feature specifications. The process relies entirely on internal intent capture and structured outlining to produce the final spec artifact on disk.

When should I use a checkpoint process during specification writing?▼

You should use a checkpoint process during specification writing right before handing off to planning, ensuring the finalized spec is safely written to disk and validated against the structured outline.

Related Skills

Explore More Product & Management Skills→
rickardprickardp
2

blueprint:require

Convert raw requirement descriptions into structured FR or NFR specifications.

Community
Intermediate
mikewatersmikewaters

work-breakdown

Generate Work Breakdown Structures with epics, tasks, dependencies, and estimates for 'bd'.

Community
Advanced
kivo360kivo360
1

moai-project-documentation

Generate product.md, structure.md, and tech.md scaffolds for software projects.

Community
Intermediate
refly-airefly-ai

sdd-development

Convert informal requirements into executable feature specifications and development plans.

Official
Advanced