firu-daniel/autonomous-sdlc-harness

An autonomous software-delivery harness for Claude Code.
You ask for a change, and you get back a branch that has been planned, implemented and independently reviewed, pushed and ready for your review.
It has two entry points, used together: locally, through the plugin and CLI installed below, and from GitHub, where labelling an issue starts a run and comments and reviews steer it to a draft pull request.
The GitHub route works once one maintainer has done a one-time local setup.
You install two things: a Claude Code plugin and a Node CLI.
1. Install the plugin (step A):
bash
claude plugin marketplace add firu-daniel/autonomous-sdlc-harness
claude plugin install autonomous-sdlc-harness@autonomous-sdlc-harness
2. Wire your repository (step B):
bash
npx autonomous-sdlc-harness init
3. Teach it the codebase: type this in an interactive Claude Code session opened on the repository, not in the terminal (step C):
/autonomous-sdlc-harness:harness-analyze
4. Verify (step D):
bash
npx autonomous-sdlc-harness doctor
5. Start the daemon (step E):
bash
npx autonomous-sdlc-harness daemon install
npx autonomous-sdlc-harness daemon start
Before you run it:
Published. The npm package and the plugin marketplace are both live, so the checklist runs as written. This command answers with the published version and exits 0:
bash
npm view autonomous-sdlc-harness version
Contributors. From a clone, the plugin installs as a directory source, and the built CLI is node cli/dist/cli.js. Both routes, and the scratch repository step 3 then needs, are docs/development.md §1 and §5.
The .claude/ write wall. Step 3 writes under .claude/, which no permission entry opens to an unattended run. There it exits 0 having written nothing, so run it supervised and check that the conventions documents changed. See docs/analyze.md §3.
mermaid
flowchart TB
subgraph ship["What ships"]
P["plugin/ — the Claude Code plugin agents · branch- commands · /autonomous-sdlc-harness:harness-analyze · harness-read-mention PreToolUse guard hooks · instruction cores and forks samples · helper scripts · flow documents"]
C["cli/ — the npm package autonomous-sdlc-harness init · doctor · config · daemon · docs"]
end
subgraph repo["An adopted repository, after init"]
CFG["harness.config.json — layers, commands, protectedBranches, stateDir, phases"]
PROF["a generated permission profile, committable project settings, a pre-push backstop"]
SCR["scriptsDir — the outer-loop scripts: watcher, commit, push, worktree, notify"]
ST["stateDir — the run-artifact tree: plans, reviews, ledgers, statistics, inbox, logs"]
end
C -->|writes| CFG
C -->|writes| PROF
C -->|writes| SCR
C -->|writes| ST
D["a file is dropped: stateDir/autonomous_inbox/<branch>_task_prompt.md"] --> W
ASK["an ordinary session: 'add a pin button' → the offer → /autonomous-sdlc-harness:branch-prompt"] --> D
N -.->|"writes it by hand, or through /autonomous-sdlc-harness:branch-prompt"| D
W["autonomous-watcher.sh — route by filename, prepare a working copy with create-worktree.sh, place and commit the prompt, launch headless, classify the exit"]
W -->|"one -p session under the generated profile"| E
P -.->|"supplies the command, agents and instructions the session runs"| E