Fredasterehub

Track-boundary living-doc reconciliation and debate protocol.

Implementation constraints, git conventions, Codex MCP usage.

Spec, plan, and task packet formats. GSD rules. Drift detection.

Conductor verdict format, drift protocol, boundary evaluation.

Verification protocol, criteria rubric, verdict format.

Core deadfish invariants and protocols. Referenced by all teammates.

Brownfield discovery protocol (detect, collect evidence, analyze, and write docs/discovery.md).

Kiln pipeline conductor. Launches and resumes the 8-step software-creation pipeline (onboarding, brainstorm, gauge, research, architecture, build, validate, report). Use when the operator runs /kiln-fire, asks to build software with Kiln, or wants to resume a Kiln run. Make sure to use this skill whenever the operator mentions building, forging, or shipping an app with Kiln, or resuming a .kiln/ run, even without the /kiln-fire command. Drives onboarding inline, brainstorm via an interactive teammate, and the autonomous stages via native workflows.

Da Vinci's brainstorm facilitation playbook for Kiln — structured ideation across 62 techniques / 10 categories and 50 elicitation methods, three depth tiers (light/standard/deep) plus an express intake, domain-pivot + stimulus-injection anti-bias, a mandatory style probe, and a clarify pass. The facilitator never authors VISION.md; every turn is captured into the append-only session ledger (.kiln/docs/brainstorm-ledger.jsonl), which a fresh-context compiler alone turns into VISION.md. Loaded by the kiln:the-creator agent during the brainstorm stage; not operator-invoked directly.

deadf(ish) autonomous development pipeline v3.0.0 — heartbeat-driven. Clawdbot cron replaces ralph.sh. Each cycle = fresh isolated session. STATE.yaml = continuity. Strict role separation: Clawdbot orchestrates, GPT-5.2 plans, gpt-5.2-codex implements, verify.sh + Opus sub-agent verify. Transforms vision into shipped code through automated cron-driven cycles with sentinel DSL, deterministic verification, and conservative safety. Use when building software projects or continuing development work. Use when Fred mentions deadfish, pipeline, autonomous coding, or continuing a dev project. Also applies when discussing cycle flow, sentinel blocks, plan/verdict parsing, verify scripts, state management, or heartbeat-driven autonomous development.