cheese-factory

/cheese-factory

Use this skill when an approved spec decomposes into 5+ file-disjoint behavioural curds and the user wants the whole implementation parallelised, reviewed per-curd, integrated, reviewed again at the seam, and shipped as 1–N reviewable PRs.

Do not use it for single coherent feature work (/cook or /ultracook), fuzzy planning (/mold), review-only work (/age), or specs that decompose into fewer than 5 curds (/ultracook).

/cheese-factory is the portable, harness-agnostic sibling of /fromagerie. Same decomposition pattern, same dual fan-out/fan-in, no bespoke agent files. Every sub-agent is a general-purpose full-peer worker driven by an in-prompt skill invocation.

Inputs

Accept:

/cheese-factory <spec-path-or-slug> [--hard] [--resume <slug>]

• A spec path. When explicit, read it verbatim wherever it points.
• A bare slug. Resolve it to the durable spec path with SPEC=$(python3 ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz artifact-path specs <slug>), then read "$SPEC". The resolver anchors specs at the per-project durable corpus (see shared/formatting.md § Corpus location).
• --hard — propagate the /hard-cheese metacognitive gate flag through per-curd /cook --hard --auto and the Phase 6 /cure --hard --auto --stake medium+. The orchestrator does not fire the gate itself. See skills/hard-cheese/SKILL.md.
• --resume <slug> — read .cheese/cheese-factory/<slug>/manifest.yaml, find the latest phase marked complete, and continue from the next phase.

/cheese-factory does not accept fuzzy or open-ended asks — route those to /mold first. The orchestrator assumes the contract is locked.

--auto is implicit. After Phase 0 gate approval, the chain runs autonomously with no per-step handoff questions. There is no interactive mode — the value of this skill is unattended parallel execution.

When to use /cheese-factory vs alternatives

Skill	Use when
/cook	Single unambiguous task, no decomposition.
/ultracook	Single coherent spec, high-blast-radius, sequential review pipeline.
/cheese-factory	Spec decomposes into 5+ file-disjoint behavioural curds.
/fromagerie	Same problem on Anthropic Claude Code with the bespoke agent files installed and a preference for specialised agent contracts.

Decomposition contract — curds of behaviour

In cheese-factory terms, a curd is the smallest commit-worthy unit of behaviour: small enough to be worked independently, but intended to be pressed back into the whole feature.

The Phase 0 decomposer produces three artifact lists from the spec:

1. seed[] — foundational types / interfaces / enums that 2+ curds depend on.
2. curds[] — parallel units of behaviour, file-disjoint, one acceptance criterion each.
3. wiring[] — integration tasks with topological dependencies (barrels, registrations, routes, config).

The five criteria

Every curd must satisfy all five. Token budgets are explicitly not a criterion — LLM agents cannot estimate their own token usage reliably, and the five behavioural criteria substitute. Curds remain bounded by their file scope, which is decomposer-controlled.

#	Criterion	Decomposer check
1	One behaviour per curd	Describable in a single declarative sentence ("adds X", "extracts Y", "renames Z", "fixes A"). If the description needs "and" between two distinct behaviours, split.
2	One acceptance criterion	Maps to exactly one bullet in the spec's Acceptance Criteria / User Story list. Curds collectively cover every acceptance criterion 1:1.
3	One test target	A single focused test command verifies this curd alone (e.g., vitest run src/orders/order.test.ts). If the curd needs N test commands, it's N curds.
4	File-disjoint	No two curds list the same file. HARD CONSTRAINT.
5	Commit-worthy alone	After this curd's commit, just check (or project equivalent) passes without sibling curds merged. Implied by 4 plus seed carrying any shared deps.

If criterion 4 cannot be satisfied because two curds genuinely share a file, the shared content belongs in seed (if foundational) or wiring (if integration). Curds never share files.

Manifest format

The per-run manifest is written as YAML at .cheese/cheese-factory/<slug>/manifest.yaml. YAML is the human/agent-facing syntax; the contract stays schema-shaped and is documented in references/manifest-schema.json. Keep manifests in the JSON-compatible subset of YAML: mappings, lists, strings, numbers, booleans, and nulls only; no anchors, aliases, tags, or multi-document streams.

The PR plan follows the same convention — written as YAML at .cheese/cheese-factory/<slug>/pr-plan.yaml, with its shape documented in references/pr-plan-schema.json. ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz pr_plan_to_branches reads either YAML or JSON for backward compatibility, but YAML is the canonical format.

Validation (Phase 0)

The decomposer's output is validated by ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz validate_manifest for required sections and field shapes, then by ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz validate_decomposition against:

