spec

Plan feature work with design artifacts and explicit approval gates.

154|13|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/garden-co/jazz --skill spec-garden-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/garden-co/jazz/tree/main/.cursor/skills/spec
Command: npx skills add https://github.com/garden-co/jazz --skill spec-garden-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan feature work with formal design and approval gates.

Core Features & Use Cases

  • Structured planning workflow to generate design and task artifacts before implementation
  • Explicit approval gates to prevent scope creep and ensure stakeholder alignment
  • Works for feature requests, refactors, and cross-team collaborations to streamline delivery

Quick Start

Initiate a spec-driven planning session for a feature and generate design and task documents with approval gates.

Frequently Asked Questions about spec

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

FAQPage Schema
What is spec-driven development for planning feature work?

Spec-driven development is a structured planning workflow that generates formal design and task artifacts before implementation. It enforces explicit approval gates to ensure stakeholder alignment and prevent scope creep during feature delivery.

How do I add approval gates to an engineering workflow for refactors?

To add approval gates to an engineering workflow, initiate a spec-driven planning session that collects design artifacts and enforces progression steps. This ensures explicit approvals are secured before coding refactors or features begin.

Can I use design docs to manage cross-team collaborations?

Yes, you can use design docs to manage cross-team collaborations by applying a structured planning workflow. It guides discussions and decisions before coding, streamlining delivery through formal artifact collection and stakeholder approvals.

What's the best way to prevent scope creep in feature management?

The best way to prevent scope creep in feature management is implementing formal approval gates during the planning phase. This ensures explicit stakeholder alignment on design artifacts before any implementation work progresses.

Do I need formal stakeholder alignment before coding a feature request?

Yes, you need formal stakeholder alignment before coding a feature request to ensure scope and quality. A spec-driven workflow gates progression with explicit approvals, guiding discussions and decisions before implementation starts.