Skip to content
/
Tier A A4 Markdown scaffold Variant

spec-kit-command-cursor (foxgod183)

spec-kit-command-cursor-foxgod · foxgod183/spec-kit-command-cursor · ★ 3 · last commit 2026-05-26

Simplified Cursor IDE spec-driven toolkit with 8 commands and compact template variants for non-technical users.

Best whenSpec documents should have compact variants for context-constrained AI sessions.
vs seeds
spec-kitcommand-cursor (same 8 command names, same feat-{N}-{name} directory pattern) at approximately v3.0 feature parity rathe…
Primitive shape 8 total
Commands 8
00

Summary

spec-kit-command-cursor (foxgod183) — Summary

spec-kit-command-cursor (foxgod183) is a minimal Cursor IDE spec-driven development toolkit based on the same madebyaris design (8 slash commands: brief, evolve, implement, plan, research, specify, tasks, upgrade) but strips away all advanced features: no subagents, no skills, no hooks, no MCP, no dashboard. The repo ships a devotedness/ folder of JavaScript utilities (utils.js, SDDHelper class) that provide feature-number auto-increment and spec directory scaffolding, but these are labeled "reference implementation for cursor commands" rather than runnable tooling. A command_kit_spec_cursor_v3.0.zip is available for direct download. The README targets non-technical users with simplified installation instructions. 3 stars, last commit May 26 2026, no license file.

Differs from seeds: Near-copy of madebyaris/spec-kit-command-cursor (same command names) but at v3.0 feature parity rather than v5.1. Compared to the madebyaris variant it drops async subagents, parallel orchestration, hooks, skills — reducing it to the Archetype 4 "markdown scaffold" pattern. Very different from the kiro and spec-kit seeds despite using the same spec phase names. Effectively a simplified redistribution of the madebyaris work.

01

Overview

spec-kit-command-cursor (foxgod183) — Overview

Origin

Created by foxgod183 (active as of May 2026). Appears to derive from madebyaris/spec-kit-command-cursor (same command names: brief, specify, plan, tasks, implement, research, evolve, upgrade). No license file. README targets non-technical users with simplified "download and install" instructions and a zip archive. JavaScript utilities in devotedness/utils.js suggest it was intended as a more guided workflow but the actual agent-side commands remain the primary artifact.

Philosophy (From README)

"Simplify Spec-Driven Development with a toolkit for Cursor IDE, turning ideas into structured, ready-to-implement features."

No detailed philosophy documentation. README focuses on installation steps.

Key Design Choices

  1. Minimal surface: 8 slash commands only — no subagents, no skills, no hooks. The simplest possible Cursor SDD toolkit.
  2. JavaScript SDDHelper utility: devotedness/utils.js provides a SDDHelper class for feature number auto-increment (feat-{N}-{name} pattern), config loading, and directory creation. This is labeled as "reference implementation" and not invoked by the commands directly.
  3. Compact templates: .sdd/templates/ includes compact variants (spec-compact.md, plan-compact.md, tasks-compact.md, todo-compact.md) alongside full templates — unusual; suggests adapting output size based on model context budget.
  4. Config-driven: .sdd/config.json stores settings including autoNumberFeatures, defaultFeaturePrefix.
  5. MDC rule file: .cursor/rules/sdd-system.mdc provides Cursor IDE Composer rules for the SDD workflow.

Antipatterns

Not documented.

02

Architecture

spec-kit-command-cursor (foxgod183) — Architecture

Distribution

  • Git clone + copy, or download command_kit_spec_cursor_v3.0.zip
  • No npm/pip package
  • No license file
  • Language: Markdown (commands), JavaScript (reference utilities)

Install

# Option 1: clone
git clone https://github.com/foxgod183/spec-kit-command-cursor.git
cp -r .cursor/ <project>/.cursor/

# Option 2: download zip
# From README: download command_kit_spec_cursor_v3.0.zip

Directory Tree

.cursor/
  commands/
    brief.md
    evolve.md
    implement.md
    plan.md
    research.md
    specify.md
    tasks.md
    upgrade.md
  rules/
    sdd-system.mdc    # Cursor IDE Composer rules

.sdd/
  config.json
  guidelines.md
  templates/
    decision-matrix.md
    example-json-format.json
    feature-brief-v2.md
    plan-compact.md
    plan-template.md
    research-compact.md
    research-template.md
    spec-compact.md
    spec-template.md
    tasks-compact.md
    tasks-template.md
    todo-compact.md
    todo-list-template.md

