All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Migration Guide: The /workflows:upgrade command reads this file to understand how to migrate projects between versions. Each version's Migration section contains the steps the upgrade orchestrator will follow.
- Personal/shared namespace collaboration model
- Personal workspace:
thoughts/{username}/NNNN-description/ - Shared workspace:
thoughts/shared/NNNN-description/
- Personal workspace:
- Changelog tracking system (
changelog.mdper feature) - Milestone grouping in implementation plans
- Agent orchestration for context window management (60% token reduction)
- New skills:
determine-feature-slug,share-docs,update-changelog,spawn-implementation-agents,upgrade-plugin - New agent:
test-writerfor isolated test generation - New templates:
changelog-document.md - New command:
/workflows:shareto promote personal docs to shared namespace - Project-level version tracking:
thoughts/.version(per-project migration state)
- Document-writing skills now create documents in personal namespace by default
- Commands support personal, shared, and legacy directory structures
- Plan template includes milestone sections and token estimates
- Implement command uses agent orchestration workflow
- Research/plan templates include namespace and sharing metadata
- thoughts-locator/thoughts-analyzer agents search across namespaces
- All user prompts now use selection interface (AskUserQuestion) instead of text input
To upgrade from v1.2.0 to v1.3.0:
-
Run
/workflows:upgrade(detects v1.2.0 → v1.3.0 automatically) -
Claude will analyze your
thoughts/shared/directory:- Count research and plan documents
- Identify related documents by topic/date
- Propose groupings (e.g., "auth research + auth plan → 0001-authentication")
-
Review proposed groupings:
- Accept suggested groupings
- Modify feature names if desired
- Decide on standalone vs grouped features
-
Claude migrates documents to shared namespace:
- Create
thoughts/shared/NNNN-description/directories - Copy documents from legacy locations
- Update cross-references to point to new paths
- Documents remain unchanged otherwise
- Create
-
Choose cleanup option:
- Delete original files from legacy locations (recommended)
- Keep original files as reference (optional)
-
Verify migration:
- Check new
thoughts/shared/NNNN-*/directories - Test commands with new paths
- Check new
Version detection:
- Check
thoughts/.versionfile (created by v1.3.0+) - If missing, detect from structure:
- v1.2.0/v1.2.2: Only
thoughts/shared/research/andthoughts/shared/plans/exist - v1.3.0+:
thoughts/shared/NNNN-*/orthoughts/{username}/NNNN-*/directories exist
- v1.2.0/v1.2.2: Only
New workflow after upgrade:
- Create new docs in personal namespace:
thoughts/{username}/NNNN-*/ - Share to team: Use
/share-docsto copy tothoughts/shared/NNNN-*/ - Migrated docs go directly to shared (they're already team documents)
Breaking changes: None - backward compatible
- Verification section from PR description template
- Extracted PR description template to
templates/pr-description.md - Extracted commit message template to
templates/commit-message.md
write-pr-descriptionskill now references template filewrite-commit-messageskill now references template file