autospec

Convert feature requests into design specs, GitHub issue trees, and autonomous implementation loops.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-berlinguyinca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autospec
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-berlinguyinca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, git, gh, and includes scripts (resource) components.

What problem does it solve?

Autospec turns a feature request into tracked, reviewable, and explainable software changes, preserving the full “story behind the code” (specs, issues, PRs, commits, and implementation state).

Core Features & Use Cases

  • End-to-end feature pipeline: bootstraps a GitHub repo (if missing), investigates, brainstorms a design spec, decomposes into an issue tree, and runs an autonomous implementation loop with admin auto-merge.
  • Existing spec mode: split and materialize an already-written design spec into linked GitHub issues, skipping investigation and design.
  • Operational guardrails & traceability: enforces a phased workflow, quality gates, dependency metadata, and produces artifacts that let you synthesize a cited repo overview afterward.

Quick Start

Run autospec to ship a feature end-to-end by invoking /autospec with a detailed feature request (for example, add a real-time presence indicator to your dashboard) and let the workflow create the spec, issues, implementation PRs, and merges.

Frequently Asked Questions about autospec

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

FAQPage Schema
How do I convert a feature request into an auditable multi-commit implementation automatically?

Autospec converts a feature request into an auditable implementation by generating a design spec, decomposing it into a dependency-linked GitHub issue tree, and running an autonomous implementation loop with auto-merge.

Can I split an existing design spec into linked GitHub issues without regenerating the design?

Yes, autospec supports an existing spec mode that materializes an already-written design spec into linked GitHub issues, skipping the investigation and design phases entirely.

What tools do I need installed to run autonomous feature planning and implementation workflows?

You need curl, jq, git, and gh installed to run autospec, as it relies on these tools for repository bootstrapping, GitHub issue management, and autonomous implementation loops.

Does autonomous coding with auto-merge work across different CLI harnesses?

Yes, autospec applies autonomous coding with auto-merge across Claude Code, OpenCode, and Codex CLI harnesses, running phase-based delegation and guardrails for each environment.

How do I bootstrap a GitHub repo for autonomous feature implementation when no remote exists?

Autospec handles repo bootstrap automatically when no GitHub remote exists, creating the necessary remote setup before proceeding with spec generation, issue tree decomposition, and the implementation loop.

What artifacts does autonomous feature shipping produce for traceability after the implementation loop finishes?

Autonomous feature shipping produces a full story behind the code including specs, issues, PRs, commits, dependency metadata, periodic status updates, and a final implementation report for cited repo overview synthesis.