Crystallize
QuantumAgent — Collapse one cosmos from superposition into a concrete deliverable. Merge its branch, generate a wavefunction-collapse report, and preserve other cosmos for further exploration.From its SKILL.md
npx -y skills add hyuniiiv/quantum-agent --skill crystallizeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 7 commands, including `git rev-parse --show-toplevel` and 6 more.
SKILL.md
4.9 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
cosmos:crystallize
Collapse a specific cosmos from superposition into a concrete result. Other cosmos remain in superposition — they are NOT affected.
This is the wave function collapse: you've observed long enough, now you choose one reality.
Trigger
/cosmos crystallize <cosmos_id>
Example: /cosmos crystallize alpha
Execution Steps
Step 1 — Detect repo root
git rev-parse --show-toplevel
Store as <repo_root>.
Step 2 — Read insights
Read <repo_root>/.quantum/<cosmos_id>/insights.jsonl.
Parse each line as JSON. Each entry has a type field — see cosmos:spawn
for the type vocabulary. Treat missing type as discovery; treat legacy
[TUNNEL]/[JUMP] content prefixes as the corresponding type.
If the file is empty or missing:
❌ cosmos:<cosmos_id> has no insights yet.
Run /cosmos spawn first, or wait for agents to complete.
Then stop.
Step 3 — Summarize worktree branch state
git -C <repo_root>/cosmos/<cosmos_id> log --oneline -10
git -C <repo_root>/cosmos/<cosmos_id> diff HEAD --stat
git -C <repo_root>/cosmos/<cosmos_id> status --short
Show:
- Current branch name
- Last 10 commits
- Changed/uncommitted files
If the worktree no longer exists (e.g., after /cosmos stop), skip this step
and proceed using only the insights file.
Step 4 — Crystallization report
From the insights, identify and summarize (group by type):
- Core decisions — all
type: "decision"entries. What architectural choices were made? - Trade-offs rejected — derive from decisions: what alternatives were considered and why?
- Resonance adopted — all
type: "resonance"entries. Which insights came from other cosmos via entanglement? - Quantum Tunneling — all
type: "tunnel"entries. What constraint was assumed, what bypass was found. - Quantum Jumps — all
type: "jump"entries. What single entanglement read caused the discontinuous shift, and what changed. - Unresolved blockers — any
type: "blocker"without a follow-uptype: "decision"ordiscoveryresolving them. List or confirm "(none)". - Final answer — drawn from
type: "complete"and accumulated decisions. What is this cosmos's solution to the goal?
Present as:
💎 cosmos:<cosmos_id> — Crystallization
════════════════════════════════════════
Strategy: <strategy>
Insights: <N>
Branch: cosmos/<cosmos_id>
Core Decisions:
1. <decision>
2. <decision>
Trade-offs Rejected:
- <option> → rejected because <reason>
Resonance Adopted (from other cosmos):
- <insight adopted via entanglement, or "none">
Quantum Tunneling:
- [TUNNEL] <bypassed constraint and how, or "none">
Quantum Jumps:
- [JUMP] <what changed discontinuously and why, or "none">
Final Answer:
<summary of what was built and why>
Step 5 — Schrödinger check before merge
Before offering to merge, prompt the user:
🐱 Schrödinger's Cat collapses on crystallization — quality is now definite, not potential.
Have you run your test suite against cosmos/<cosmos_id>?
- yes, tests pass — proceed to merge
- yes, tests failed — do not merge; fix in the cosmos branch, then re-crystallize
- no, not yet — run tests first; come back when ready
Wait for user response.
- "yes, tests pass" → continue to Step 6
- "yes, tests failed" → stop; output:
❌ Do not merge a failing cosmos. Fix the issues in cosmos/<cosmos_id>, then run /cosmos crystallize <cosmos_id> again. - "no, not yet" → stop; output:
Run your tests first. Re-run /cosmos crystallize <cosmos_id> when ready.
Step 6 — Offer merge
Ask the user:
Merge
cosmos/<cosmos_id>into main?
- yes —
git merge cosmos/<cosmos_id> --no-ff- no — keep the branch for later
Wait for user response.
If yes:
Detect the default branch:
git symbolic-ref --short HEAD
Switch to main/master if not already on it, then:
git merge cosmos/<cosmos_id> --no-ff -m "feat: crystallize cosmos/<cosmos_id>"
Then record the collapse in quantum memory:
echo '{"type":"crystallize","content":"Cosmos <cosmos_id> collapsed and merged into main.","ts":"<ISO timestamp>"}' \
>> <repo_root>/.quantum/<cosmos_id>/insights.jsonl
Output: ✅ Merged cosmos/<cosmos_id> into main.
If no:
Output: Branch cosmos/<cosmos_id> preserved. Run /cosmos crystallize <cosmos_id> again to merge later.
Note: /cosmos observe is non-destructive — it reads without collapsing the superposition.
/cosmos crystallize is the measurement that collapses one cosmos into a definite result.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.