autonomous-dev

Implements code changes autonomously through test-first development and iterative self-review.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/tktcorporation/cli-sim-game-escape --skill autonomous-dev-tktcorporation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autonomous-dev
Source: https://github.com/tktcorporation/cli-sim-game-escape/tree/main/.claude/skills/autonomous-dev
Command: npx skills add https://github.com/tktcorporation/cli-sim-game-escape --skill autonomous-dev-tktcorporation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Once an implementation direction is agreed upon, constant back-and-forth confirmation interrupts work and wastes the user's time. This Skill takes a confirmed plan and drives it to completion autonomously, maintaining quality through test-first development, repeated self-review rounds, and actual runtime verification instead of relying on user checkpoints. ## Core Features & Use Cases - Autonomous Implementation Workflow: A seven-phase process covering policy confirmation, codebase exploration, test-first development, implementation, iterative self-review, PR integration, and concise reporting. - Test-First Discipline: Writes regression and edge-case tests before implementation code, verifying they fail for the right reason before building the feature. - Iterative Self-Review: Runs a minimum of two review rounds across seven quality dimensions (correctness, conventions, test coverage, intent, simplicity, type safety, ripple effects) until no further issues are found. - Use Case: After agreeing with your AI assistant on how to fix a bug or add a feature, say "go ahead" and let it explore the affected code, write failing tests, implement the fix, self-review until clean, run lint and tests, verify the change actually works, and report back with a summary. ## Quick Start Tell the assistant to implement the agreed feature or fix autonomously and report back only when tests pass and the change is verified working.

Frequently Asked Questions about autonomous-dev

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

FAQPage Schema
How do I get an AI assistant to implement a feature without constant check-ins?▼

Agree on the implementation direction first, then let the autonomous workflow run. It only pauses for destructive operations, invalidated plans, or major scope growth, and reports back when tests pass and the change is verified working.

How does test-first development work in an autonomous coding workflow?▼

Tests are written before implementation code and must fail for the expected reason first. For bug fixes, a single regression test reproducing the bug is the minimum; refactoring instead verifies new tests pass against current behavior.

Does this workflow work with Python, TypeScript, or other languages?▼

Yes, it is language-agnostic. At the start it detects the project's quality gate commands from CLAUDE.md, CI configuration, package.json, pyproject.toml, or Makefiles, then uses those commands for all lint and test steps.

When should I not use an autonomous implementation workflow?▼

Avoid it for tasks that end with investigation, answers, or review only, and for work where the direction is still undecided. It is designed for execution after a plan is agreed, not for open-ended consultation.

What happens when the AI gets stuck or the plan stops making sense?▼

It stops and asks the user only in three cases: destructive or irreversible operations are needed, the agreed plan turns out to be invalid, or the scope grows far beyond the original agreement. All other uncertainty is resolved independently.

How is quality maintained without human review during implementation?▼

Quality comes from iterative self-review: a minimum of two rounds re-reading entire changed files against seven criteria including correctness, conventions, test coverage, and type safety, plus lint, full test runs, and actual runtime verification before completion.