huzairsaputra/scrum-kit

Scrum sprints for Claude Code agent teams.
One agent, one turf. A hook enforces it, your CI decides when it's done.
English · Bahasa Indonesia
Parallel coding agents are fast until two of them edit the same migration. scrum-kit runs a sprint the
way a small Scrum team would: an orchestrator splits the backlog, each agent owns one area of the repo
on its own branch, tests are written by someone other than the implementer, and nothing merges until
an independent reviewer and your own CI agree.
It works with any stack (Go, Laravel, Node, Python, …). Nothing project-specific is hard-coded: every
project describes itself in one file, .claude/kit.json.
> The agent prompts, commands, and templates are written in Bahasa Indonesia. Claude reads them
> fine in any language; your team's docs and commit messages follow whatever you set in CLAUDE.md.
## What you get
Per-branch file ownership. A PreToolUse hook reads the branch name (sprint-03/admin/BE-1) and
kit.json, then blocks any Write/Edit outside that agent's area.
Eight agent roles: module-dev, shared-module-owner, api-contract-keeper, qa-test-engineer,
code-reviewer, platform-tooling, security-auditor, spec-change-adapter.
Definition of Done gate that runs your project's own fmt/lint/build/test commands, the same ones
CI runs. No second source of truth.
Headless dispatch. The orchestrator runs heavy work as background claude -p --agent … processes
in per-item git worktrees, not as subagents eating its own context.
GitLab or GitHub, optional OpenAPI contract-first flow, optional Google Drive spec sync.
## Install
Requires Claude Code, git, Python 3 (python3, python, or py), and bash (Git Bash on Windows).
/plugin marketplace add huzairsaputra/scrum-kit
/plugin install scrum-kit@scrum-kit
Then, inside your project:
/scrum-kit:kit-init
It inspects the repo, asks a few questions (modules, base branch, gate commands), and writes
.claude/kit.json, CLAUDE.md, a worktree script, an MR/PR template, and sprint doc skeletons on a new
branch. The project's .claude/settings.json registers this marketplace, so teammates get the same
plugin just by trusting the folder.
## Commands
| Command | What it does |
| /scrum-kit:kit-init | Install the kit in a project (interview, then config + templates). --perbarui to revisit. |
| /scrum-kit:sprint | Run one sprint: spec sync → foundation → contract → parallel implementation → QA → review → one integration MR/PR. |
| /scrum-kit:hotfix | Out-of-sprint work with the same gates. Normal path: a small change approved by the product owner, to the base branch. Emergency path: an urgent production fix with no downtime, merged to the release branch on the product owner's approval, then merged back into base. |
| /scrum-kit:rilis [version] [schedule] | Scheduled release from the base branch to production: readiness checks, downtime assessment, release notes, one MR/PR merged on the product owner's approval, then a tag. |
## How it works
kit.json ──► hook (who may write where) ──► worktree per item ──► agent on sprint-nn/ /
backlog ──► orchestrator ──► claude -p --agent scrum-kit: ──────────┘