spec-kitty-cli 0.7.0__tar.gz → 0.9.0__tar.gz

{spec_kitty_cli-0.7.0 → spec_kitty_cli-0.9.0}/.kittify/missions/software-dev/command-templates/plan.md

@@ -84,7 +84,9 @@ Planning requirements (scale to complexity):
    - Phase 1: Update agent context by running the agent script
    - Re-evaluate Constitution Check post-design, asking the user to resolve new gaps before proceeding
 
-5. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
+5. **STOP and report**: This command ends after Phase 1 planning. Report branch, IMPL_PLAN path, and generated artifacts.
+
+   **⚠️ CRITICAL: DO NOT proceed to task generation!** The user must explicitly run `/spec-kitty.tasks` to generate work packages. Your job is COMPLETE after reporting the planning artifacts.
 
 ## Phases
 
@@ -137,3 +139,28 @@ Planning requirements (scale to complexity):
 
 - Use absolute paths
 - ERROR on gate failures or unresolved clarifications
+
+---
+
+## ⛔ MANDATORY STOP POINT
+
+**This command is COMPLETE after generating planning artifacts.**
+
+After reporting:
+- `plan.md` path
+- `research.md` path (if generated)
+- `data-model.md` path (if generated)
+- `contracts/` contents (if generated)
+- Agent context file updated
+
+**YOU MUST STOP HERE.**
+
+Do NOT:
+- ❌ Generate `tasks.md`
+- ❌ Create work package (WP) files
+- ❌ Create `tasks/` subdirectories
+- ❌ Proceed to implementation
+
+The user will run `/spec-kitty.tasks` when they are ready to generate work packages.
+
+**Next suggested command**: `/spec-kitty.tasks` (user must invoke this explicitly)

{spec_kitty_cli-0.7.0 → spec_kitty_cli-0.9.0}/.kittify/missions/software-dev/command-templates/specify.md

@@ -40,6 +40,42 @@ Discovery requirements (scale to feature complexity):
 3. When you have sufficient context for the feature's scope, paraphrase into an **Intent Summary** and confirm. For trivial features, this can be very brief.
 4. If user explicitly asks to skip questions or says "just testing", acknowledge and proceed with minimal discovery.
 
+## Mission Selection
+
+After completing discovery and confirming the Intent Summary, determine the appropriate mission for this feature.
+
+### Available Missions
+
+- **software-dev**: For building software features, APIs, CLI tools, applications
+  - Phases: research → design → implement → test → review
+  - Best for: code changes, new features, bug fixes, refactoring
+
+- **research**: For investigations, literature reviews, technical analysis
+  - Phases: question → methodology → gather → analyze → synthesize → publish
+  - Best for: feasibility studies, market research, technology evaluation
+
+### Mission Inference
+
+1. **Analyze the feature description** to identify the primary goal:
+   - Building, coding, implementing, creating software → **software-dev**
+   - Researching, investigating, analyzing, evaluating → **research**
+
+2. **Check for explicit mission requests** in the user's description:
+   - If user mentions "research project", "investigation", "analysis" → use research
+   - If user mentions "build", "implement", "create feature" → use software-dev
+
+3. **Confirm with user** (unless explicit):
+   > "Based on your description, this sounds like a **[software-dev/research]** project.
+   > I'll use the **[mission name]** mission. Does that work for you?"
+
+4. **Handle user response**:
+   - If confirmed: proceed with selected mission
+   - If user wants different mission: use their choice
+
+5. **Handle --mission flag**: If the user provides `--mission <key>` in their command, skip inference and use the specified mission directly.
+
+Store the final mission selection to pass to the script via `--mission "<selected-mission>"`.
+
 ## Outline
 
 ### 0. Generate a Friendly Feature Title
@@ -60,13 +96,15 @@ Given that feature description, do this:
    - Only proceed once every discovery question has an explicit answer and the user has acknowledged the Intent Summary.
    - Empty invocation rule: stay in interview mode until you can restate the agreed-upon feature description. Do **not** call `{SCRIPT}` while the description is missing or provisional.
 
