Stats
Actions
Tags
From crux
Exports active Crux decisions, rationales, constraints, and goals from current session graph to CLAUDE.md, appending under dedicated sections without duplication.
How this skill is triggered — by the user, by Claude, or both
Slash command
/crux:crux-exportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read the current Crux graph from `.claude/.crux/sessions/` in the project root (find the most recent `.json` file, or the one matching the current session).
Read the current Crux graph from .claude/.crux/sessions/ in the project root (find the most recent .json file, or the one matching the current session).
For each active DECISION atom, append to CLAUDE.md in the project root under a ## Architectural Decisions (Crux) section. Include the full causal chain:
dependsOn links)dependsOn links)Format each as:
Also export any active GOAL atoms in a separate ## Project Goals (Crux) section.
If CLAUDE.md already has these sections, append new items below existing ones. Do not duplicate items already present.
If the graph has no active decisions, inform the user: "No active decisions to export. Crux captures decisions automatically during the session."
After appending, confirm what was exported: "Exported N decision(s) to CLAUDE.md."
npx claudepluginhub akashp1712/claude-marketplace --plugin cruxRecords significant architectural decisions like database choices, frameworks, or core patterns in docs/decisions.md. Activates on major decisions, explicit requests, or proactively at session ends.
Synthesizes Architecture Decision Records from Claude Code session transcripts via multi-agent pipeline. Extracts decisions and writes MADR files to a directory after /define or /do sessions.
Manages persistent progress state, module health, dependency graphs, and ADRs across sessions. Use for workflows needing durable tracking of decisions and status beyond single interactions.