← all publishers

fredhead88

@fredhead88 source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 21 hours ago last updated

1. ▌
   Orc · fredhead88 bundle

   Boot a session into the INTEGRATOR role (formerly ORCHESTRATOR) for the DO-IT pipeline. Use when the user says 'orc', '/orc', 'integrator', 'be the integrator', 'be the orchestrator', 'start as integrator', 'boot the integrator', 'this is the integrator session', or opens a session whose job is to take specs written by thinker sessions, derive each spec's file footprint, assign it to the builder pool via the build lane, then speculative-re-check, merge, and deploy the ready branches builders hand back. The integrator is the SINGLE session that touches the real working tree and the only one that commits or deploys. It runs on the strongest model available, stays lean and interactive, NEVER builds (even when idle), reads only the ledger + lane files, owns git-tree custodianship, mirrors the ledger to a harness task list, and hands off to the next integrator via a relay baton. `/orc` is preserved as an alias. Invoke at the START of an integrator session.
   0
   installs
2. ▌
   Rev · fredhead88

   Boot a session into the REVIEWER role for the Albert Scott repo. Use when the user says 'rev', '/rev', 'be the reviewer', 'start the review session', 'this is the rev session', or opens a session whose job is to drive the verification loop, watch what's awaiting prod-verification, spot-check the rendered product, write per-criterion verdicts, and file correctives back to the orchestrator. rev is the standing review twin of orc — one builds, one reviews. It runs on Opus, self-relays on a context ceiling exactly like orc (its OWN relay, never orc's), never touches the build tree, never commits, never authors specs. Invoke at the START of a reviewer session.
   0
   installs
3. ▌
   Think · fredhead88

   Boot a session into the THINKER role for the DO-IT pipeline. Use when the user says 'think', '/think', 'thinker session', 'let's spec something out', 'brainstorm X', 'triage these ideas', 'sort this dump', 'collect some bugs', or 'process the done work' — any session whose job is discovery, intake, capture, or review that ends in a spec (or a closed review), not code. A thinker is READ-ONLY on code: never edits files, never touches git. It has four shapes (brainstorm / review / intake-triage / collect) and performs its own handoffs (hand a spec to the orchestrator, send a memo). Stage 2 of the DO-IT pipeline. Invoke at the START of a thinking session.
   0
   installs
4. ▌
   Builder · fredhead88

   Boot a session into the BUILDER role for the DO-IT pipeline. Use when the user says 'builder', '/builder', 'be a builder', 'start a builder session', 'this is a builder pane', or opens a session whose job is to claim ONE assigned spec from the build lane, build it to a mergeable branch in its OWN git worktree, run the full close-out evidence gate against its own running surface, write an identity-stamped review card, push the branch, and hand it to the integrator as ready-to-merge. A builder is ONE of N parallel Opus sessions; it NEVER touches master, NEVER deploys, NEVER edits another spec's files. It runs on the strongest model available with a large context config, dispatches mid-tier sub-agents to build, self-gates blind, and self-relays at 400k via a per-builder baton. The single integrator is the only session that commits to master. Invoke at the START of a builder session.
   0
   installs
5. ▌
   Watcher · fredhead88

   watcher — the standing process reviewer (one level up from rev)
   0
   installs
6. ▌
   Spec Handover · fredhead88

   Hand a finished spec over to the orchestrator. Use when the user says 'spec handover', '/spec-handover', 'hand this spec over', 'ship the spec', 'send this to the orchestrator', 'get this spec across', or any time a spec doc written this session needs to reach the orchestrator session. One atomic, self-verifying action — places the numbered spec in the bus AND writes its ledger record, or errors loudly. NO git. If the spec isn't written yet, this is the wrong skill.
   0
   installs
7. ▌
   Verification Loop · fredhead88

   Use when verifying shipped work on prod, standing up the autonomous verifier, running the verification loop, confirming a spec is actually done end-to-end, or checking whether shipped criteria are hollow. Trigger phrases include "verify shipped work", "stand up the verifier", "run the verification loop", "is this actually done on prod", "check for hollow specs", "autonomous post-ship review".
   0
   installs