-2. When discovery is complete and the intent summary **and title** are confirmed, run the script `{SCRIPT}` from repo root, inserting `--feature-name "<Friendly Title>"` (replace the quoted text with the confirmed title) immediately before the feature description argument. For example:
+2. When discovery is complete and the intent summary, **title**, and **mission** are confirmed, run the script `{SCRIPT}` from repo root, inserting `--feature-name "<Friendly Title>"` and `--mission "<selected-mission>"` immediately before the feature description argument. For example:
 
-   - **bash/zsh**: `.kittify/scripts/bash/create-new-feature.sh --json --feature-name "Checkout Upsell Flow" "$ARGUMENTS"`
-   - **PowerShell**: `.kittify/scripts/powershell/create-new-feature.ps1 -Json -FeatureName "Checkout Upsell Flow" "$ARGUMENTS"`
+   - **bash/zsh**: `.kittify/scripts/bash/create-new-feature.sh --json --feature-name "Checkout Upsell Flow" --mission "software-dev" "$ARGUMENTS"`
+   - **PowerShell**: `.kittify/scripts/powershell/create-new-feature.ps1 -Json -FeatureName "Checkout Upsell Flow" -Mission "software-dev" "$ARGUMENTS"`
 
    Parse its JSON output for `BRANCH_NAME`, `SPEC_FILE`, `FEATURE_NUM`, and `FRIENDLY_NAME`. All file paths must be absolute.
 
+   **Note**: The `--mission` flag writes the mission to the feature's `meta.json`, which downstream commands will read to use the correct templates.
+
    **IMPORTANT** You must only ever run this script once. The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for.
 3. Load `templates/spec-template.md` to understand required sections.
 

{spec_kitty_cli-0.7.0 → spec_kitty_cli-0.9.0}/.kittify/missions/software-dev/templates/task-prompt-template.md

@@ -4,7 +4,7 @@ subtasks:
   - "Txxx"
 title: "Replace with work package title"
 phase: "Phase N - Replace with phase name"
-lane: "planned"  # planned | doing | for_review | done
+lane: "planned"  # DO NOT EDIT - use: tasks_cli.py move <feature> <WP> <lane>
 assignee: ""      # Optional friendly name when in doing/for_review
 agent: ""         # CLI agent identifier (claude, codex, etc.)
 shell_pid: ""     # PID captured when the task moved to the current lane
@@ -102,11 +102,21 @@ Use language identifiers in code blocks: ````python`, ````bash`
 
 ### Updating Metadata When Changing Lanes
 
-1. Capture your shell PID: `echo $$` (or use helper scripts when available).
-2. Update frontmatter (`lane`, `assignee`, `agent`, `shell_pid`).
-3. Add an entry to the **Activity Log** describing the transition.
-4. Run `.kittify/scripts/bash/tasks-move-to-lane.sh <FEATURE> <WPID> <lane>` (PowerShell variant available) to move the prompt, update metadata, and append history in one step.
-5. Commit or stage the change, preserving history.
+**IMPORTANT: Never manually edit the `lane:` field.** The lane is determined by the file's directory location, not the YAML field. Editing the field without moving the file creates a mismatch that breaks the system.
+
+**Always use the move command:**
+```bash
+python3 .kittify/scripts/tasks/tasks_cli.py move <FEATURE> <WPID> <lane> --note "Your note"
+```
+
+This command:
+1. Moves the file to the correct `tasks/<lane>/` directory
+2. Updates the `lane:` field in YAML
+3. Updates `agent` and `shell_pid` metadata
+4. Appends an entry to the Activity Log
+5. Stages the changes for commit
+
+You can add `--agent <name>` and `--shell-pid <pid>` flags for explicit metadata.
 
 ### Optional Phase Subdirectories
 

