jthoma74

Jem Build — Documentation skill for Claude Code

Documentation community

Claude Code skill: turn a PRD/architecture doc into a multi-agent swarm-build protocol — orchestrator prompt, 5 specialist agent prompts, operations manual with merge gates/protected paths/kill switch.

How to install Jem Build

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jthoma74/jem-build and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Jem Build does

Alternatives in Documentation

PDF — Extract text, create PDFs, merge/split documents, and handle forms 94.1k ★
会话管理（Session Manager）需求文档（PRD / Markdown） — 目标：对 Codex / Claude Code 的本地会话记录进行可视化管理，并提供“一键复制 / 一键终端恢复”能力 31.7k ★
99 Release — MoAI-ADK production release via Enhanced GitHub Flow (CLAUDE.local.md §18) 991 ★

README

jem-build

A [Claude Code](https://claude.com/claude-code) skill that turns an architecture / PRD document into a **swarm-build protocol**: four files that let one long-running Claude Code session (the Orchestrator) drive a team of specialist subagents to build the system, with hard safety rails instead of vibes.

PRD / architecture doc  ──▶  jem-build  ──▶  docs/swarm-build/
                                              ├── 00-operations-manual.md   the constitution
                                              ├── 01-orchestrator-prompt.md paste into `claude`
                                              ├── 02-agent-prompts.md       5 specialist templates
                                              ├── 03-build-plan.md          phased, dependency-ordered tasks
                                              └── README.md                 folder index
                                         +    swarm/   runtime state files + journal hook

What the protocol gives you

Mechanism	What it does
5 specialists	Architect (specs only) · Builder (code) · Content Author (docs/prompts) · Integrator (services, runbooks) · Tester (verdicts) — each with an explicit lane and a list of what it may not touch
File-based handoff	Agents never talk to each other. They read/write `swarm/state.md`, `swarm/escalations.md`, `docs/specs/*`, and pull requests. Everything is inspectable and resumable
10 merge gates	CI green · Tester PASS label · checklist complete · no conflicts · recognised branch name · not a protected path · daily cap · not quiet hours · cooldown · no cycle
Protected paths	Migrations, secrets, CI config, dependency manifests, build configs, the protocol itself → always human merge
Auto-revert + cycle detection	Watches `main` for 5 min after every merge; reverts on red; halts after repeated failures on the same task
Kill switches	`touch swarm/STOP` halts everything; `touch swarm/HALT-MER