• Behaviour overlap — each curd describes one behaviour (criterion 1).
• Spec coverage — every acceptance criterion has exactly one curd (criterion 2).
• Test target check — each curd has a focused test command (criterion 3).
• File disjointness — no file appears in two curds (criterion 4).
• Wiring DAG check — no cycles, no cross-branch overlap, barrel files included where curds create new slices.
• Seed minimality — seed contains only files that 2+ curds depend on.

If validation fails: re-run decomposer with violations highlighted. Max 2 retries before escalating to the user.

Phases

Eight phases. The orchestrator walks them top-to-bottom and stops after the last entry or any halt.

#	Phase	Shape
0	Pre-compile	Read spec, decompose via heavy general-purpose sub-agent, validate against the five criteria, user gate
1	Seed	Orchestrator inline edits via /cheez-write (or host edit tool if tilth MCP is unavailable), commit, push
2	Curds (fan-out)	N parallel general-purpose spawns; each runs /cook --auto → /press --auto → /age --auto (inline-degrade) → /cure --auto --stake medium+ and commits
3	Merge curds (fan-in)	Cherry-pick curd commits → orchestrator branch; /melt on conflicts
4	Wiring (sequential within wave)	Integration files only; per-task general-purpose spawn with wiring-only prompt
5	Final merge wiring	Wiring commits → orchestrator branch; conflicts here = halt (decomposer error)
6	Post-merge review (fresh-context, ultracook-style)	Three sub-agent spawns: /press --auto, /age --auto, /cure --auto --stake medium+. Single pass.
7	PR plan + publish	Heavy PR planner sub-agent decides layout, orchestrator delegates publish via skill discovery (/pr-stack, /gh, fallbacks)

Phase 0 — Pre-compile

Read the spec from the argument (or, if --resume <slug>, read the manifest and skip to the next incomplete phase).

Validate the spec has: Executive Summary, Problem Statement, User Stories, Acceptance Criteria, Quality Gates. Fail fast if any is missing.

Hard worktree gate: detect the host's worktree mechanism (Conductor, git worktrees, plain branches) and prompt if working on the default branch. Never skipped.

Spawn a heavy general-purpose decomposer sub-agent (prompt template at references/decomposer-prompt.md) with the spec text, the five criteria, the validation checks, and instructions to produce seed[], curds[], wiring[], and a manifest scaffold.

The decomposer may invoke /culture or /briesearch internally if it needs to ground its decomposition against the codebase or external docs.