{spec_kitty_cli-0.7.0 → spec_kitty_cli-0.9.0}/CHANGELOG.md

@@ -9,6 +9,253 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.9.0] - 2025-12-17
+
+### 🎯 Major Release: Frontmatter-Only Lane Management
+
+This release fundamentally changes how Spec Kitty manages work package lanes, eliminating directory-based lane tracking in favor of a simpler, conflict-free frontmatter-only system.
+
+### ⚠️ Breaking Changes
+
+- **Lane system completely redesigned**
+  - Work packages now live in a flat `kitty-specs/<feature>/tasks/` directory
+  - Lane status determined **solely by `lane:` frontmatter field** (no more subdirectories)
+  - Old system: `tasks/planned/WP01.md`, `tasks/doing/WP02.md` ❌
+  - New system: `tasks/WP01.md` with `lane: "planned"` ✅
+
+- **Command renamed: `move` → `update`**
+  - `tasks_cli.py move` command removed
+  - Use `tasks_cli.py update <feature> <WP> <lane>` instead
+  - Semantic clarity: command updates metadata, doesn't move files
+  - Legacy format detection: `update` command refuses to work on old directory-based structure
+
+- **Direct frontmatter editing now supported**
+  - You can now directly edit the `lane:` field in WP frontmatter
+  - Previous "DO NOT EDIT" warnings removed from all templates
+  - System recognizes manual lane changes immediately
+  - No file movement required for lane transitions
+
+### 🆕 Added
+
+- **Migration command: `spec-kitty upgrade`**
+  - Automatically migrates features from directory-based to frontmatter-only format
+  - Preserves all lane assignments during migration
+  - Idempotent: safe to run multiple times
+  - Cleans up empty lane subdirectories after migration
+  - Migrates both main repo and worktree features
+
+- **Legacy format detection**
+  - `is_legacy_format()` function detects old directory-based structure
+  - CLI commands display helpful warnings when legacy format detected
+  - Dashboard shows migration prompt for legacy features
+  - Non-blocking: legacy features remain functional until migrated
+
+- **Enhanced status command**
+  - Better formatted output with lane grouping
+  - Auto-detects feature from branch/worktree when not specified
+  - Shows work packages organized by current lane
+  - Works with both legacy and new formats
+
+### 🔧 Changed
+
+- **Work package location logic**
+  - `locate_work_package()` now searches flat `tasks/` directory first
+  - Falls back to legacy subdirectory search for backwards compatibility
+  - Exact WP ID matching (WP04 won't match WP04b)
+
+- **Lane extraction utilities**
+  - New `get_lane_from_frontmatter()` function extracts lane from YAML
+  - Defaults to "planned" when `lane:` field missing
+  - Validates lane values against allowed set
+  - Available in both `task_helpers.py` and `tasks_support.py`
+
+- **Dashboard scanner updates**
+  - Reads lane from frontmatter instead of directory location
+  - Displays legacy format warnings
+  - Works seamlessly with both formats during transition
+
+- **Activity log behavior**
+  - Lane transitions still append activity log entries
+  - Captures agent, shell PID, and timestamp
+  - No file movement logged (because no movement occurs)
+
+### 📚 Documentation
+
+- **Updated all templates**
+  - `.kittify/templates/task-prompt-template.md` - Removed "DO NOT EDIT" warnings
+  - `.kittify/templates/tasks-template.md` - Updated for flat structure
+  - `.kittify/templates/AGENTS.md` - New lane management instructions
+  - `tasks/README.md` - Rewritten for flat directory layout
+
+- **Updated mission templates**
+  - All mission-specific templates updated (software-dev, research)
+  - Command templates updated (`implement.md`, `review.md`, `merge.md`)
+  - Examples updated to show new workflow
+
+- **Updated main documentation**
+  - `README.md` - Updated quick start examples
+  - `docs/quickstart.md` - New lane management workflow
+  - `docs/multi-agent-orchestration.md` - Updated collaboration examples
+  - All `examples/` updated with new commands
+
+### 🧪 Testing
+
+- 286 tests passing (0 failures)
+- New tests for frontmatter-only lane system
+- Legacy format detection tests
+- Migration command tests
+- Dual-format compatibility tests
+
+### 🚀 Migration Guide
+
+**For existing projects:**
+
+1. **Back up your work** (commit changes, push to remote)
+2. **Run migration**: `spec-kitty upgrade`
+3. **Verify**: `spec-kitty status --feature <your-feature>`
+4. **Update workflows**: Replace `move` with `update` in scripts/docs
+
+**Key benefits of upgrading:**
+
+- ✅ No file conflicts during lane changes (especially in worktrees)
+- ✅ Direct editing of `lane:` field supported
+- ✅ Better multi-agent compatibility
+- ✅ Simpler mental model (one directory, not four)
+- ✅ Fewer git operations per lane change
+
+**Legacy format still works** - You can continue using old directory structure until ready to migrate. All commands detect format automatically.
+
+### 🐛 Fixed
+
+- File conflicts during simultaneous lane changes by multiple agents
+- Git staging issues with lane transitions
+- Race conditions in worktree-based parallel development
+- Lane mismatch validation errors (no longer possible with frontmatter-only)
+
+### 🔗 Related
+
+- Feature implementation: `007-frontmatter-only-lane`
+- All 6 work packages completed and reviewed
+- Comprehensive test coverage added
+
+---
+
+## [0.8.2] - 2025-12-17
+
+### Added
+
+- **Task lane management documentation** - Added clear instructions to AGENTS.md and task templates warning agents never to manually edit the `lane:` YAML field
+  - Lane is determined by directory location, not YAML field
+  - Editing `lane:` without moving the file creates a mismatch that breaks the system
+  - All templates now include YAML comment: `# DO NOT EDIT - use: tasks_cli.py move`
+  - Added "Task Lane Management Rule" section to project AGENTS.md
+
+## [0.8.1] - 2025-12-17
+
+### Fixed
+
+- **Work package move race conditions** - Multiple agents can now work on different WPs simultaneously without blocking each other
+  - Conflict detection now only blocks on changes to the same WP, not unrelated WP files
+  - Agents working on WP05 no longer block moves of WP04
+
+- **Exact WP ID matching** - `WP04` no longer incorrectly matches `WP04b`
+  - Changed from prefix matching to exact boundary matching
+  - Pattern now requires WP ID to be followed by `-`, `_`, `.`, or end of filename
+
+- **Cleanup no longer leaves staged deletions** - Stale copy cleanup uses filesystem delete instead of `git rm`
+  - Prevents orphaned staged deletions from blocking subsequent operations
+  - Automatically unstages any previously staged changes to cleaned files
+
+## [0.8.0] - 2025-12-15
+
+### Breaking Changes
+
+- **Mission system refactored to per-feature model**
+  - Missions are now selected during `/spec-kitty.specify` instead of `spec-kitty init`
+  - Each feature stores its mission in `meta.json` (field: `"mission": "software-dev"`)
+  - `.kittify/active-mission` symlink/file is no longer used
+  - Run `spec-kitty upgrade` to clean up existing projects
+
+- **Removed commands**
+  - `spec-kitty mission switch` - Missions are now per-feature, not per-project
+  - Running this command now shows a helpful error message explaining the new workflow
+
+- **Removed flags**
+  - `--mission` flag from `spec-kitty init` - Use `/spec-kitty.specify` instead
+  - Flag is hidden but shows deprecation warning if used
+
+### Added
+
+- **Mission inference during `/spec-kitty.specify`** - LLM analyzes feature description and suggests appropriate mission:
+  - "Build a REST API" → suggests `software-dev`
+  - "Research best practices" → suggests `research`
+  - User confirms or overrides the suggestion
+  - Explicit `--mission` flag bypasses inference
+
+- **Per-feature mission storage** - Selected mission stored in feature's `meta.json`:
+  - All downstream commands read mission from feature context
+  - Legacy features without mission field default to `software-dev`
+
+- **Mission discovery** - New `discover_missions()` function returns all available missions with source indicators
+
+- **Updated `spec-kitty mission list`** - Shows source column (project/built-in) for each mission
+
+- **Migration for v0.8.0** - `spec-kitty upgrade` removes obsolete `.kittify/active-mission` file
+
+- **AGENTS.md worktree fix** - New worktrees get AGENTS.md symlink, and `spec-kitty upgrade` fixes existing worktrees
+
+### Changed
+
+- All downstream commands (`/spec-kitty.plan`, `/spec-kitty.tasks`, `/spec-kitty.implement`, `/spec-kitty.review`, `/spec-kitty.accept`) now read mission from feature's `meta.json`
+- `create-new-feature.sh` accepts `--mission <key>` parameter to set mission in meta.json
+- Common bash/PowerShell scripts updated to resolve mission from feature directory
+- `spec-kitty mission current` shows current default mission (for informational purposes)
+- Dashboard template now includes dynamic AGENTS.md path discovery instructions
+
+### Deprecated
+
+- `set_active_mission()` function - Shows deprecation warning, will be removed in future version
+
+### Migration Guide
+
+1. Run `spec-kitty upgrade` to remove `.kittify/active-mission`
+2. Existing features without `mission` field will use `software-dev` by default
+3. New features will have mission set during `/spec-kitty.specify`
+
+## [0.7.4] - 2025-12-14
+
+### Added
+
+- **Script Update Migration** – `spec-kitty upgrade` now updates project scripts:
+  - Copies latest `create-new-feature.sh` from package to project
+  - Fixes worktree feature numbering bug in existing projects
+  - Previously, projects kept old scripts from when they were initialized
+
+## [0.7.3] - 2025-12-14
+
+### Fixed
+
+- **Duplicate Feature Numbers with Worktrees** – Script now scans both `kitty-specs/` AND `.worktrees/` for existing feature numbers:
+  - Previously only scanned `kitty-specs/` which was empty when using worktrees
+  - This caused new features to get `001` even when `001-*` worktree already existed
+  - Now correctly finds highest number across both locations
+
+## [0.7.2] - 2025-12-14
+
+### Fixed
+
+- **Duplicate Slash Commands in Worktrees (Corrected)** – Fixed the fix from v0.7.1:
+  - v0.7.1 incorrectly removed commands from main repo (broke `/` commands there)
+  - v0.7.2 removes commands from **worktrees** instead (they inherit from main repo)
+  - Claude Code traverses UP, so worktrees find main repo's `.claude/commands/`
+  - Main repo keeps commands, worktrees don't need their own copy
+
+## [0.7.1] - 2025-12-14 [YANKED]
+
+### Fixed
+
+- ~~Duplicate Slash Commands in Worktrees~~ – **Incorrect fix, replaced by v0.7.2**
+
 ## [0.7.0] - 2025-12-14
 
 ### Added

{spec_kitty_cli-0.7.0 → spec_kitty_cli-0.9.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spec-kitty-cli
-Version: 0.7.0
+Version: 0.9.0
 Summary: Spec Kitty CLI, a community fork of GitHub's Spec Kit for bootstrapping Spec-Driven Development (SDD) projects.
 Project-URL: Repository, https://github.com/spec-kitty/spec-kit
 Project-URL: Issues, https://github.com/spec-kitty/spec-kit/issues
@@ -58,7 +58,7 @@ Description-Content-Type: text/markdown
 
 <div align="center">
     <img src="https://github.com/Priivacy-ai/spec-kitty/raw/main/media/logo_small.webp" alt="Spec Kitty Logo"/>
-    <h1>🐱 Spec Kitty</h1>
+    <h1>Spec Kitty</h1>
     <h3><em>Real-Time AI Development Dashboard for Spec-Driven Multi-Agent Workflows</em></h3>
 </div>
 
@@ -89,6 +89,10 @@ Description-Content-Type: text/markdown
 
 > **Note:** Spec Kitty is a community-maintained fork of GitHub's [Spec Kit](https://github.com/github/spec-kit). We retain the original attribution per the Spec Kit license while evolving the toolkit under the Spec Kitty banner.
 
+> **🎉 Version 0.9.0 Released - Frontmatter-Only Lane Management**
+> Work packages now use a flat `tasks/` directory with lane status in frontmatter (no more lane subdirectories).
+> **Existing projects:** Run `spec-kitty upgrade` to migrate. Legacy format still works. [See CHANGELOG](CHANGELOG.md#090---2025-12-17) for full details.
+
 <details>
 <summary><b>🔄 What's Different from GitHub Spec Kit?</b></summary>
 

{spec_kitty_cli-0.7.0 → spec_kitty_cli-0.9.0}/README.md

@@ -1,6 +1,6 @@
 <div align="center">
     <img src="https://github.com/Priivacy-ai/spec-kitty/raw/main/media/logo_small.webp" alt="Spec Kitty Logo"/>
-    <h1>🐱 Spec Kitty</h1>
+    <h1>Spec Kitty</h1>
     <h3><em>Real-Time AI Development Dashboard for Spec-Driven Multi-Agent Workflows</em></h3>
 </div>
 
@@ -31,6 +31,10 @@
 
 > **Note:** Spec Kitty is a community-maintained fork of GitHub's [Spec Kit](https://github.com/github/spec-kit). We retain the original attribution per the Spec Kit license while evolving the toolkit under the Spec Kitty banner.
 
+> **🎉 Version 0.9.0 Released - Frontmatter-Only Lane Management**
+> Work packages now use a flat `tasks/` directory with lane status in frontmatter (no more lane subdirectories).
+> **Existing projects:** Run `spec-kitty upgrade` to migrate. Legacy format still works. [See CHANGELOG](CHANGELOG.md#090---2025-12-17) for full details.
+
 <details>
 <summary><b>🔄 What's Different from GitHub Spec Kit?</b></summary>
 

spec_kitty_cli-0.9.0/kitty-specs/007-frontmatter-only-lane/tasks/README.md

@@ -0,0 +1,71 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files for the feature.
+
+## Directory Structure
+
+All WP files live in this flat directory:
+```
+tasks/
+├── WP01-setup.md
+├── WP02-implement.md
+├── WP03-test.md
+└── README.md
+```
+
+## Lane Management
+
+Each WP file has a `lane:` field in its YAML frontmatter:
+- `planned` - Not yet started
+- `doing` - In progress
+- `for_review` - Ready for review
+- `done` - Complete
+
+To change a WP's lane:
+```bash
+python3 .kittify/scripts/tasks/tasks_cli.py update <feature> <WP> <lane>
+```
+
+Or edit the `lane:` field directly in the WP file.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+subtasks:
+  - "T001"
+  - "T002"
+title: "Work Package Title"
+phase: "Phase 1 - Setup"
+lane: "planned"  # Edit directly or use: tasks_cli.py update
+assignee: ""
+agent: ""
+shell_pid: ""
+review_status: ""
+reviewed_by: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    lane: "planned"
+    agent: "system"
+    shell_pid: ""
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 - Work Package Title
+
+[Content follows...]
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md` (no extra hyphens in WP number)
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`
+
+## Viewing Status
+
+```bash
+python3 .kittify/scripts/tasks/tasks_cli.py status <feature>
+```

{spec_kitty_cli-0.7.0 → spec_kitty_cli-0.9.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "spec-kitty-cli"
-version = "0.7.0"
+version = "0.9.0"
 description = "Spec Kitty CLI, a community fork of GitHub's Spec Kit for bootstrapping Spec-Driven Development (SDD) projects."
 readme = "README.md"
 license = { file = "LICENSE" }