auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
What this skill does
# Auto-Claude: Autonomous Coding Framework Autonomous multi-agent system for complex feature implementation with QA validation. ## When to Use ✅ **Use Auto-Claude for:** - **Complexity 3-4** - Well-defined features, multiple files - Established codebases with clear patterns - Repetitive tasks (CRUD, forms, API endpoints, auth flows) - When you prefer review-at-end vs step-by-step - Features requiring iterative refinement with QA validation ❌ **Don't use Auto-Claude for:** - **Complexity 1-2** - Use manual `/start-task` instead - **Complexity 5+** - Use `/gsd:new-project` instead - Greenfield projects (no existing codebase patterns) - Exploratory/research tasks (unclear requirements) - Simple typo fixes or config changes - Tasks requiring human decision-making during implementation **Quick Guide:** - Complexity 1-2 → Manual implementation - Complexity 3-4 → **Auto-Claude** (autonomous) - Complexity 5+ → GSD (multi-phase) ## Core Capabilities 1. **Codebase Analysis** - Generates semantic baseline 2. **Spec Generation** - Creates detailed implementation plan 3. **Autonomous Implementation** - Multi-agent coordination 4. **Git Worktree Isolation** - Safe development in separate worktree 5. **QA Validation** - Iterative quality checks 6. **Memory System** - Graphiti-powered context retention ## Workflow ```bash # From project directory: /auto-claude Add user authentication with JWT tokens ``` **What Happens:** 1. Analyzes project structure → generates baseline 2. Creates implementation spec → stores in ~/.auto-claude/specs/ 3. Creates git worktree → isolated development environment 4. Autonomous agents implement → with QA loops 5. Returns completed code → ready for review **Output Location:** `~/.auto-claude/` (gitignored) ## Integration with Existing Workflows **Manual Implementation:** ``` /start-task [description] → Claude implements step-by-step ``` **Autonomous Implementation:** ``` /auto-claude [description] → Auto-Claude implements autonomously ``` **Multi-Phase Projects:** ``` /gsd:new-project → GSD for project management ``` ## Configuration **Location:** `~/.auto-claude/.env` **Required:** - `CLAUDE_CODE_OAUTH_TOKEN` - Get from `/settings` in Claude Code **Optional (Recommended):** - `GRAPHITI_ENABLED=true` - Semantic memory - `GOOGLE_API_KEY` - For Gemini embeddings (memory feature) - Alternative: Ollama (local) or disable memory ## Trade-offs **Strengths:** - Autonomous with minimal oversight - QA validation ensures quality - Git worktree prevents main branch disruption - Memory learns from previous sessions **Limitations:** - Best for established codebases - Requires clear specifications - Uses tokens for multi-agent iterations - Manual merge required after completion ## Examples **Good use cases:** - "Add user authentication with JWT tokens and session management" - "Implement dark mode toggle with localStorage persistence" - "Refactor API layer to use async/await instead of callbacks" - "Add pagination to user list with 20 items per page" - "Create export-to-CSV functionality for reports" **Poor use cases:** - "Fix typo in README" (too simple) - "Explore best approach for state management" (exploratory) - "Build entire e-commerce platform" (too large, use GSD) - "Make the app better" (too vague) ## Typical Timeline - **Analysis:** 30 seconds - **Spec Generation:** 1-2 minutes - **Implementation:** 5-15 minutes (depends on complexity) - **QA Validation:** 2-5 minutes - **Your Review:** 5-10 minutes **Total:** 15-30 minutes for most features ## Related - `generic-feature-developer` - Manual implementation patterns - `debug-systematic` - Systematic debugging - `test-specialist` - Testing strategies ## Documentation See `~/.claude/docs/AUTO-CLAUDE-GUIDE.md` for: - Complete setup instructions - Real-world examples with detailed walkthroughs - Troubleshooting guide - Performance tips - Comparison with other workflows
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.