Releases: ChriRas/craft
Releases · ChriRas/craft
Release list
CRAFT v1.4.0 — Blocked-Slice Lifecycle, Checkable Phase Graph & Docs Site
Epic-002 (Blocked-Slice Lifecycle), the checkable phase-transition graph, read-only context sources, and the public documentation site.
Added
- Blocked-slice lifecycle (epic-002, slices 023–026) —
/craft:blockrecords a first-classblockedstate with a blocker taxonomy, aBlocked-statusresume token and a structured## Blockersection;/craft:unblockclears it via the resume / re-plan / abort fork;/craft:commitauto-resurfacesprerequisite-workdependents when their prerequisite lands;/craft:primeand/craft:statussurface blocked slices with blocker + orphan detection; theslice-builderagent classifies out-of-scope blockers autonomously and pauses with a.craft/handoff.mdinstead of growing the slice. - Protected-
mainsequential-epic landing (slice-021) — sequential epics land each slice through the PR + GitHub-approval workflow ("approve ≠ merge"). - Grouped
/craft:statusoverview (slice-022) — phase names, progress bars, handoff markers, stale partition. - Profile-configurable
Co-Authored-Bytrailer (slice-027). - Ensure-primed gate (slice-028) — context-dependent commands auto-run
/craft:primewhen the session marker is missing. - Read-only context sources (F1, slice-029) — declared "connected projects" and the in-repo
research/folder are readable but write-blocked via a PreToolUse guard; ships a self-contained test harness. - Phase-transition graph + marker contract (slice-031) — the status graph is declared once in
skills/workflow/SKILL.md; status writes/reads/delegations carry machine-readablecraft:writes/craft:reads/craft:delegatesmarkers;scripts/test-workflow-status-graph.shasserts graph closure under both Phase-7 configurations, marker↔table agreement in both directions, and/craft:continuerouting. - Documentation site —
docs/ships a self-contained bilingual (EN/DE) GitHub-Pages page in terminal aesthetic with automatic light/dark and SVG diagrams of the 9-phase loop, the status graph with every branch-off, and the three execution modes — plus a regeneration skill and thescripts/test-docs-site.shstaleness harness.
Fixed
- Phase 8 unreachable when Phase 7 is dropped (B1, slice-031) —
/craft:recapnow writesStatus: reviewingdirectly under the phase7-dropped configuration; previously such slices stalled atStatus: reviewand Commit was never gated. - Read-only guard path normalization (slice-030) — traversal bypass (
commands/../research/x) and false-deny (research/../commands/x) closed; guard↔helper normalizer agreement asserted against the real function.
Changed
rules.md/intent.mdpromote the slice-031 lessons: "prose is not checkable — markers are" and "a rule is never described twice."
Full changelog: https://github.com/ChriRas/craft/blob/main/CHANGELOG.md
CRAFT v1.3.0 — Autonomy Profiles
Epic-001 (Autonomy Profiles) plus the in-place / sequential execution and protected-main slices.
Added
- Portable CRAFT profile format (slice-015) — a new
.claude/project/craft-profile.mdcarrying autonomy, language, commit/merge, and per-agent model settings in one portable file, with named presets and sensible defaults./craft:primedetects, validates, and reports the active profile. - Guided onboarding profile wizard + read-only permission allowlist (slice-017) —
/craft:onboardwalks the user through profile creation and seeds a tiered read-only permission allowlist in.claude/settings.local.json, cutting per-command permission prompts on common read-only tools. - In-place autonomous execution mode +
/craft:release(slice-018) —/craft:executegainsMode: in-place, building a slice on a branch in the main checkout with no commits and halting before Phase 5 so the raw diff can be reviewed in the IDE. The new/craft:releasecommand is the human "approve-to-proceed" gesture that resumes the slice into Phase 5. - Profile-driven protected-
mainPR merge gate (slice-019) —/craft:commitrunsgh pr mergeitself, but only after a real human GitHub PR approval (never--admin). "Approve ≠ merge": the human approves, the system merges. - Sequential epic mode (slice-020) —
/craft:executegainsEpic Mode: sequential, running an epic's slices one after another through the direct workflow instead of parallel worktrees;/craft:commitgains status-aware A1 handling and an in-place-finalize path.
Changed
- Language and per-agent model settings now live in
craft-profile.md(slice-016) — sourced by/craft:prime,/craft:commit,/craft:build, and/craft:review. The## Operational Languageand## Agent Model Overridesblocks were removed fromrules.md. Migration: projects that kept language or model-override settings inrules.mdshould move them into.claude/project/craft-profile.md— run/craft:onboardto generate one and migrate automatically. intent.mdpromotes "approve ≠ merge on protectedmain" to a headline architectural decision.
Fixed
/craft:commitawaiting-release recovery now points at/craft:release(it referenced a stale recovery path).
Full changelog: https://github.com/ChriRas/craft/blob/v1.3.0/CHANGELOG.md
CRAFT v1.2.0 — Worktree Trust
Added
- Worktree trust via
additionalDirectories(slice-014) —/craft:executenow resolves the base directory of the configuredWorktree path patternand idempotently records it inpermissions.additionalDirectoriesof.claude/settings.local.jsonbefore creating any worktree. This stops the per-path permission prompts that previously stalled autonomous runs (worktrees live outside the project root, which Claude Code does not trust by default). Shipsscripts/ensure-worktree-trust.sh, which derives the base path platform-neutrally, merges without overwriting existing permissions, creates + gitignores the settings file when missing, and verifies the result is valid JSON.
Changed
## Worktree Settingsin therules.mdtemplate (and this repo's ownrules.md) documents that/craft:executemaintains the worktree base directory inpermissions.additionalDirectories.
Note: this GitHub release was created retroactively; the v1.2.0 tag shipped 2026-06-07.
CRAFT v1.1.0 — Durable Capture
Minor release. Adds Durable Capture — a named CRAFT methodology principle that planning/design output is written to a durable artifact in the same turn it is produced. Chat is not storage.
Added
- Durable Capture (slice-013) — named principle in the workflow Knowledge Model: context is ephemeral (cleared on
/clear, compaction, or session end), so any analysis, decision, scenario, domain model, or proposal of lasting value produced during planning / design must be captured the same turn. Ships a routing table mapping each kind of output to its home, plus a worked example. .claude/project/design/knowledge home — canonical, on-demand directory for cross-cutting design knowledge (domain model, scenario catalogs, matrices) that is neither why (intent) nor how (rules). Not loaded on/craft:prime, so it costs no session-context budget. Wired into/craft:onboard(greenfield + migration) and theCLAUDE.mdindex template.- Closing-capture enforcement —
/craft:plan(Procedure step 9 + Post-Assertion P5) and/craft:epic(step 6 + P5) sweep the planning dialog and route material insight to its durable home before finishing: "Do not end a planning turn leaving material insight only in chat."
Changed
skills/senior-developer/SKILL.mdworkflow gates cross-reference Durable Capture, so the principle applies session-wide beyond the two planning commands.intent.mdrecords Durable Capture as a headline architectural decision.
Full changelog: https://github.com/ChriRas/craft/blob/main/CHANGELOG.md