spec-create

Generate requirements, design, and task files for feature specifications.

1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jrollin/claudio --skill spec-create-jrollin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-create
Source: https://github.com/jrollin/claudio/tree/main/skills/spec-create
Command: npx skills add https://github.com/jrollin/claudio --skill spec-create-jrollin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of defining new features by guiding you through a structured workflow, ensuring all requirements, design decisions, and implementation tasks are clearly documented and traceable.

Core Features & Use Cases

  • Phased Specification: Guides you sequentially through Requirements, Design, and Tasks.
  • Traceability: Establishes clear links between user stories, technical decisions, and implementation tasks.
  • Use Case: When starting a new feature, use this Skill to generate detailed requirements.md, design.md, and tasks.md files, ensuring a solid foundation before coding begins.

Quick Start

Use the spec-create skill to start a new feature specification for 'user authentication'.

Frequently Asked Questions about spec-create

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

FAQPage Schema
How do I create a feature specification from a project idea?

To create a feature specification, this workflow guides you sequentially through Requirements, Design, and Tasks phases, generating detailed traceable documentation including requirements.md, design.md, and tasks.md files before coding begins.

What is spec-driven development and how does it structure requirements?

Spec-driven development structures features by orchestrating a multi-phase workflow that establishes clear traceability links between user stories, technical design decisions, and implementation task breakdowns.

How do I break down software requirements into traceable implementation tasks?

Breaking down requirements into traceable tasks involves analyzing the existing codebase for context, then sequentially processing design decisions and task breakdowns with user approval gates to ensure alignment.

Can I generate design documentation and task breakdowns for an existing codebase?

Yes, the workflow analyzes your existing codebase for context to accurately generate comprehensive design documentation and task breakdowns that integrate with your current software architecture.

Does the specification workflow support test-driven development?

Yes, the specification workflow supports test-driven development by generating traceable documentation that links requirements and design decisions directly to implementation tasks, ensuring solid foundations for TDD.

When should I not use a phased specification workflow?

A phased specification workflow with sequential approval gates should be avoided for rapid prototyping or minor tweaks where the overhead of generating requirements, design, and tasks documentation outweighs the benefits of traceability.