AI-powered system of work for software engineering
You can install this plugin from any of these themed marketplaces. Choose one, add it as a marketplace, then install the plugin.
Choose your preferred installation method below
A marketplace is a collection of plugins. Every plugin gets an auto-generated marketplace JSON for individual installation, plus inclusion in category and themed collections. Add a marketplace once (step 1), then install any plugin from it (step 2).
One-time setup for access to all plugins
When to use: If you plan to install multiple plugins now or later
Step 1: Add the marketplace (one-time)
/plugin marketplace add https://claudepluginhub.com/marketplaces/all.jsonRun this once to access all plugins
Step 2: Install this plugin
/plugin install sow@allUse this plugin's auto-generated marketplace JSON for individual installation
When to use: If you only want to try this specific plugin
Step 1: Add this plugin's marketplace
/plugin marketplace add https://claudepluginhub.com/marketplaces/plugins/sow.jsonStep 2: Install the plugin
/plugin install sow@sowAn AI-powered framework for software engineering that provides a structured, opinionated approach to building software with AI assistance.
sow leverages Claude Code's capabilities to create a unified development experience across projects through:
# Install Claude Code Plugin
/plugin install sow@sow-marketplace
# Restart Claude Code
exit && claude
# Initialize in your repository
/init
# Start your first project
git checkout -b feat/my-feature
/start-project "Add new feature"
# Let the orchestrator coordinate the work
# When ready to merge
/cleanup
git commit -m "chore: cleanup sow project state"
.claude/) - AI agents, commands, hooks (distributed via plugin).sow/) - Project knowledge, external context, active work stateš OVERVIEW - Complete introduction to sow concepts and terminology
š USER_GUIDE - Installation, daily workflows, and troubleshooting
š ARCHITECTURE - Design decisions, patterns, and architectural philosophy
š FILE_STRUCTURE - Complete directory layout and organization
š AGENTS - Multi-agent system, roles, and coordination
š COMMANDS_AND_SKILLS - Slash commands and agent skills reference
š PROJECT_MANAGEMENT - Project lifecycle, phases, tasks, and logging
š HOOKS_AND_INTEGRATIONS - Event automation and external tool integrations
š DISTRIBUTION - Packaging, versioning, and upgrade workflows
š SCHEMAS - File format specifications (state.yaml, indexes, etc.)
š CLI_REFERENCE - CLI command documentation
š Claude Code Features - Claude Code capability reference
ā Consistent experience across all projects ā Clear structure for complex work ā Resume anytime without losing context ā Specialized expertise via worker agents ā Progressive discovery instead of upfront planning
ā Shared conventions via committed execution layer ā Knowledge sharing via information sinks ā Collaboration through committed project state on branches ā Quality gates through agent specialization ā Reduced onboarding with standardized structure
ā Focused context - workers receive only relevant information ā Clear roles - each agent has specific expertise ā Structured state - can resume without conversation history ā Fail-forward - can adapt to discoveries and changes ā Audit trails - logs track all actions
# 1. Create feature branch
git checkout -b feat/add-authentication
# 2. Start project
/start-project "Add JWT authentication"
# Orchestrator:
# - Assesses complexity: "moderate"
# - Selects phases: design, implement, test
# - Creates tasks with assigned agents
# - Spawns architect for design task
# 3. Continue working
/continue
# Orchestrator:
# - Reads project state
# - Spawns next worker (implementer)
# - Worker writes code with TDD
# - Updates state
# 4. Provide feedback if needed
"The JWT service should use RS256, not HS256"
# Orchestrator creates feedback, respawns worker
# 5. Complete and clean up
/cleanup
git commit -m "chore: cleanup sow project state"
git push
# 6. Create PR and merge
# CI verifies no .sow/project/ exists
Strong opinions:
Flexible where it matters:
sow complements existing tools:
Not replacing: JIRA, Linear, GitHub Issues, Sprint planning, Team chat
sow is for: Active work coordination, AI agent orchestration, Short-term execution (hours to days)
Current State: Comprehensive architecture design complete, implementation in progress
Documentation: Complete (you're looking at it!)
Next Steps:
sow/
āāā docs/ # Comprehensive documentation
ā āāā OVERVIEW.md
ā āāā ARCHITECTURE.md
ā āāā FILE_STRUCTURE.md
ā āāā AGENTS.md
ā āāā COMMANDS_AND_SKILLS.md
ā āāā HOOKS_AND_INTEGRATIONS.md
ā āāā USER_GUIDE.md
ā āāā PROJECT_MANAGEMENT.md
ā āāā DISTRIBUTION.md
ā āāā SCHEMAS.md
ā āāā CLI_REFERENCE.md
āāā research/ # Research and feature references
ā āāā CLAUDE_CODE.md
āāā archive/ # Historical discovery documents
āāā BRAINSTORMING.md
āāā PROJECT_LIFECYCLE.md
āāā FS_STRUCTURE.md
āāā EXECUTION.md
āāā DISTRIBUTION.md
This project is in early development. Design feedback and contributions welcome!
Areas of interest:
MIT (placeholder - to be determined)
Start with docs/OVERVIEW.md for a comprehensive introduction, then explore the other documentation based on your needs.
For users: USER_GUIDE.md For contributors: ARCHITECTURE.md For reference: SCHEMAS.md
0.1.0