autonomous-master
Master orchestrator for autonomous coding projects. Use when starting autonomous projects, continuing sessions, checking status, or running complete autonomous workflows.
60
Quality
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/autonomous-master/SKILL.mdThe canonical home for this skill is autonomous-master in fernandezbaptiste/Skrillz
Autonomous Master
The single entry point for fully autonomous coding.
Orchestrates all 16 autonomous coding skills to implement complete projects from specification to working code.
Quick Start
Start New Project
autonomous start: Build a task management app with user authentication,
project management, and team collaboration features. Use Next.js,
TypeScript, Prisma, and PostgreSQL.Continue Existing Project
autonomous continueCheck Status
autonomous statusHow It Works
┌─────────────────────────────────────────────────────────────────┐
│ AUTONOMOUS MASTER │
│ │
│ "autonomous start: [spec]" │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ PHASE 1: INITIALIZATION │ │
│ │ ├─ Parse specification │ │
│ │ ├─ Generate 100+ features → feature_list.json │ │
│ │ ├─ Create environment → init.sh │ │
│ │ ├─ Scaffold project structure │ │
│ │ ├─ Initialize git repository │ │
│ │ └─ Create master-state.json │ │
│ │ │ │
│ │ Skills Used: initializer-agent, context-state-tracker │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ PHASE 2: IMPLEMENTATION LOOP │ │
│ │ while (incomplete_features > 0): │ │
│ │ │ │ │
│ │ ├─ CHECK CONTEXT │ │
│ │ │ └─ If > 85% used → HANDOFF │ │
│ │ │ │ │
│ │ ├─ SELECT FEATURE │ │
│ │ │ └─ Priority + dependency order │ │
│ │ │ │ │
│ │ ├─ CREATE CHECKPOINT │ │
│ │ │ └─ Safe rollback point │ │
│ │ │ │ │
│ │ ├─ IMPLEMENT (TDD) │ │
│ │ │ ├─ RED: Write failing test │ │
│ │ │ ├─ GREEN: Implement to pass │ │
│ │ │ └─ REFACTOR: Clean up │ │
│ │ │ │ │
│ │ ├─ VERIFY │ │
│ │ │ └─ Run E2E tests │ │
│ │ │ │ │
│ │ ├─ If PASS: │ │
│ │ │ ├─ Mark feature complete │ │
│ │ │ ├─ Commit changes │ │
│ │ │ └─ Update progress │ │
│ │ │ │ │
│ │ └─ If FAIL: │ │
│ │ ├─ Attempt recovery │ │
│ │ ├─ If unrecoverable: rollback, skip │ │
│ │ └─ Store error→solution for learning │ │
│ │ │ │
│ │ Skills Used: coding-agent, tdd-workflow, │ │
│ │ browser-e2e-tester, error-recoverer, │ │
│ │ checkpoint-manager, progress-tracker │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ PHASE 3: HANDOFF (when context limit reached) │ │
│ │ ├─ Compact context summary │ │
│ │ ├─ Serialize full state │ │
│ │ ├─ Save handoff package │ │
│ │ ├─ Generate continuation prompt │ │
│ │ └─ Exit cleanly │ │
│ │ │ │
│ │ Skills Used: context-compactor, handoff-coordinator, │ │
│ │ memory-manager │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ PHASE 4: COMPLETION (when all features pass) │ │
│ │ ├─ Run full E2E test suite │ │
│ │ ├─ Generate completion report │ │
│ │ ├─ Final commit │ │
│ │ └─ Clean up temporary files │ │
│ │ │ │
│ │ Skills Used: browser-e2e-tester, progress-tracker │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘Commands
autonomous start: [specification]
Initializes a new autonomous coding project.
Input: Natural language project specification Output:
feature_list.jsonwith 100+ featuresinit.shenvironment setup scriptclaude-progress.txtprogress file.claude/master-state.jsonorchestrator state
Example:
autonomous start: Create an e-commerce platform with:
- User authentication (email, OAuth)
- Product catalog with search and filters
- Shopping cart and checkout
- Order management
- Admin dashboard
Use React, Node.js, PostgreSQL, Stripe for payments.autonomous continue
Resumes from the last handoff point.
Detects:
- Loads
.claude/master-state.json - Reads
.claude/handoffs/current.json - Resumes at current feature
Example:
autonomous continueautonomous status
Shows current project status.
Output:
╔══════════════════════════════════════════════════════════════╗
║ AUTONOMOUS PROJECT STATUS ║
╠══════════════════════════════════════════════════════════════╣
║ Project: e-commerce-platform ║
║ Status: IMPLEMENTING ║
║ ║
║ Progress: ████████████░░░░░░░░ 45/100 (45%) ║
║ ║
║ Sessions: 5 ║
║ Current Feature: cart-012 (Add item to cart) ║
║ ║
║ Errors Recovered: 8 ║
║ Errors Skipped: 2 ║
║ ║
║ Context Usage: 62% (within limits) ║
╚══════════════════════════════════════════════════════════════╝autonomous rollback [checkpoint-id]
Rolls back to a specific checkpoint.
Example:
autonomous rollback checkpoint-20250115-143000State Detection
The master orchestrator automatically detects the project state:
def detect_state():
if not exists("feature_list.json"):
return "NEEDS_INITIALIZATION"
if exists(".claude/handoffs/current.json"):
return "CONTINUE_FROM_HANDOFF"
features = load("feature_list.json")
if all(f["passes"] for f in features):
return "COMPLETE"
return "CONTINUE_IMPLEMENTATION"Files Created
| File | Purpose |
|---|---|
feature_list.json | All features with pass/fail status |
init.sh | Environment setup script |
claude-progress.txt | Human-readable progress log |
.claude/master-state.json | Orchestrator state |
.claude/handoffs/*.json | Handoff packages |
.claude/checkpoints/*.json | Rollback points |
.claude/memory/*.json | Error→solution chains |
Multi-Session Workflow
SESSION 1 SESSION 2 SESSION 3
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ autonomous │ │ autonomous │ │ autonomous │
│ start: spec │ │ continue │ │ continue │
├─────────────┤ ├─────────────┤ ├─────────────┤
│ Initialize │ │ Load state │ │ Load state │
│ Features │ │ Resume │ │ Resume │
│ 1-15 │──handoff──▶ │ Features │──handoff──▶ │ Features │
│ │ │ 16-35 │ │ 36-50 │
│ Context: 85%│ │ Context: 85%│ │ Context: 60%│
└─────────────┘ └─────────────┘ └─────────────┘
│
▼
┌─────────────┐
│ COMPLETE │
│ 50/50 ✓ │
└─────────────┘Skill Dependencies
The master orchestrator uses all 16 skills:
autonomous-master
├── Layer 1: Session Management
│ ├── autonomous-session-manager
│ ├── context-state-tracker
│ └── security-sandbox
├── Layer 2: Agent Roles
│ ├── initializer-agent
│ ├── coding-agent
│ └── progress-tracker
├── Layer 3: Context Engineering
│ ├── context-compactor
│ ├── memory-manager
│ └── handoff-coordinator
├── Layer 4: Verification & Recovery
│ ├── browser-e2e-tester
│ ├── error-recoverer
│ └── checkpoint-manager
└── Layer 5: Orchestration
├── autonomous-loop
├── parallel-agent-spawner
├── autonomous-cost-optimizer
└── tdd-workflowConfiguration
Edit .claude/master-config.json:
{
"max_sessions": 20,
"features_per_session": 15,
"context_threshold": 0.85,
"auto_checkpoint": true,
"parallel_features": false,
"tdd_strict": true,
"e2e_required": true
}Error Recovery
When errors occur:
- Transient errors (network, rate limit): Automatic retry with backoff
- Code errors (syntax, type): Attempt fix, retry
- Test failures: Debug, fix, retry
- Unrecoverable: Rollback to checkpoint, skip feature, continue
All errors are stored in memory for future reference (causal chains).
Scripts
scripts/master_orchestrator.py- Core orchestrationscripts/state_machine.py- State transitionsscripts/command_parser.py- Parse user commandsscripts/session_detector.py- Detect project statescripts/continuation_generator.py- Generate handoff prompts
References
references/COMMANDS.md- Full command referencereferences/STATE-MACHINE.md- State transition detailsreferences/TROUBLESHOOTING.md- Common issues and fixes
- Repository
- fernandezbaptiste/Skrillz
- Commit
93ed392
- Last updated
- First committed
Canonical home
fernandezbaptiste/Skrillz
In sync
since Sep 12, 2026
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.