autonomous-builder

What it does

A fully autonomous software development agent that manages the complete software lifecycle: requirements analysis, architecture design, implementation, testing, debugging, and deployment. It is intended for end-to-end project creation, feature development, bug fixing, or code refactoring.

How it works

• Follows a Two-Agent Model: an Initializer Agent reads requirements, creates project structure, generates feature_list.json (200+ tests), initializes a Git repository, prompts for a GitHub URL (optional), creates README.md & PLANNING.md, commits the initial state, and may push to GitHub and create issues. Then Builder Agents (fresh context per session) perform steps: get context (pwd, ls, git log, progress), start/verify server, verify previous tests, select next false feature, implement feature, run a browser automation test, update feature_list.json, generate a workflow report, commit + push, update progress notes, and clean exit after a 3-second delay.
• Maintains state via feature_list.json and .builder state files; uses Git commits as state anchors; supports auto-continue with a 3-second delay between sessions.
• Employs browser automation testing to verify UI behavior and requires explicit user approval for operations affecting system stability or outside the workspace.
• Supports auto-resume and recovery from interruptions; uses a predefined auto-continue protocol to decide next steps without user input when features remain.

When to use it

Use this skill when the user explicitly wants ownership of an end-to-end build or major refactor, such as starting a new project from a full specification, continuing a previously initialized .builder/ project, driving a broad feature build across multiple steps, or performing an explicit refactor across the codebase. For narrow bug fixes or scoped edits that do not require full lifecycle ownership, use stage assistants or other routed specialists.

What it can touch

The skill declares tools in frontmatter including Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Skill, Task, ToolSearch, mcp__ide__executeCode, mcp__ide__getDiagnostics. It is designed to operate within a workspace with a .builder/ directory for state persistence and uses Git for versioning. It interacts with project files such as README.md, PLANNING.md, feature_list.json, and the repository state.

Caveats

• Safety: Operations that could affect system stability, data integrity, or files outside the workspace require explicit user approval. See SAFETY sections in the skill description.
• Not intended for security-critical systems or production deployments without review.
• Auto-continue behavior relies on the auto-resume protocol; user input is not required between features unless explicitly needed by the router authority.