spec-mode

Organize project work into traceable spec packs with TASK, Requirements, and Design artifacts.

31|4|Updated Apr 6, 2026

Search Tags:#design #planning #specification #requirements #traceability #spec-mode

Ready to run

npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill spec-mode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-mode
Source: https://github.com/kissrosecicd-hub/agents-evolution/tree/main/.agents/skills/spec-mode
Command: npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill spec-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill helps teams translate complex projects into formal spec packs that preserve traceability between tasks, requirements, and design, reducing ambiguity and miscommunication.

Core Features & Use Cases

Phase-based governance: enforce discovery, formalization, and verification before delivering specs.
Traceability: maintain Task -> Requirements -> Design links across independent workstreams.
Scoped spec packs: create .spec/<slug>/TASK.md, Requirements.md, and Design.md to organize work.

Quick Start

Provide a project idea and ask to scaffold a new spec pack; the AI will propose top-level tasks, requirements, and a design outline, and place them under .spec/<slug>/.

Frequently Asked Questions about spec-mode

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

FAQPage Schema

How do I structure project requirements with traceable tasks across independent workstreams?▼

You can structure project requirements by organizing work into formal spec packs containing traceable TASK, Requirements, and Design artifacts. This enforces phase-based governance with explicit ownership and phase transitions across independent workstreams.

What is phase-based governance for project specifications and how does it work?▼

Phase-based governance for project specifications enforces discovery, formalization, and verification stages before delivering specs. It works by requiring explicit phase transitions and clear deliverables to reduce ambiguity and miscommunication in complex projects.

How do I scaffold a new spec pack from a project idea?▼

To scaffold a new spec pack, provide a project idea and request scaffolding. The system proposes top-level tasks, requirements, and a design outline, then places these artifacts into the .spec/<slug>/ directory structure for organized tracking.

When do I need formal specification packs for product initiatives?▼

You need formal specification packs when product initiatives involve independent workstreams that must be scoped, planned, and tracked across teams. This approach preserves traceability between tasks, requirements, and design to reduce ambiguity.

Can I maintain traceability between tasks, requirements, and design artifacts in markdown?▼

Yes, you can maintain traceability by generating TASK.md, Requirements.md, and Design.md files within scoped .spec/<slug>/ directories. These files preserve explicit links between tasks, requirements, and design components throughout the workflow.

Does spec-mode work for scoping cross-team workstreams without external dependencies?▼

Yes, spec-mode works independently without external dependencies to scope, plan, and track cross-team workstreams. It uses internal scripts and references to enforce governance and generate structured deliverables for independent initiatives.