Repository navigation
0.4.1 - Release Notes
Summary
Collaboration Framework v1.3.0 — a project-management cleanup release that
moves planning artifacts out of implementation-branch docs/ trees and into a
dedicated planning Git worktree, with project directories named like arcs and
slices.
Planning Worktree Default
The project-management default changed from version-looking directories such as
docs/design-v0.1.0/ to a dedicated orphan planning branch mounted as a Git
worktree.
The new default is:
- Reuse the repository's existing worktree convention when one is present.
- Otherwise use
$PROJECT_DIR/.worktrees. - Use a
planningbranch and.worktrees/planningworktree by default. - Keep the planning branch orphaned, with no inherited implementation files.
- Store project plans under
projectNN-<slug>/.
This makes the planning tree the official source of truth for project plans,
arc plans, slice ledgers, prompts, close reports, and CDC verification, without
mixing those records into product or release documentation.
Project Naming and Metadata
Project directories now follow the same naming pattern as arcs and slices:
projectNN-<slug>, for example project01-vault-split.
Ordering and relationships are no longer inferred from release-looking
directory names. project-plan.md now carries explicit metadata for:
projectstatusdepends-onblocksrelated
This gives humans and LLMs the sortable filesystem shape without encoding
dependency semantics in path names.
Slice Plan Naming
The slice plan-of-record was renamed from slice-doc.md to slice-plan.md, so
all three planning scales now use the same pattern:
project-plan.mdarc-plan.mdslice-plan.md
The old name remains only in version-history notes that explain the rename.
Framework Document Updates
The release updates the collaboration-framework entry point and the two
operational specs that carry the planning/verification mechanics:
SKILL.mdbumped to1.3.0and now routes planning work to the new
planning-worktree default.docs/PROJECT-MANAGEMENT.mdbumped to2.2and now owns the new substrate,
naming rules, metadata fields, confirmation protocol, and related
anti-patterns.docs/AI-ENGINEERING-METHODOLOGY.mdbumped to1.6and now summarizes the
worktree-based planning model rather than the olddocs/design-vX.Y.Ztree.templates/LEDGER-DISCIPLINE.mdbumped to2.1and now uses the
planning-worktree path andslice-plan.mdterminology.
Verification
git diff --checkpassed before the cleanup commit.- Remaining
docs/design-vX.Y.Zanddocs/design-v0.1.0mentions are
historical, explicitly superseded, or anti-pattern examples. - The installed
collaboration-frameworkskill was checked after install and
reportsversion: 1.3.0with the new planning-worktree andslice-plan.md
guidance visible.