Front-load permissions: present the per-host permission manifest (git, the project's quality gate command, the host-specific spawn primitive) to the user. On approval, merge into the host's settings.

Gate — User Approval

Present the full plan:

## Cheese-Factory Plan: <slug>

### Seed (sequential)
1. <description> — files: [<list>]

### Curds (parallel)
| # | Behaviour | Acceptance criterion | Files | Test target |
|---|---|---|---|---|

### Wiring DAG
| # | Type | File | Depends on |
|---|---|---|---|

### Review Pipeline
Per-curd: /cook → /press → /age (inline-degrade) → /cure
Post-merge: /press → /age → /cure (fresh-context sub-agents)

A. Approve — start execution
B. Modify — change the decomposition
C. Re-decompose — different boundaries
D. Pause — hold off

Use the shared handoff gate in ../../shared/handoff-gate.md for this approval step. All four options keep cheese-factory running internally (no skill transition) — they use continue: identifiers rather than dispatch: commands per the gate vocabulary:

• Approve — continue: write-manifest-then-seed: write .cheese/cheese-factory/<slug>/manifest.yaml, set phase: gate_approved, then proceed with Phase 1 (seed execution).
• Modify — continue: ask-for-decomposition-change: ask one targeted question for the requested decomposition change, then re-render the plan.
• Re-decompose — continue: re-run-decomposer: re-run the decomposer with the user's boundary instruction. Retry at most twice.
• Pause — dispatch: none: leave the manifest draft and report its path.

Do NOT proceed without explicit approval.

Compaction seam C1

Drop: full spec text, permission manifest, decomposition reasoning. Keep: slug, spec summary (≤2K chars), manifest path, quality gate commands.

Phase 1 — Seed (sequential, inline)

Seed items are minimal — only the shared types / protocols that curds cannot compile without. The orchestrator executes seed inline (a deliberate exception to the orchestrator's "never write code" rule because seed is always small).

For each seed item:

1. Implement the change. Prefer /cheez-write when tilth MCP is present; otherwise fall back to the host's native edit tool (per the cheez-* portability rule in README.md). The skill must not hard-fail when /cheez-write is unavailable.
2. Run quality gates (the project's just check or equivalent) — if gates fail, STOP.
3. Commit via /commit (if available) or git commit direct.

Push to branch — curds branch from HEAD.

Update manifest: phase: seed_complete, commit SHAs.

Phase 2 — Curds (fan-out)

Spawn ALL curd workers in a single message via the host's fan-out primitive. If more than 5 curds, dispatch in waves of 5.

Each curd worker is a general-purpose sub-agent (full peer of the orchestrator — same model, full tools, full skills, full MCP) given the per-curd prompt at references/curd-prompt.md.

Collect results as curds complete. For failed curds: retry ONCE with error context. Mark retry_count: 1; do not retry twice.

Update manifest: curd statuses, worktree paths, branch names, commit SHAs.

Compaction seam C2

Drop: decomposer artifacts, curd dispatch prompts, curd return summaries. Keep: slug, manifest path, quality gate commands, curd branch list. Read from disk when needed: wiring DAG.

Phase 3 — Merge curds (fan-in)

Cherry-pick curd commits onto the orchestrator branch in curd-id order:

For each curd (in order):

1. git cherry-pick <curd_commit_sha> — or, if the host fan-out used worktrees, merge the worktree branch.
2. On conflict: invoke /melt if available, else fall back to mergiraf → git rerere → manual.
3. If /melt cannot resolve: STOP, fall back to per-curd PRs in Phase 7.

After all curds merged: run quality gates. If failing, STOP and report — curds passed individually but conflict in aggregate (decomposer error).

Phase 4 — Wiring (fan-out, sequential within wave)

Read wiring DAG from manifest. Dispatch wiring tasks in topological order, sequentially within each wave (concurrent commits to the same working directory race on git's index.lock).

Each wiring worker is a general-purpose sub-agent with the prompt template at references/wiring-prompt.md.

For failed wiring tasks: retry ONCE. If still failing, mark incomplete in manifest.

Phase 5 — Final merge wiring

Cherry-pick wiring commits onto the orchestrator branch.

If conflicts arise here: STOP. Wiring conflicts mean the decomposer's DAG was wrong (wiring touched implementation territory, or two wiring tasks shared a file outside the DAG). Do not auto-resolve.

Compaction seam C3

Drop: wiring DAG details, per-curd diffs, intermediate merger reports. Keep: slug, spec path (for downstream skills), quality gates, list of all changed files, list of all commit SHAs (curds + seed + wiring).

Phase 6 — Post-merge review (ultracook-style fresh-context)

By Phase 6 the orchestrator's context is heavy. Run the final review pipeline in fresh-context sub-agents to keep review reasoning adversarial and clean.

Three sequential spawns:

1. /press --auto on the merged diff — writes .cheese/press/<slug>.md.
2. /age --auto on the merged diff — writes .cheese/age/<slug>.md.
3. /cure --auto --stake medium+ on the age findings — writes .cheese/cure/<slug>.md.

Each spawn is a full-peer general-purpose sub-agent. Pass the no-chain-forward directive (same as /ultracook) so each spawn runs its phase only.

Single pass through — no two-cure-pass cap. Curds each had their own press/age/cure; this is integration-level review.

If any phase writes status: halt: <reason> in its slug, surface the halt and STOP. If /cure writes next: done, continue to Phase 7.

Phase 7 — PR plan + publish

Spawn a heavy general-purpose PR planner sub-agent (prompt template at references/pr-planner-prompt.md) with the wiring DAG, the manifest, the merged diff, and the spec summary.

The planner emits one of four shapes:

Shape	When	PR layout
single	Small total diff, tightly coupled	All commits in one PR.
orthogonal_flat	Curds touch disjoint slices, no seed/wiring coupling	N PRs each branching from main.
stacked_linear	Linear dependencies seed → curds → wiring	gt/gh stack.
diamond_stack	Seed and wiring exist; curds independent of each other	seed PR (base) → N parallel curd PRs → wiring PR.

The planner writes its grouping to .cheese/cheese-factory/<slug>/pr-plan.yaml and returns control.

Skill discovery (orchestrator-side)

Before publishing PRs, the orchestrator detects which skills are available and picks the right delegate:

Need	Prefer	Fallback
Stack publish	/pr-stack (Graphite gt or gh stack)	manual gh pr create --base <prev-branch> chain
Commits	/commit	git commit direct
PR publish	/gh	gh pr create direct
Merge conflicts	/melt	mergiraf → rerere → kdiff3 direct

Detection: attempt to invoke the skill via the host's Skill tool; on unrecognised-skill error, fall back. Cache the result for the rest of the phase.

Publish

For each PR group in the plan:

1. Read group metadata from pr-plan.yaml.
2. Push the branch (use ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz pr_plan_to_branches to convert pr-plan.yaml to branch-creation commands).
3. Create the PR (via /gh if available, else gh pr create direct).
4. For stacks: invoke /pr-stack with the ordered branch list.
5. Update manifest with PR numbers and URLs.

Final report

## Cheese-Factory Complete: <slug>

### Results
| Phase | Status | Detail |
|---|---|---|
| Seed | complete | 2 commits |
| Curds | 5/6 succeeded | Curd #4 failed after retry |
| Merge | complete | — |
| Wiring | 4/4 complete | — |
| Final merge | complete | — |
| Post-merge review | press: pass, age: 3 findings, cure: 3 applied |
| PR plan | diamond_stack | seed + 5 curds + wiring = 7 PRs |

### PRs
| PR | Title | Stack base |
|---|---|---|
| #101 | feat(orders): shared types | main |
| #102 | feat(orders): order entity | #101 |
| ... |

### Manual actions needed
- Curd #4 failed: {error_summary}

Manifest: .cheese/cheese-factory/<slug>/manifest.yaml

Orchestrator token discipline

The orchestrator reads ONE thing: the spec. Everything else is delegated.

Must not:

• Read / grep / glob codebase files (decomposer + per-curd workers do that).
• Run build / test commands (per-curd workers + post-merge sub-agents do that).
• Read full sub-agent reports — work from handoff slug digests.

Should:

• Read the spec once at Phase 0.
• Read per-phase handoff slugs (each ≤2KB).
• Write manifest updates after each phase.
• Decide chain progression based on slug status and next fields, never on sub-agent stdout.

Compaction strategy

Three seams where the orchestrator drops accumulated context.

Seam	After	DROP	KEEP
C1	Phase 0 (gate approved)	Full spec text, permission manifest, decomposition reasoning	Slug, spec summary (≤2K), manifest path, quality gates
C2	Phase 2 (curds done)	Decomposer artifacts, curd dispatch prompts, curd return summaries	Slug, manifest path, quality gates, curd branch list
C3	Phase 5 (final merge done)	Wiring DAG, per-curd diffs, merger details	Slug, spec path, quality gates, changed files list, all commit SHAs

At each seam, write a self-summary to the manifest before dropping:

{
  "phase_summary": "<2-3 sentences: what happened, what succeeded/failed, what's next>",
  "carry_forward": ["slug", "spec_summary", "manifest_path", "quality_gates"]
}

On --resume, read phase_summary from the manifest. This is the only cross-seam continuity mechanism — do not rely on conversation history.

Spawn primitive contract (host-agnostic)

The orchestrator never names a specific host primitive. Any primitive that satisfies all five invariants below is acceptable. See references/spawn-primitive-reference.md for host-by-host examples.

1. Fresh context per spawn. The sub-agent boots with no memory of prior phases.
2. Full-peer inheritance. Same model as the parent, full tool access, full skill access, full MCP access. No diminutive workers.
3. No chain-forward. The sub-agent runs only its phase and returns. The no-chain-forward directive is passed in the prompt.
4. Returns control. The orchestrator regains control after each spawn so it can read the handoff slug.
5. Writes handoff slug. Each spawn writes its result to .cheese/<phase>/<slug>.md per the schema. The orchestrator decides chain progression from the slug, never from stdout.

If the host harness exposes no fan-out primitive at all, /cheese-factory is the wrong skill — recommend /ultracook for the same review semantics in the parent's own context.

Handoff slug schema

Every phase writes a handoff slug to .cheese/<phase>/<slug>.md (or, for per-curd workers, to .cheese/cheese-factory/<slug>/curds/<curd-id>.md) with the minimum shape:

status: ok | halt: <one-line reason>
next: <phase-name | done>
artifact: <path-to-richer-report-if-any>
<one-line orientation: what this phase did>

For phases that already write rich reports (/age, /press, /cure), the schema is prepended at the top of the same file.

Quality gates

/cheese-factory runs the project's quality gate command (typically just check per AGENTS.md) at four points:

1. After seed (Phase 1).
2. Inside each curd worker (after its /cure step).
3. After curd merge (Phase 3, before wiring).
4. After Phase 6 /cure.

If any gate fails: STOP, report, do not silently fix.

--hard propagation

/cheese-factory <spec> --hard:

• Passes --hard to per-curd /cook --hard --auto — each curd gets its own hard-cheese vibecheck at its /cure share-for-review boundary.
• Passes --hard to Phase 6 /cure --hard --auto --stake medium+ — the integration /cure runs the share-for-review vibecheck too.

The orchestrator does not invoke /hard-cheese itself — it propagates the flag. See skills/hard-cheese/SKILL.md.

--resume <slug>

Read manifest at .cheese/cheese-factory/<slug>/manifest.yaml, find the latest phase marked complete, skip to the next phase. Report: Resuming <slug> from phase <N>.

If the manifest references commits that no longer exist (rebased, deleted), fail fast and report — do not silently re-execute the phase.

Error recovery

Failure	Recovery
No spec argument	STOP. Report cheese-factory requires an approved spec; run /mold first if you need to shape one. Do not auto-dispatch — cross-skill handoffs stay user-visible.
Overlap / criterion violation in decomposer output	Re-run decomposer (max 2 retries)
Seed gate failure	STOP, report — do not dispatch curds
Curd fails	Retry once with error context, then mark failed
All curds fail	STOP, no merge/wiring
Curd merge conflict	/melt; if /melt fails, fall back to per-curd PRs
Wiring agent fails	Retry once, mark incomplete if still failing
Phase 5 conflicts	STOP — decomposer error, report to user
Phase 6 /press or /age halt	Surface halt, STOP
Phase 6 /cure cannot apply any finding	Surface report, STOP
/pr-stack not available, plan calls for stack	Fall back to manual gh pr create --base chain
--resume on missing manifest	Fail fast

Never proceed past Phase 0 gate without explicit user approval. Never claim green on partial work.

What the orchestrator never does

• Read codebase files (sub-agents explore, orchestrator routes).
• Run build / test commands (per-curd workers and post-merge sub-agents handle verification).
• Write implementation code (cook agents and wiring agents implement; the orchestrator's only inline writes are the small seed items in Phase 1).
• Make decomposition decisions after Phase 0 (plan is locked at gate approval).
• Retry more than once (curds and wiring get one retry, then mark failed).
• Auto-resolve Phase 5 conflicts (wiring conflicts = decomposer error).
• Estimate sub-agent token usage (decomposition uses behavioural criteria, not token counts).

Gotchas

• /age nesting depth: curd workers invoke /age which normally fans out to 6 review sub-agents (level 2, blocked). /cheese-factory requires /age to support an inline-degrade mode for sub-agent invocation — see skills/age/SKILL.md "Inline-degrade mode".
• Context death after C2: after C2 the orchestrator has no curd details. The wiring DAG must be self-contained on disk. If wiring references curd internals not captured in the manifest, wiring agents will fail.
• Wiring race conditions: wiring tasks commit to the same working directory. Phase 4 dispatches them sequentially (not in parallel) to avoid git index.lock races even when files differ.
• bypassPermissions doesn't bypass Bash: curd workers can Edit/Write freely but cannot git push or gh pr create without explicit Bash allowlist. The orchestrator must handle all push / PR operations.
• Stale worktrees: curd worktrees persist after Phase 3 merge. The orchestrator does NOT clean them up — recommend the user run /worktree-sweep (or host equivalent) after the pipeline completes.

References

• references/decomposer-prompt.md — heavy decomposer sub-agent prompt template.
• references/curd-prompt.md — per-curd worker prompt template.
• references/wiring-prompt.md — per-wiring task prompt template.
• references/pr-planner-prompt.md — PR planner sub-agent prompt template.
• references/manifest-schema.json — JSON Schema for the manifest.
• references/pr-plan-schema.json — JSON Schema for the PR plan, $ref'd from manifest-schema.json.
• references/spawn-primitive-reference.md — host-by-host invocation examples plus the five invariants.
• ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz validate_manifest — Phase 0 structural validation of required manifest sections and fields.
• ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz validate_decomposition — Phase 0 semantic validation of decomposer output against the five criteria.
• ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz validate_pr_plan — Phase 7 validation of PR planner output before branch creation.
• ${CLAUDE_SKILL_DIR}/scripts/cheese-factory.pyz pr_plan_to_branches — converts pr-plan.yaml to branch-creation commands for Phase 7.

Rules

• Sub-agents are full peers, not diminutive workers. Do not downgrade the model, do not narrow subagent_type, do not restrict tools or MCP access.
• The chain is fixed at eight phases. Do not invent extra phases or skip phases (except via --resume).
• Read each phase's handoff slug after the sub-agent returns. Do not infer success from the sub-agent's last line — read the file.
• Surface halts verbatim. Do not paraphrase, do not soften, do not "retry" a halted phase silently.
• Never invoke /gh directly without confirming via the user-approved permission manifest from Phase 0.
• Apply the shared voice kernel (lives at skills/age/references/voice.md in this repo): lead the final report with what happened, flag residual risk as certain | speculating | don't know, do not manufacture follow-ups.