auto-develop

Transform task specs into working codebases with build verification.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill auto-develop-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-develop
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/auto-develop
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill auto-develop-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomously converts a task specification into a complete working codebase by reading the spec, writing the code in line with the repo's patterns, and running the build to verify success, all while flagging every assumption.

Core Features & Use Cases

  • Autonomous implementation: reads a spec and produces a working tree and a detailed autonomy report without user prompts.
  • Spec-bound development: adheres strictly to the file list and existing project conventions, stopping at hard gates when encountered.
  • Verification-first workflow: runs build/verification after implementation and surfaces results and decisions for review.
  • Use Case: Imagine a backlog task, hand the spec to /auto-develop and receive a ready-to-review working tree.

Quick Start

Hand the task spec to /auto-develop and review the resulting working tree and the autonomy report.

Frequently Asked Questions about auto-develop

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

FAQPage Schema
How do I automate code generation from a task spec?

Automating code generation from a task spec requires providing a specification file in your tasks/active/ or backlog/ directory. The system reads the spec, writes code adhering to existing project conventions, and runs verification to produce a ready-to-review working tree and autonomy report.

What is autonomous software development from a task specification?

Autonomous software development is the hands-off conversion of a task specification into a working codebase. It handles writing code based on repo patterns, runs build verification, and returns a non-committed working tree with an autonomy report flagging all assumptions.

Does development automation commit changes or deploy code automatically?

Development automation does not commit or deploy code automatically. It returns a non-committed working tree and an autonomy report, ensuring you retain full control over review and integration before any changes enter your repository.

How do I verify a build after autonomous code implementation?

Build verification after autonomous code implementation runs automatically as part of the workflow. The system executes verification immediately after writing code and surfaces the results and decisions in the returned autonomy report for your review.

Can I use spec-bound development with existing project conventions?

You can use spec-bound development with existing project conventions by providing a task spec with a defined file list. The automation adheres strictly to repo patterns, stops at hard gates when encountered, and flags every assumption made during implementation.

What happens when autonomous code generation hits a hard gate?

When autonomous code generation hits a hard gate, the process stops and surfaces the issue in the autonomy report. It does not force changes past the gate, ensuring you can review the blocked state and make manual decisions for the working tree.