[Resource]: Autospec - CLI for Spec Driven Development

[ariel-frischer]

Display Name

Autospec

Category

Tooling

Sub-Category

Tooling: Orchestrators

Primary Link

https://github.com/ariel-frischer/autospec

Secondary Link

https://ariel-frischer.github.io/autospec/

Author Name

Ariel Frischer

Author Link

https://github.com/ariel-frischer

License

MIT

Other License

No response

Description

Spec-driven development CLI — generates YAML specs, plans, and tasks for structured Claude Code implementation.

Validate Claims

Quick test:

curl -fsSL https://raw.githubusercontent.com/ariel-frischer/autospec/main/install.sh | sh
mkdir fastapi-test && cd fastapi-test && git init
echo "# FastAPI Test App" > README.md
autospec init
autospec prep "Add a /health endpoint that returns JSON with status and timestamp"

What to expect:

Install script downloads a single Go binary (~15MB) to ~/.local/bin/autospec

autospec init creates:

• .claude/commands/autospec*.md — slash commands for Claude Code
• .autospec/ — config and state
• Prompts to run constitution (press Y) → generates .autospec/memory/constitution.yaml (project coding standards, once per project)

autospec prep (git checks out a branch) creates specs/001-health-endpoint/ with:

• spec.yaml — requirements, acceptance criteria, edge cases
• plan.yaml — implementation approach
• tasks.yaml — phased task breakdown

Then autospec implement executes the tasks via Claude Code → generates working code given the original prompt.

Reversal: autospec clean removes project files, rm ~/.local/bin/autospec removes binary.

Best for: Features with 3+ design decisions, 3-10 files — not trivial fixes, not multi-week projects.

Additional Comments

Wrapper CLI built specifically for heavy Claude Code usage.

Recommendation Checklist

• I have checked that this resource hasn't already been submitted
• My resource provides genuine value to Claude Code users, and any risks are clearly stated
• All provided links are working and publicly accessible
• I am submitting only ONE resource in this issue
• I understand that low-quality or duplicate submissions may be rejected

[ariel-frischer]

This ever gonna get pushed? Whats the process?

[hesreallyhim]

hi @ariel-frischer , thanks for sharing this. The process has evolved somewhat so be sure to review the updated CONTRIBUTING documentation.

i really like the look of this, nice work. for me personally, i read through 4-5 pages of docs and i couldn't find an example of an actual spec.yml. that would be really helpful for the reader, in my opinion. also, it's up to you, but if you want encourage me to review this more efficiently, instead of:

run autospec specify "my feature description"

tell me exactly what to have it spec out (like what specific prompt, even) and what i should expect it to do.

• what gets installed when i run the install script? what permissions does it have? is it easily reversible?

finally:

CLI for streamlined spec-driven development using Claude Code. Stop AI slop coding. Autospec brings structure to AI coding: spec → plan → tasks → implement - all in one command.

Strike that long as it doesn't fit the tone of the list.

Thanks, with a little help I can hopefully understand what I'm buying into, and this is a kind of workflow that I like to use myself. Ceers. /request-changes see comments

[github-actions]

🔄 Changes Requested by @hesreallyhim

see comments

Please edit your issue to address these points. The validation will run again automatically after you make changes.

[github-actions]

📝 Issue Updated

@hesreallyhim - The submitter has edited their issue in response to your requested changes.

✅ The updated submission now passes all validation checks!

You may want to review the changes and consider approving the submission.

[ariel-frischer]

@hesreallyhim Thanks for the valuable feedback - I've updated the issue with clearer test steps, reversal instructions, and a shorter description. I'll look to improve my README.md as well - given your feedback. If you need any help running it - or have any questions let me know!

Here are the YAML templates each stage generates (but expect real ones to be more comprehensive):

spec.yaml

feature:
  branch: "001-health-endpoint"
  status: "Specified"
user_stories:
  - id: "US-001"
    as_a: "developer"
    i_want: "a /health endpoint"
    so_that: "I can monitor service availability"
requirements:
  functional:
    - id: "FR-001"
      description: "GET /health returns {status, timestamp}"
  non_functional:
    - id: "NFR-001"
      category: "performance"
      description: "Response time < 50ms"

plan.yaml

overview:
  approach: "Add new route handler with JSON response"
  key_decisions:
    - decision: "Use standard library for timestamp"
      rationale: "No external dependencies needed"
components:
  - name: "HealthHandler"
    description: "Route handler returning status JSON"
    files_affected:
      - path: "main.py"
        changes: "Add /health route"

tasks.yaml

phases:
  - id: "phase-1"
    name: "Implementation"
    tasks:
      - id: "task-1"
        title: "Create health endpoint"
        status: "pending"
        acceptance_criteria:
          - "GET /health returns 200"
          - "Response includes status and timestamp"

[github-actions]

🤖 Validation Results

✅ All validation checks passed!

Your submission is ready for review by a maintainer.

Validated Data:

{
  "display_name": "Autospec",
  "category": "Tooling",
  "subcategory": "Orchestrators",
  "primary_link": "https://github.com/ariel-frischer/autospec",
  "secondary_link": "https://ariel-frischer.github.io/autospec/",
  "author_name": "Ariel Frischer",
  "author_link": "https://github.com/ariel-frischer",
  "license": "MIT",
  "description": "Spec-driven development CLI — generates YAML specs, plans, and tasks for structured Claude Code implementation.",
  "last_modified": "2026-01-06:04-51-08",
  "active": "TRUE",
  "last_checked": "2026-01-13:06-05-59"
}

---

_{This comment is automatically updated when you edit the issue.}

[ariel-frischer]

@hesreallyhim I think I've clarified as much as possible. Lmk what you think.

[ariel-frischer]

Bump