what is fable-sonnet-orchestrator-kit fr?

nickalaslight/fable-sonnet-orchestrator-kit — explained in plain English

Analysis updated 2026-05-18

★ 1PowerShellAudience · developerComplexity · 3/5Setup · moderate

vibe map

mindmap
  root((orchestrator-kit))
    Workflow loop
      GitHub issues as todo list
      Git worktree per issue
      PR open and review
      Merge as approval
    Roles
      Orchestrator main agent
      Sonnet executor subagents
      Issue triage agent
    Enforcement
      Stop hook PowerShell script
      Blocks without PR
      Injects review feedback
    Memory
      Handoff.md rolling summary
      SessionStart auto-inject
    Audience
      Developers
      Vibe coders
      AI workflow builders

mindmap root((orchestrator-kit)) Workflow loop GitHub issues as todo list Git worktree per issue PR open and review Merge as approval Roles Orchestrator main agent Sonnet executor subagents Issue triage agent Enforcement Stop hook PowerShell script Blocks without PR Injects review feedback Memory Handoff.md rolling summary SessionStart auto-inject Audience Developers Vibe coders AI workflow builders

what do people make with this?

VIBE 1

Drop the .claude folder into a project and give Claude Code a request, it will break the work into GitHub issues, dispatch subagents to implement each one, and manage the PR review loop.

VIBE 2

Use the Stop hook to enforce that every subagent session produces a pull request before it ends, preventing silent incomplete work.

VIBE 3

Pin subagent model versions in the agent definition files to control cost when the main orchestrator session runs on an expensive model.

what's the stack?

PowerShellClaude CodeGitHub CLI

how it stacks up fr

	nickalaslight/fable-sonnet-orchestrator-kit	c0urag1/break-risk-intel-skill	pnwcomputers/jwrapper-screenconnect-rat-remediation-toolkit
Stars	1	1	1
Language	PowerShell	PowerShell	PowerShell
Setup difficulty	moderate	easy	moderate
Complexity	3/5	2/5	3/5
Audience	developer	ops devops	ops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires Claude Code, the GitHub CLI authenticated non-interactively, and PowerShell 7+ installed, three placeholder values must be replaced before use.

No license file is included in the repository.

in plain english

This repository is a set of configuration files for Claude Code, an AI coding assistant, that wires up a specific way of working on GitHub projects. The goal is to split the AI's role in two: one main agent acts as a manager that breaks down requests into GitHub issues and hands each issue off to a separate focused subagent to implement. The subagents work on isolated copies of the code, open pull requests, and the main agent reviews and merges them. The workflow goes in a fixed loop: a request comes in, the main agent turns it into one or more GitHub issues, a subagent per issue creates a separate working branch, makes the smallest correct change needed to close that issue, opens a pull request, and the main agent reviews it. A PowerShell script enforces the hand-offs at every step. If a subagent finishes its turn without opening a pull request, the script blocks it from proceeding until one exists. If the main agent has requested changes on a pull request, the script injects the review feedback into the subagent's context so it fixes the issues in that same session. The practical benefit is that this structure keeps the two agents from doing each other's jobs. The main agent handles judgment and sequencing. The subagents handle implementation. The configuration pins the subagents to a specific Claude model version so that cost does not accidentally escalate if the main session is running on a more expensive model. A rolling handoff document keeps a summary of current state so that if the main agent is interrupted or restarted, a fresh instance can pick up where the previous one left off. Installation is copying the .claude folder into your project and replacing three placeholder values with your GitHub organization, local checkout path, and secrets directory path. No credentials are stored in the repository files themselves.

prompts (copy fr)

prompt 1

I want to use the fable-sonnet-orchestrator-kit with my GitHub repo. Walk me through the three placeholder replacements I need to make in the .claude folder files and what each value should be.

prompt 2

Explain how the executor-stop-gate.ps1 Stop hook works in this kit: what conditions does it check, when does it block the agent, and how does it inject review feedback?

prompt 3

I am setting up this orchestrator kit. How does the SessionStart hook inject the orchestrator role, and why do the subagents need separate agent definition files while the main agent only needs a skill?

Frequently asked questions