OpenSpec Bulk Change Archiver
Fission-AI/OpenSpec
Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.
Implement features using Spec Driven Development (SDD) workflow.
Install Spec
$ npx skills add garden-co/classic-jazz --skill spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install garden-co/classic-jazz spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/garden-co/classic-jazz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/spec .claude/skills/spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spec" agent skill from https://github.com/garden-co/classic-jazz/tree/main/.cursor/skills/spec into .claude/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/garden-co/classic-jazz/tree/main/.cursor/skills/specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add garden-co/classic-jazz --skill spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install garden-co/classic-jazz spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garden-co/classic-jazz.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/spec .agents/skills/spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec" agent skill from https://github.com/garden-co/classic-jazz/tree/main/.cursor/skills/spec into .agents/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add garden-co/classic-jazz --skill spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install garden-co/classic-jazz spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garden-co/classic-jazz.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/spec .cursor/skills/spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spec" agent skill from https://github.com/garden-co/classic-jazz/tree/main/.cursor/skills/spec into .cursor/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/garden-co/classic-jazz.git --path .cursor/skills/spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add garden-co/classic-jazz --skill spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install garden-co/classic-jazz spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garden-co/classic-jazz.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/spec .gemini/skills/spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/garden-co/classic-jazz/tree/main/.cursor/skills/spec into .gemini/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install garden-co/classic-jazz specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add garden-co/classic-jazz --skill spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/garden-co/classic-jazz.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/spec .github/skills/spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/garden-co/classic-jazz/tree/main/.cursor/skills/spec into .github/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add garden-co/classic-jazz --skill spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install garden-co/classic-jazz spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garden-co/classic-jazz.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/spec .opencode/skills/spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spec" agent skill from https://github.com/garden-co/classic-jazz/tree/main/.cursor/skills/spec into .opencode/skills/spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
spec- GitHub stars
- 2.5k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 591 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implement features using Spec Driven Development (SDD) workflow.
- Works in 7 steps: Create Feature Directory → (Optional): Create Requirements Document → Create Design Document → …
- Tasks that involve Spec-driven development
- SKILL.md covers Workflow and Important Rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Spec is an agent skill from garden-co/classic-jazz. Implement features using Spec Driven Development (SDD) workflow. Creates design and task documents with approval gates.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Spec-driven development. The repository describes itself as: A new kind of database that's distributed across your frontend, containers, serverless functions and its own storage cloud. The licence is MIT.
When your agent uses it
- Tasks that involve Spec-driven development
Example prompts
- “/spec”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4f90501. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Spec loads about 1.3k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 591 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from garden-co/classic-jazz at commit 4f90501, republished under its MIT licence (© garden-co). 591 words, ~1,298 tokens.
Download SKILL.mdSave it as
.claude/skills/spec/SKILL.md (or your agent's skills folder).- name
- spec
- description
- Implement features using Spec Driven Development (SDD) workflow. Creates design and task documents with approval gates.
Spec Driven Development Skill
Use this skill when the user asks to implement a feature. This workflow ensures proper planning and approval before any code is written.
Workflow
Follow these steps in order. Do not skip steps. Always ask for explicit approval before moving to the next step.
Step 1: Create Feature Directory
Create a feature directory under .specs/{feature_name} using kebab-case for the name.
Step 2 (Optional): Create Requirements Document
This step is opt-in and must be explicitly requested by the user.
If the user requests requirements, create requirements.md in the feature directory with:
- Introduction - Brief context and purpose of the feature
- User Stories & Acceptance Criteria - Written in EARS (Easy Approach to Requirements Syntax) style
Example EARS patterns:
- Ubiquitous: "The [system] shall [action]"
- Event-driven: "When [event], the [system] shall [action]"
- State-driven: "While [state], the [system] shall [action]"
- Optional: "Where [condition], the [system] shall [action]"
- Unwanted behavior: "If [condition], then the [system] shall [action]"
Example structure:
# Requirements
## Introduction
[Brief context about what this feature addresses and why it's needed]
## User Stories & Acceptance Criteria
### US-1: [User Story Title]
**As a** [role], **I want** [goal], **so that** [benefit].
**Acceptance Criteria:**
- When [user action], the system shall [expected behavior]
- While [state], the system shall [maintain condition]
- Where [optional condition], the system shall [handle appropriately]After creating the requirements document, refine it:
- Scan for missing requirements — Review the document for gaps such as missing edge cases, undefined behavior, unspecified error handling, unclear scope boundaries, missing performance constraints, or unaddressed user roles/permissions.
- Identify ambiguities — Flag any requirements that could be interpreted in multiple ways, have vague language (e.g., "fast", "simple", "flexible"), or lack concrete acceptance criteria.
- Ask clarifying questions — Present the user with a clear list of questions covering the missing and ambiguous areas. Group them logically and explain why each question matters.
Do not proceed until all critical ambiguities are resolved. Minor open questions can be noted as assumptions in the design document.
If requirements are created, get approval before proceeding to the design document.
Show full SKILL.md (313 more words)Show less
Step 3: Create Design Document
Create design.md in the feature directory with:
- Overview - High-level description of the solution
- Architecture / Components - System structure and component interactions
- Data Models - Schemas, types, and data structure
- Testing Strategy - Approach to testing the feature
Show the code snippets of the core parts of the implementation in the design.
We prioritize integration testing, and show a couple of test snippets as example of testing strategy.
After creating the design document, refine it:
- Scan for missing requirements — Check whether the design covers all stated requirements and user stories. Identify any requirements that were dropped, under-specified, or only partially addressed.
- Identify ambiguities — Flag design decisions that are vague or leave open questions about behavior, data flow, or component responsibilities.
- Ask clarifying questions — Present the user with questions about any gaps or ambiguities discovered. Explain how each gap could affect implementation.
Do not proceed until all critical gaps are resolved. Minor open questions can be noted as assumptions.
Step 4: Design Approval Gate
Ask the user: "Does the design look good? If so, we can move on to the implementation plan."
Wait for explicit approval before proceeding.
Step 5: Create Tasks Document
Once design is approved, create tasks.md in the feature directory with:
- Numbered checklist of coding tasks
- Each task should reference specific design components
- Include only coding tasks - no deployment, documentation, or other non-coding tasks
Example structure:
# Implementation Tasks
## Tasks
- [ ] 1. Create data model for [entity]
- [ ] 2. Add API endpoint for [action]
- [ ] 3. Implement validation logic
- [ ] 4. Add unit tests for [component]
- [ ] 5. Add integration tests for [feature]Step 6: Tasks Approval Gate
Ask the user: "Do the tasks look good?"
Wait for explicit approval.
Step 7: Stop
Do not implement any code. The workflow ends here. Implementation should be a separate activity initiated by the user.
Important Rules
- Never skip steps - Each step builds on the previous one
- Always get approval - Do not proceed without explicit user confirmation
- No implementation - This workflow is for planning only
- Kebab-case naming - Feature directories use kebab-case (e.g.,
user-authentication)
© garden-co, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .cursor/skills/spec of garden-co/classic-jazz.
Open the folder on GitHubat commit 4f90501
Compare with similar skills
Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spec this skillgarden-co/classic-jazz | 2.5k | — | ~1.3k | Automated safety check: Pass | MIT | |
| OpenSpec Bulk Change ArchiverFission-AI/OpenSpec | 71k | 2 repos | ~5.6k | Automated safety check: Pass | MIT | |
| Speckit ConstitutionWeihanLi/WeihanLi.Common | 242 | 11 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Speckit Plankunstmusik/blue | 154 | 18 repos | ~2.1k | Automated safety check: Pass | GPL-3.0 | |
| Speckit Specifykunstmusik/blue | 154 | 18 repos | ~4.7k | Automated safety check: Pass | GPL-3.0 | |
| Review Spdzhu1090093659/spec_driven_develop | 985 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Speckit Constitution
WeihanLi/WeihanLi.Common
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Speckit Plan
kunstmusik/blue
Execute the implementation planning workflow using the plan template to generate design artifacts.
Speckit Specify
kunstmusik/blue
Create or update the feature specification from a natural language feature description.
Review Spd
zhu1090093659/spec_driven_develop
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.
Speckit Tasks
kunstmusik/blue
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
More from garden-co/classic-jazz
All 8 skills in this repoJazz Performance
garden-co/classic-jazz
A skill your agent uses when optimizing Jazz applications for speed, responsiveness, and scalability.
Jazz Testing
garden-co/classic-jazz
A skill your agent uses when you need to write, review, or debug automated tests for applications built on the Jazz framework.
Jazz UI Development
garden-co/classic-jazz
A skill your agent uses when building, debugging, or optimizing Jazz applications.
Benchmarking
garden-co/classic-jazz
A skill your agent uses when writing or running performance benchmarks for Jazz packages.
Jazz Permissions Security
garden-co/classic-jazz
A skill your agent uses when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications.
Jazz Schema Design
garden-co/classic-jazz
Design and implement collaborative data schemas using the Jazz framework.
Related
Categories
Questions about Spec
What does Spec do?
Implement features using Spec Driven Development (SDD) workflow. Spec is an agent skill from garden-co/classic-jazz. Implement features using Spec Driven Development (SDD) workflow.
When should I use Spec?
Spec fits situations like: tasks that involve Spec-driven development.
How do I install Spec in Claude Code?
Run `npx skills add garden-co/classic-jazz --skill spec -a claude-code`. Or copy the skill folder (.cursor/skills/spec in garden-co/classic-jazz) into .claude/skills/spec in your project. Claude Code loads it when a task matches its description.
How do I install Spec in Codex?
Run `npx skills add garden-co/classic-jazz --skill spec -a codex`. Or copy the skill folder (.cursor/skills/spec in garden-co/classic-jazz) into .agents/skills/spec in your project. Codex loads it when a task matches its description.
Can I use Spec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add garden-co/classic-jazz --skill spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec, .gemini/skills/spec, .github/skills/spec and .opencode/skills/spec in your project.
What does Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Spec is instructions for the agent only.
Does Spec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Spec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Spec use?
Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Spec use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Spec?
Skills that share tags, products or a category with Spec: OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 71k stars), Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars), Speckit Plan (kunstmusik/blue, 154 stars) and Speckit Specify (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spec?
garden-co (a GitHub organization) maintains it in garden-co/classic-jazz, which has 2,534 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 7, 2026.
Source: garden-co/classic-jazz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.