🚨 BREAKING CHANGES - Workspace Model Changed (Feature 010)
Old (0.10.x): One worktree per feature
/spec-kitty.specifycreated.worktrees/###-feature/- All WPs worked in same worktree
- Sequential development (one agent at a time)
New (0.11.0): One worktree per work package
- Planning commands (specify, plan, tasks) work in main repository (NO worktree created)
spec-kitty implement WP##creates.worktrees/###-feature-WP##/- Each WP has isolated worktree with dedicated branch
- Enables parallel multi-agent development
⚠️ Migration Required
You MUST complete or delete all in-progress features before upgrading to 0.11.0.
Check for legacy worktrees:
spec-kitty list-legacy-featuresSee docs/upgrading-to-0-11-0.md for complete migration guide.
🔒 Security (IMPORTANT) - Feature 011
- Comprehensive adversarial review framework
- Expanded review template from 3 bullets (109 lines) to 12 scrutiny categories (505 lines)
- Security scrutiny now mandatory: 10 detailed security subsections
- Mandatory verification: 7 security grep commands must be run on EVERY review
- Automatic rejection if any security check fails
- Impact: All future features will have security-first reviews
✨ Added
Workspace-per-WP Features (010):
- New command:
spec-kitty implement WP## [--base WPXX]- Create workspace for work package--baseflag branches from another WP's branch (for dependencies)- Automatically moves WP from
planned→doinglane
- New command:
spec-kitty agent feature finalize-tasks- Finalize WP generation- Parses dependencies from tasks.md
- Generates
dependencies: []field in WP frontmatter - Validates dependency graph (cycle detection, invalid references)
- Dependency tracking: WP frontmatter includes
dependencies: []field - Dependency graph utilities:
src/specify_cli/core/dependency_graph.py - Review warnings: Alert when dependent WPs need rebase
Constitution Features (011):
- Interactive constitution command (Phase-based discovery)
- 4-phase discovery workflow (Technical, Quality, Tribal Knowledge, Governance)
- Two paths: Minimal (Phase 1 only) or Comprehensive (all phases)
- Skip options for each phase
- Truly optional - all commands work without constitution
♻️ Refactored - Feature 011
-
Template source relocation (Safe dogfooding - Critical)
- Moved ALL template sources from
.kittify/tosrc/specify_cli/ - Updated template manager to load from package resources
- Removed
.kittify/*force-includes frompyproject.toml - Impact: Developers can now safely dogfood without packaging risk
- Moved ALL template sources from
-
Mission-specific constitutions removed
- Single project-level constitution model (
.kittify/memory/constitution.md) - Migration removes mission constitutions from user projects
- Single project-level constitution model (
🐛 Fixed - Feature 011
-
Windows dashboard ERR_EMPTY_RESPONSE (#71)
- Replaced POSIX-only signal handling with cross-platform psutil
- Added
psutil>=5.9.0dependency - Dashboard now works on Windows 10/11
-
Upgrade migration failures (#70)
- Fixed multiple migrations to handle missing files gracefully
- All migrations now idempotent
- Upgrade path from 0.6.4 → 0.10.12 completes without intervention
🐛 Fixed - Feature 012
/spec-kitty.statustemplate instructed agents to run Python code- AI agents cannot execute arbitrary Python - they use CLI tools
- Updated template to use CLI command as primary method
- Python API now documented as alternative for Jupyter/scripts
📖 Documentation - Feature 010
- New docs:
docs/workspace-per-wp.md- Workflow guide with examples - New docs:
docs/upgrading-to-0-11-0.md- Migration instructions
🎯 Why These Changes?
Feature 010 (Workspace-per-WP):
- Enables parallel multi-agent development
- Better isolation per work package
- Explicit dependencies with validation
- Scalability for large features (10+ WPs)
- Foundation for future jujutsu VCS integration
Feature 011 (Constitution & Packaging Safety):
- Safe dogfooding (no packaging contamination)
- Cross-platform dashboard support
- Optional, interactive constitution setup
- Smooth upgrade migrations