devotedness/          # JavaScript reference utilities
  utils.js            # SDDHelper class: feature numbering, dir creation
  IMPLEMENTATION_GUIDE.md
  ISSUE_1_RESOLUTION.md

specs/
  active/
  index.md
  00-overview.md

Required Runtime

  • Cursor IDE

Target AI Tools

Cursor IDE only.

03

Components

spec-kit-command-cursor (foxgod183) — Components

Slash Commands (8)

Command Purpose
/brief Quick feature brief creation
/specify Transform description into structured specification
/plan Technical architecture plan
/tasks Break plan into actionable tasks
/implement Execute task implementation
/research Technical research and pattern investigation
/evolve Update specs when changes are discovered
/upgrade Upgrade brief to full spec planning

MDC Rule File

File Purpose
.cursor/rules/sdd-system.mdc Cursor IDE Composer rules enforcing SDD workflow

JavaScript Utilities (Reference, not invoked by commands)

File Contents
devotedness/utils.js SDDHelper class: feature number auto-increment, config loading, specs/active/feat-{N}-{name}/ directory creation

Templates (11 in .sdd/templates/)

Template Purpose
spec-template.md Full specification document
spec-compact.md Compact specification for smaller context
plan-template.md Full technical plan
plan-compact.md Compact plan
tasks-template.md Full task list
tasks-compact.md Compact task list
todo-list-template.md Todo list format
todo-compact.md Compact todo list
research-template.md Research document
research-compact.md Compact research
feature-brief-v2.md Feature brief v2 format
decision-matrix.md Decision matrix template

Config

.sdd/config.jsonautoNumberFeatures, defaultFeaturePrefix settings.

05

Prompts

spec-kit-command-cursor (foxgod183) — Prompts

Excerpt 1: /specify Command

Source: .cursor/commands/specify.md

Prompting technique: Simple numbered procedure with "what/why not how" constraint; clarification-first gate; template-based generation.

# /specify Command

## Purpose
Transform feature ideas into detailed, testable requirements focusing on the "what" and "why" before implementation.

## Process
1. Create feature directory in `specs/active/feat-XXX-[name]/`
2. Generate `spec.md` using template with:
   - Problem statement and user needs
   - Functional and non-functional requirements  
   - User stories with acceptance criteria
   - Success metrics and edge cases
3. Prompt for clarification on vague requirements
4. Ensure specifications are testable and measurable
5. Update project index

## Implementation Rules
- Always ask clarifying questions if description is vague
- Focus on "what" and "why", not "how"
- Create measurable acceptance criteria
- Consider edge cases and error scenarios
- Include user personas and use cases
- Define success metrics and KPIs

Excerpt 2: SDDHelper — JavaScript Reference Utility

Source: devotedness/utils.js

Prompting technique: Config-driven feature numbering; filesystem-based state detection; feat-{N}-{name} directory convention.

// Get next feature number
getNextFeatureNumber() {
    const config = this.loadConfig();
    if (!config.settings.autoNumberFeatures) return '';

    const activeDir = path.join(this.specsPath, 'active');
    if (!fs.existsSync(activeDir)) return '001';

    const features = fs.readdirSync(activeDir)
        .filter(dir => dir.startsWith('feat-'))
        .map(dir => {
            const match = dir.match(/feat-(\d+)-/);
            return match ? parseInt(match[1]) : 0;
        })
        .filter(num => num > 0);

    const maxNum = features.length > 0 ? Math.max(...features) : 0;
    return String(maxNum + 1).padStart(3, '0');
}
09

Uniqueness

spec-kit-command-cursor (foxgod183) — Uniqueness and Positioning

Differs from Seeds

Extremely close to madebyaris/spec-kit-command-cursor (same command names, same .cursor/ structure, same specs/active/feat-{N}-{name}/ directory pattern) but strips all v5.1 features: no async subagents, no skills, no parallel execution, no hooks, no file-conflict detection. Compared to spec-kit (GitHub), both are Cursor command packs but this one has no Python CLI installer and no hooks. Compared to kiro, uses same phase names (specify → plan → tasks → implement) but no EARS notation or steering layer. This is effectively an older/simpler fork of the madebyaris work — the devotedness/utils.js SDDHelper class shares the same feat-{N}-{name} numbering logic.

