autonomous-builder
Autonomous Builder is a two-agent software development system that manages complete project lifecycles from requirements analysis through deployment. The Initializer Agent creates project structure, generates test specifications, and establishes version control, while the Builder Agent iteratively implements features, runs browser automation tests, and commits progress across multiple sessions. Use this skill when users request end-to-end project creation, comprehensive feature development, systematic bug fixing, or large-scale code refactoring with built-in testing and deployment workflows.
git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills /tmp/autonomous-builder && cp -r /tmp/autonomous-builder/bundled/skills/autonomous-builder ~/.claude/skills/autonomous-builderSKILL.md
# Autonomous Builder A fully autonomous software development agent that handles the complete software lifecycle: requirements analysis, architecture design, implementation, testing, debugging, and deployment. ## Architecture Pattern: Two-Agent Model **Based on Anthropic's official claude-quickstarts architecture** ``` ┌─────────────────────────────────────────────────────────────────┐ │ TWO-AGENT ARCHITECTURE │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ SESSION 1: INITIALIZER AGENT │ │ ┌─────────────────────────────────────────────────────────┐ │ │ │ • Read requirements / spec │ │ │ │ • Create project structure │ │ │ │ • Generate feature_list.json (200+ tests) │ │ │ │ • Initialize Git repository │ │ │ │ • ✨ Prompt for GitHub URL (optional) │ │ │ │ • ✨ Create README.md & PLANNING.md │ │ │ │ • Commit initial state │ │ │ │ • ✨ Push to GitHub & create issues │ │ │ └─────────────────────────────────────────────────────────┘ │ │ │ │ │ feature_list.json │ │ (Single Source of Truth) │ │ │ │ │ SESSIONS 2+: BUILDER AGENT (fresh context each session) │ │ ┌─────────────────────────────────────────────────────────┐ │ │ │ Step 1: Get Context (pwd, ls, git log, progress) │ │ │ │ Step 2: Start/verify server │ │ │ │ Step 3: Verify previous tests (regression check) │ │ │ │ Step 4: Select next "passes": false feature │ │ │ │ Step 5: Implement feature │ │ │ │ Step 6: Browser automation test │ │ │ │ Step 7: Update feature_list.json │ │ │ │ Step 8: Generate workflow report │ │ │ │ Step 9: Git commit + GitHub push │ │ │ │ Step 10: Update progress notes │ │ │ │ Step 11: Clean exit (auto-continue in 3s) │ │ │ └─────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────┘ ``` **Key Design Principles (Official Pattern):** 1. **Fresh Context Per Session** - Each session uses brand new context window 2. **File-Based State Persistence** - Progress via feature_list.json, not context 3. **Git Commit as State Anchor** - Atomic progress units with easy rollback 4. **Browser Automation Testing** - Act like human user, verify via UI 5. **Auto-Continue with Delay** - 3 second delay between sessions ## Core Philosophy **The Autonomous Development Loop:** ``` PLAN -> BUILD -> TEST -> DEBUG -> DEPLOY -> (REPEAT) | | +------------------------------------+ ``` **Key Principles:** 1. **Self-Sufficient**: No user intervention required during execution 2. **State-Persistent**: Recovers from interruptions via `.builder/` state files 3. **Multi-Language**: Auto-detects and adapts to project technology stack 4. **Incremental**: Completes one feature at a time, commits progress 5. **Error-Resilient**: 3-strike protocol with automatic recovery strategies ## When to Use This Skill Use this skill when the user explicitly wants this agent to own 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 implementation steps - Performing an explicit refactor or modernization effort across the codebase Use stage assistants or other routed specialists for narrow bug fixes, one-off debugging, or scoped edits that do not need full lifecycle ownership. ## Not For / Boundaries - **Security-critical systems** without human review - **Production deployments** without user confirmation - **Legal/compliance-sensitive code** without audit - **Data migration** without backup verification - **Infrastructure changes** without explicit approval - **System-level operations** outside workspace (see SAFETY CRITICAL below) **Required inputs (ask if missing):** 1. Project requirements or specification 2. Target platform/environment (web, CLI, mobile, etc.) 3. Preferred language/framework (or auto-detect) **Safety First:** All operations that could affect system stability, data integrity, or files outside the workspace require explicit user approval. See **SAFETY CRITICAL** section below for details. ## Quick Reference ### Session Continuity (Auto-Resume) **⚠️ Critical for Unattended Long-Running Operation** ``` AUTO-RESUME PROTOCOL: ┌─────────────────────────────────────────────────────────────────┐ │ Session Start │ │ │ │ │ ▼ │ │ Check .builder/state.json exists? │ │ │ │ │ ├─ NO → Initialize new project │ │ │ │ │ └─ YES → Resume from saved state: │ │ 1. Read current_phase │ │ 2. Read current_feature │ │ 3. Read pending_features[]
Vibe Code Orchestrator (VCO) is a governed runtime entry that freezes requirements, plans XL-first execution, and enforces verification and phase cleanup.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
|
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Access real-time and historical stock market data, forex rates, cryptocurrency prices, commodities, economic indicators, and 50+ technical indicators via the Alpha Vantage API. Use when fetching stock prices (OHLCV), company fundamentals (income statement, balance sheet, cash flow), earnings, options data, market news/sentiment, insider transactions, GDP, CPI, treasury yields, gold/silver/oil prices, Bitcoin/crypto prices, forex exchange rates, or calculating technical indicators (SMA, EMA, MACD, RSI, Bollinger Bands). Requires a free API key from alphavantage.co.