dotclaude

dotclaude

A multi-agent development workflow system for Claude Code.

Overview

This repository provides a structured workflow for software development using specialized AI agents. The system enables:

• Systematic project planning and specification
• Parallel development with git worktrees
• Automated code validation
• Language-specific coding standards
• Orchestrator-managed workflow from init to merge

For the full project structure, see Architecture.

Getting Started

Install

Option 1: Plugin Marketplace (Recommended)

Install dotclaude via Claude Code's plugin marketplace:

# Add the marketplace repository (first time only)
/plugin marketplace add https://github.com/U-lis/dotclaude

# Install the plugin
/plugin install dotclaude

Option 2: Manual Installation

For direct control or customization, clone and copy manually:

git clone https://github.com/U-lis/dotclaude.git
cp -r dotclaude/.claude your-project/

Note: For updates, use /plugin update dotclaude (plugin installation) or re-clone and copy (manual installation). Restart Claude Code after updating to apply changes.

Optional: GitHub CLI

The /dotclaude:pr command requires GitHub CLI (gh).

• Install: brew install gh (macOS) or see installation guide
• Authenticate: gh auth login

Configure

Configure dotclaude settings for your project:

/dotclaude:configure

See the Configuration section below for available settings and file locations.

Start Your First Task

# In Claude Code session
/dotclaude:start-new

# Orchestrator takes over:
# 1. Asks work type (Feature/Bugfix/Refactor/GitHub Issue)
# 2. Gathers requirements via step-by-step questions
#    - If GitHub Issue: parses issue URL, auto-detects type, pre-fills fields
#      and skips questions already answered in the issue body
# 3. Asks target version (auto-filled from milestone if GitHub Issue)
# 4. Creates and reviews SPEC with user
# 5. Asks execution scope (Design only / Design+Code / Design+Code+Docs)
# 6. Executes selected scope
# 7. Asks post-completion integration (Direct Merge or Create PR)
# 8. Returns final summary

# After merge, create version tag (verifies version consistency, pushes automatically):
/dotclaude:tagging
# Or specify version explicitly:
/dotclaude:tagging 0.3.0

Manual Execution (Bypass Orchestrator)

Individual skills can be invoked directly for debugging or partial work:

/dotclaude:design           # Create implementation plan
/dotclaude:validate-spec    # Validate document consistency
/dotclaude:code 1           # Implement Phase 1
/dotclaude:code all         # Implement all phases
/dotclaude:update-docs      # Update documentation
/dotclaude:merge             # Merge to base branch
/dotclaude:tagging          # Create version tag (with push + version checks)
/dotclaude:tagging 0.3.0   # Create tag for specific version
/dotclaude:purge            # Clean up merged branches and worktrees
/dotclaude:purge 0.3.0     # Clean up using specific version as deployment boundary

Configuration

dotclaude supports both global and per-project configuration.

Configuration Files

Scope	Location	Description
Global	~/.claude/dotclaude-config.json	Applies to all projects
Local	<project_root>/.claude/dotclaude-config.json	Project-specific overrides

Configuration merge order: Defaults < Global < Local

Configuration Command

/dotclaude:configure

Interactive workflow to edit settings at global or local scope. Basic settings (Language, Working Directory, Base Branch) are presented as a multi-question batch for faster configuration. Version Files uses a separate interactive workflow. Changes take effect immediately.

Available Settings

Setting	Type	Default	Description
language	string	en_US	Language for agent conversations and user-facing text. Set via SessionStart hook. Documents remain in English.
working_directory	string	.dc_workspace	Directory for work files (relative to project root)
base_branch	string	main	Default base branch for git operations
version_files	array	[]	Version files for tagging consistency check. Empty = auto-detect. See Version Files.

Version Files