Distinctive Positioning

  • Compact templates: The only framework in the batch that ships both full and compact template variants, acknowledging context-budget constraints explicitly.
  • Simplified target audience: README explicitly addresses non-technical users — positioning unique in this corpus.
  • No formal license: No LICENSE file, which makes commercial and derivative use legally ambiguous.

Observable Failure Modes

  1. JavaScript utilities not connected to commands: devotedness/utils.js is labeled "reference implementation" but Cursor commands don't invoke it — the feature-numbering logic is either duplicated in the command markdown or absent.
  2. No license: Unclear redistribution terms.
  3. 3 stars, no forks: Minimal adoption; likely used only by the author.
  4. Possible fork of madebyaris without attribution: Same command names, same directory structure, same feature-numbering pattern — relationship not acknowledged in README.
04

Workflow

spec-kit-command-cursor (foxgod183) — Workflow

Phases and Artifacts

Phase Command Artifact
1. Brief /brief specs/active/feat-{N}-{name}/feature-brief.md
1a. Research /research specs/active/feat-{N}-{name}/research.md
2. Specify /specify specs/active/feat-{N}-{name}/spec.md
3. Plan /plan specs/active/feat-{N}-{name}/plan.md
4. Tasks /tasks specs/active/feat-{N}-{name}/tasks.md
5. Implement /implement Code changes
6. Evolve /evolve Updated spec documents

Feature Numbering

Per devotedness/utils.js, feature directories follow feat-{N}-{name} pattern with {N} auto-incremented from the highest existing number in specs/active/. Config setting autoNumberFeatures controls this.

Approval Gates

Not formally defined in command files. Assumed to require user approval between phases (standard for spec workflows).

Compact Templates

Compact variants (spec-compact.md, plan-compact.md, tasks-compact.md) are available for environments with limited context windows. Commands presumably load the appropriate template based on configuration or context size.

06

Memory Context

spec-kit-command-cursor (foxgod183) — Memory and Context

State Storage

File-based under specs/active/feat-{N}-{name}/:

File Content
specs/active/feat-{N}-{name}/spec.md Feature specification
specs/active/feat-{N}-{name}/plan.md Technical plan
specs/active/feat-{N}-{name}/tasks.md Task list
specs/active/feat-{N}-{name}/research.md Research output
specs/index.md Project-level spec index
.sdd/config.json Configuration including feature numbering state

Persistence Level

project — all under specs/.

Cross-Session Handoff

Yes — file presence determines phase completion.

Compact Templates

Unique feature: compact template variants (spec-compact.md, plan-compact.md) for context-constrained sessions.

07

Orchestration

spec-kit-command-cursor (foxgod183) — Orchestration

Multi-Agent

No.

Orchestration Pattern

sequential — one command at a time.

Multi-Model

No.

Isolation Mechanism

None.

Execution Mode

one-shot — each command runs once.

Prompt Chaining

Yes — each command reads prior phase artifacts.

Cross-Tool Portability

Single-tool (Cursor IDE).

08

Ui Cli Surface

spec-kit-command-cursor (foxgod183) — UI, CLI, and Surface

CLI Binary

None.

IDE Integration

Cursor IDE slash commands in .cursor/commands/. MDC rule file .cursor/rules/sdd-system.mdc.

Dashboard / Web UI

None.

Observability

No audit log. Feature directory naming (feat-{N}-{name}) serves as implicit state tracking.

Related frameworks

same archetype · same primary tool · same memory type

BMAD-METHOD ★ 48k

Provides a full agile delivery lifecycle with named expert-persona AI collaborators that elicit the human's best thinking rather…

Agent OS ★ 4.6k

Extracts implicit codebase conventions into token-efficient markdown standards files and injects them selectively into AI agent…

Claude Conductor ★ 367

Gives Claude Code a persistent, cross-linked, auto-analyzed documentation system so it retains codebase context across sessions.

Spec-Driver (Greenfield Spec-Driven Development) ★ 25

Prevents spec rot in AI-assisted development by making implementation changes flow back into evergreen, authoritative specs via…

Anthropic Knowledge Work Plugins ★ 16k

Role-specialized plugin bundles with live MCP connectors that turn Claude into a domain expert for enterprise knowledge workers.

Codex Integration for Claude Code (skill-codex) ★ 1.3k

Single Claude Code skill that handles Codex CLI invocation correctly (stdin blocking, thinking token suppression, session resume)…