Documentation

# Huskies Docs

Everything you need to set up and run huskies — a story-driven development pipeline that turns coding agents into a disciplined team.

Quickstart
Install huskies, run the server, create your first story, and watch an agent implement it.
Configuration
Reference for `project.toml`, `agents.toml`, and `bot.toml`.
Bot commands
Full list of commands available in Matrix, Slack, WhatsApp, and the web UI.
Pipeline stages
How work items move from backlog through QA and merge to done.
Chat transports
Connect huskies to Matrix, WhatsApp, Slack, Discord, or the built-in web UI.
CLI reference
Command-line flags for `huskies`, `huskies init`, and `huskies agent`.

## What is huskies?

Huskies is a story-driven development server. You write stories (feature requests) with acceptance criteria; huskies spawns coding agents in isolated git worktrees, runs them through quality gates, and squash-merges the result to your main branch — all without you writing a line of code.

It ships as a single Rust binary with an embedded React frontend. No separate database or build infrastructure required.

## How it works

1. Write a story. Describe the change with acceptance criteria via the web UI, a chat room (Matrix, WhatsApp, Slack), or by dropping a Markdown file in `.huskies/work/1_backlog/`.
2. Agent picks it up. Run `start <number>` (or configure auto-start). A coder agent creates a feature branch, implements the code, and writes tests against your criteria.
3. Quality gates run. Linters, tests, and compilation checks run automatically when the agent exits. Nothing moves forward until everything passes.
4. QA review. A QA agent verifies each acceptance criterion, runs your test suite, and either approves or rejects with detailed findings.
5. Merge & land. A merge agent resolves conflicts and squash-merges to your main branch. The worktree is cleaned up automatically.

## Key concepts

Stories are Markdown files with YAML front matter. They live in `.huskies/work/` and move through pipeline stages as work progresses.

Agents are Claude Code sessions that run autonomously in git worktrees. Each story gets its own isolated worktree so multiple stories can be in flight simultaneously.

MCP tools give Claude Code sessions programmatic access to the pipeline: creating stories, starting agents, checking status, recording test results.