spec-kitty-cli 3.2.0a10__tar.gz → 3.2.0rc2__tar.gz

{spec_kitty_cli-3.2.0a10 → spec_kitty_cli-3.2.0rc2}/.gitignore

@@ -65,6 +65,7 @@ pyproject.local.toml
 .kittify/workspaces/
 .kittify/merge-state.json
 .kittify/.migration-backup/
+kitty-specs/**/.kittify/config.yaml
 kitty-specs/**/.kittify/dossiers/
 
 # Dossier snapshots are mutable derived artifacts; recomputable from dossier source.

{spec_kitty_cli-3.2.0a10 → spec_kitty_cli-3.2.0rc2}/CHANGELOG.md

@@ -17,6 +17,79 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Removed
 
+## [3.2.0rc2] - 2026-05-05
+
+3.2.0rc2 adds the TeamSpace mission-state repair and validation surface needed
+before public TeamSpace import. The repair command is available now; the
+TeamSpace dry-run path requires `spec-kitty-events>=5.0.0` once that contract
+package is published.
+
+### Added
+
+- Added deterministic `doctor mission-state --fix` repair for historical
+  `kitty-specs/` state, including Git safety checks, migration manifests, legacy
+  key cleanup, typed-row quarantine, lane normalization, and production
+  `status.json` rematerialization (#980).
+- Added `doctor mission-state --teamspace-dry-run` to synthesize canonical
+  TeamSpace envelopes in memory and validate them with the 5.0.0 event contract
+  when available (#980).
+- Documented the distributed Git repair workflow for coordinated repository
+  migration before TeamSpace launch (#980).
+- Added `doctor mission-state --include-fixtures` and the packaged
+  mission-state survey fixture pack used by the TeamSpace readiness audit
+  contract (#920, #922, #929).
+- Added an opt-in `TeamSpace Mission-State Readiness` GitHub Actions workflow
+  that runs `doctor mission-state --audit --fail-on teamspace-blocker` and
+  uploads the JSON audit artifact (#920, #934).
+
+### Changed
+
+- Aligned CLI sync emission for `WPStatusChanged` and `MissionClosed` with the
+  canonical TeamSpace event payload shape while keeping launch dry-run gated on
+  the published events contract (#980).
+- `doctor mission-state --audit` JSON reports now expose TeamSpace blocker
+  counts, and `--fail-on teamspace-blocker` gates import/sync readiness
+  without requiring network access (#920, #934).
+
+## [3.2.0rc1] - 2026-05-05
+
+3.2.0rc1 is the first release candidate for the 3.2.0 line. It rolls up the
+workflow stabilization work from the alpha series and the final release
+confidence missions.
+
+### Fixed
+
+- Hardened the mission status, review, and merge surfaces that block reliable
+  implement-review-retrospect loops, including stale review verdict handling,
+  finalized-board routing, canonical review feedback pointers, and first-class
+  retrospective synthesis paths.
+- Fixed task-board progress semantics so done-only counts are no longer paired
+  with unlabeled weighted readiness percentages; JSON status output now exposes
+  explicit progress semantics and weighted readiness fields (#966).
+- Added an installed dependency drift guard for shared packages so release and
+  review evidence fail when the active environment disagrees with `uv.lock` for
+  `spec-kitty-events` or `spec-kitty-tracker` (#848).
+- Addressed final mission-review regressions around machine-facing contract
+  output, sync-control side effects, and the charter golden-path E2E assertion.
+
+### Release Validation
+
+- Closed the stale ruff blocker after `uv run ruff check src tests` passed on
+  current `main` (#869).
+- Re-ran final local release gates from fresh `origin/main`: dependency sync,
+  lock validation, installed shared-package drift guard, ruff, and the
+  contract/architectural/release pytest batch all passed.
+- GitHub Actions on the release candidate base commit passed `CI Quality`,
+  `ci-windows`, and `Protect Main Branch`.
+
+### Known Limitations
+
+- The broad strict mypy gate remains tracked for follow-up in #971 and is not a
+  blocking gate for this release candidate.
+- Hosted sync drain reliability has a known SaaS-sync limitation tracked in
+  #889; do not treat this release candidate as proof of full hosted drain
+  reliability until that issue is fixed.
+
 ## [3.2.0a10] - 2026-05-04
 
 3.2.0a10 is a prerelease that stabilizes the implement-review-retrospect

spec_kitty_cli-3.2.0rc2/PKG-INFO

@@ -0,0 +1,241 @@
+Metadata-Version: 2.4
+Name: spec-kitty-cli
+Version: 3.2.0rc2
+Summary: Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation.
+Project-URL: Repository, https://github.com/Priivacy-ai/spec-kitty
+Project-URL: Issues, https://github.com/Priivacy-ai/spec-kitty/issues
+Project-URL: Documentation, https://docs.spec-kitty.ai/
+Project-URL: Changelog, https://github.com/Priivacy-ai/spec-kitty/blob/main/CHANGELOG.md
+Author: Spec Kitty Contributors
+Maintainer: Spec Kitty Contributors
+License: MIT License
+        
+        Copyright GitHub, Inc.
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+License-File: LICENSE
+Keywords: agentic-development,ai-agents,ai-coding,claude-code,cli,code-generation,feature-specs,git-worktree,kanban,llm-tools,planning,requirements,sdd,spec-driven-development,specification,workflow-automation
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Version Control
+Classifier: Topic :: Software Development :: Version Control :: Git
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: cryptography>=42.0
+Requires-Dist: filelock>=3.13.0
+Requires-Dist: google-re2>=1.1
+Requires-Dist: httpx[socks]>=0.28.1
+Requires-Dist: jsonschema>=4.0
+Requires-Dist: packaging>=23.0
+Requires-Dist: platformdirs>=4.9.2
+Requires-Dist: psutil>=5.9.0
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pygments>=2.20.0
+Requires-Dist: python-ulid>=3.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: readchar>=4.2.1
+Requires-Dist: requests>=2.33.0
+Requires-Dist: rich>=14.3.3
+Requires-Dist: ruamel-yaml>=0.18.0
+Requires-Dist: spec-kitty-events<6.0.0,>=4.0.0
+Requires-Dist: spec-kitty-tracker<0.5,>=0.4
+Requires-Dist: toml>=0.10.2
+Requires-Dist: transitions>=0.9.2
+Requires-Dist: truststore>=0.10.4
+Requires-Dist: typer>=0.24.1
+Requires-Dist: websockets>=12.0
+Provides-Extra: lint
+Requires-Dist: bandit>=1.7.0; extra == 'lint'
+Requires-Dist: cyclonedx-bom>=4.0; extra == 'lint'
+Requires-Dist: mypy>=1.10.0; extra == 'lint'
+Requires-Dist: pip-audit>=2.7.0; extra == 'lint'
+Requires-Dist: ruff>=0.4.0; extra == 'lint'
+Requires-Dist: types-jsonschema>=4.0.0; extra == 'lint'
+Requires-Dist: types-psutil>=5.9.0; extra == 'lint'
+Requires-Dist: types-pyyaml>=6.0; extra == 'lint'
+Requires-Dist: types-requests>=2.33.0; extra == 'lint'
+Requires-Dist: types-toml>=0.10.0; extra == 'lint'
+Provides-Extra: test
+Requires-Dist: build>=1.0.0; extra == 'test'
+Requires-Dist: chardet<6,>=3.0.4; extra == 'test'
+Requires-Dist: diff-cover>=10.0.0; extra == 'test'
+Requires-Dist: mutmut>=3.5.0; extra == 'test'
+Requires-Dist: pytest-asyncio>=0.21.0; extra == 'test'
+Requires-Dist: pytest-cov>=4.1.0; extra == 'test'
+Requires-Dist: pytest-timeout>=2.2.0; extra == 'test'
+Requires-Dist: pytest>=9.0.3; extra == 'test'
+Requires-Dist: pytestarch>=4.0.0; extra == 'test'
+Requires-Dist: respx>=0.21.1; extra == 'test'
+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>
+    <p><strong>Spec-driven development for AI coding agents.</strong></p>
+</div>
+
+Spec Kitty is an open-source CLI for turning product intent into a repeatable agent workflow:
+
+```text
+spec -> plan -> tasks -> next -> review -> accept -> merge
+```
+
+It keeps the important context in your repository, creates work packages that agents can execute, and uses git worktrees so implementation work can happen without constantly switching branches.
+
+[![PyPI version](https://img.shields.io/pypi/v/spec-kitty-cli?style=flat-square&logo=pypi)](https://pypi.org/project/spec-kitty-cli/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-yellow?style=flat-square)](LICENSE)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue?style=flat-square)](https://www.python.org/downloads/)
+
+## Is It For You?
+
+Use Spec Kitty when:
+
+- AI coding sessions are losing requirements, decisions, or acceptance criteria.
+- You want specs, plans, tasks, reviews, and merge state stored in the repo.
+- Multiple agents or developers need clear work package boundaries.
+- You want a local workflow first, with optional hosted tracker and sync integrations later.
+
+It is probably overkill for one-off edits, tiny scripts, or teams that do not use Git.
+
+## What It Provides
+
+| Need | Spec Kitty provides |
+| --- | --- |
+| Start from intent | Guided `specify`, `plan`, and `tasks` workflows |
+| Keep agents aligned | Repository-native mission artifacts under `kitty-specs/` |
+| Split implementation | Work packages with lifecycle lanes such as `planned`, `in_progress`, `for_review`, and `done` |
+| Avoid branch chaos | Isolated git worktrees under `.worktrees/` |
+| See progress | Optional local kanban dashboard with `spec-kitty dashboard` |
+| Integrate agents | Slash commands or skills for common AI coding tools |
+
+## Quick Start
+
+Install the CLI:
+
+```bash
+pip install spec-kitty-cli
+# or
+uv tool install spec-kitty-cli
+```
+
+Create or initialize a project:
+
+```bash
+spec-kitty init my-project --ai claude
+cd my-project
+spec-kitty verify-setup
+```
+
+Replace `claude` with your agent key when needed. Common choices include `codex`, `cursor`, `gemini`, `copilot`, `opencode`, `qwen`, `windsurf`, `kiro`, and `vibe`.
+
+Open your AI coding agent in the project and run the core workflow:
+
+```text
+/spec-kitty.charter
+/spec-kitty.specify Build a small task list app.
+/spec-kitty.plan
+/spec-kitty.tasks
+```
+
+Then let the runtime choose the next action until the mission is ready:
+
+```bash
+spec-kitty next --agent claude --mission <mission-slug>
+```
+
+Review, accept, and merge:
+
+```text
+/spec-kitty.review
+/spec-kitty.accept
+/spec-kitty.merge --push
+```
+
+For the full walkthrough, see [Your First Feature](docs/tutorials/your-first-feature.md).
+
+## Everyday Commands
+
+| Command | Purpose |
+| --- | --- |
+| `spec-kitty init . --ai <agent>` | Add Spec Kitty to the current repo |
+| `spec-kitty verify-setup` | Check local installation and project wiring |
+| `spec-kitty dashboard` | Open the local mission dashboard |
+| `spec-kitty next --agent <agent> --mission <slug>` | Ask Spec Kitty what the agent should do next |
+| `spec-kitty upgrade` | Update an existing project after upgrading the CLI |
+| `spec-kitty --help` | Show available commands |
+
+## Documentation
+
+Start here:
+
+- [Getting Started](docs/tutorials/getting-started.md)
+- [Your First Feature](docs/tutorials/your-first-feature.md)
+- [CLI Command Reference](docs/reference/cli-commands.md)
+- [Slash Commands](docs/reference/slash-commands.md)
+- [Supported Agents](docs/reference/supported-agents.md)
+- [Dashboard Guide](docs/how-to/use-dashboard.md)
+- [Install and Upgrade](docs/how-to/install-and-upgrade.md)
+
+Deeper topics:
+
+- [Spec-Driven Development](docs/explanation/spec-driven-development.md)
+- [Mission System](docs/explanation/mission-system.md)
+- [Git Worktrees](docs/explanation/git-worktrees.md)
+- [Multi-Agent Orchestration](docs/explanation/multi-agent-orchestration.md)
+- [External Orchestrator Runbook](docs/how-to/run-external-orchestrator.md)
+- [Hosted Sync Workspaces](docs/how-to/sync-workspaces.md)
+
+## Development
+
+```bash
+git clone https://github.com/Priivacy-ai/spec-kitty.git
+cd spec-kitty
+pip install -e ".[test]"
+```
+
+When testing templates from a source checkout:
+
+```bash
+export SPEC_KITTY_TEMPLATE_ROOT="$(pwd)"
+spec-kitty init my-project --ai claude
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for contribution guidelines.
+
+## Support
+
+- Open a [GitHub issue](https://github.com/Priivacy-ai/spec-kitty/issues/new) for bugs, feature requests, or questions.
+- See [CHANGELOG.md](CHANGELOG.md) for release notes.
+- See [CONTRIBUTORS.md](CONTRIBUTORS.md) and the [GitHub contributors graph](https://github.com/Priivacy-ai/spec-kitty/graphs/contributors) for contributor credits.
+
+## License
+
+Spec Kitty is released under the [MIT License](LICENSE).

spec_kitty_cli-3.2.0rc2/README.md

@@ -0,0 +1,143 @@
+<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>
+    <p><strong>Spec-driven development for AI coding agents.</strong></p>
+</div>
+
+Spec Kitty is an open-source CLI for turning product intent into a repeatable agent workflow:
+
+```text
+spec -> plan -> tasks -> next -> review -> accept -> merge
+```
+
+It keeps the important context in your repository, creates work packages that agents can execute, and uses git worktrees so implementation work can happen without constantly switching branches.
+
+[![PyPI version](https://img.shields.io/pypi/v/spec-kitty-cli?style=flat-square&logo=pypi)](https://pypi.org/project/spec-kitty-cli/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-yellow?style=flat-square)](LICENSE)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue?style=flat-square)](https://www.python.org/downloads/)
+
+## Is It For You?
+
+Use Spec Kitty when:
+
+- AI coding sessions are losing requirements, decisions, or acceptance criteria.
+- You want specs, plans, tasks, reviews, and merge state stored in the repo.
+- Multiple agents or developers need clear work package boundaries.
+- You want a local workflow first, with optional hosted tracker and sync integrations later.
+
+It is probably overkill for one-off edits, tiny scripts, or teams that do not use Git.
+
+## What It Provides
+
+| Need | Spec Kitty provides |
+| --- | --- |
+| Start from intent | Guided `specify`, `plan`, and `tasks` workflows |
+| Keep agents aligned | Repository-native mission artifacts under `kitty-specs/` |
+| Split implementation | Work packages with lifecycle lanes such as `planned`, `in_progress`, `for_review`, and `done` |
+| Avoid branch chaos | Isolated git worktrees under `.worktrees/` |
+| See progress | Optional local kanban dashboard with `spec-kitty dashboard` |
+| Integrate agents | Slash commands or skills for common AI coding tools |
+
+## Quick Start
+
+Install the CLI:
+
+```bash
+pip install spec-kitty-cli
+# or
+uv tool install spec-kitty-cli
+```
+
+Create or initialize a project:
+
+```bash
+spec-kitty init my-project --ai claude
+cd my-project
+spec-kitty verify-setup
+```
+
+Replace `claude` with your agent key when needed. Common choices include `codex`, `cursor`, `gemini`, `copilot`, `opencode`, `qwen`, `windsurf`, `kiro`, and `vibe`.
+
+Open your AI coding agent in the project and run the core workflow:
+
+```text
+/spec-kitty.charter
+/spec-kitty.specify Build a small task list app.
+/spec-kitty.plan
+/spec-kitty.tasks
+```
+
+Then let the runtime choose the next action until the mission is ready:
+
+```bash
+spec-kitty next --agent claude --mission <mission-slug>
+```
+
+Review, accept, and merge:
+
+```text
+/spec-kitty.review
+/spec-kitty.accept
+/spec-kitty.merge --push
+```
+
+For the full walkthrough, see [Your First Feature](docs/tutorials/your-first-feature.md).
+
+## Everyday Commands
+
+| Command | Purpose |
+| --- | --- |
+| `spec-kitty init . --ai <agent>` | Add Spec Kitty to the current repo |
+| `spec-kitty verify-setup` | Check local installation and project wiring |
+| `spec-kitty dashboard` | Open the local mission dashboard |
+| `spec-kitty next --agent <agent> --mission <slug>` | Ask Spec Kitty what the agent should do next |
+| `spec-kitty upgrade` | Update an existing project after upgrading the CLI |
+| `spec-kitty --help` | Show available commands |
+
+## Documentation
+
+Start here:
+
+- [Getting Started](docs/tutorials/getting-started.md)
+- [Your First Feature](docs/tutorials/your-first-feature.md)
+- [CLI Command Reference](docs/reference/cli-commands.md)
+- [Slash Commands](docs/reference/slash-commands.md)
+- [Supported Agents](docs/reference/supported-agents.md)
+- [Dashboard Guide](docs/how-to/use-dashboard.md)
+- [Install and Upgrade](docs/how-to/install-and-upgrade.md)
+
+Deeper topics:
+
+- [Spec-Driven Development](docs/explanation/spec-driven-development.md)
+- [Mission System](docs/explanation/mission-system.md)
+- [Git Worktrees](docs/explanation/git-worktrees.md)
+- [Multi-Agent Orchestration](docs/explanation/multi-agent-orchestration.md)
+- [External Orchestrator Runbook](docs/how-to/run-external-orchestrator.md)
+- [Hosted Sync Workspaces](docs/how-to/sync-workspaces.md)
+
+## Development
+
+```bash
+git clone https://github.com/Priivacy-ai/spec-kitty.git
+cd spec-kitty
+pip install -e ".[test]"
+```
+
+When testing templates from a source checkout:
+
+```bash
+export SPEC_KITTY_TEMPLATE_ROOT="$(pwd)"
+spec-kitty init my-project --ai claude
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for contribution guidelines.
+
+## Support
+
+- Open a [GitHub issue](https://github.com/Priivacy-ai/spec-kitty/issues/new) for bugs, feature requests, or questions.
+- See [CHANGELOG.md](CHANGELOG.md) for release notes.
+- See [CONTRIBUTORS.md](CONTRIBUTORS.md) and the [GitHub contributors graph](https://github.com/Priivacy-ai/spec-kitty/graphs/contributors) for contributor credits.
+
+## License
+
+Spec Kitty is released under the [MIT License](LICENSE).

spec_kitty_cli-3.2.0rc2/kitty-specs/stable-320-p0-cli-stabilization-01KQSNGY/tasks/README.md

@@ -0,0 +1,69 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. Status is tracked in `status.events.jsonl`, not in WP frontmatter.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+dependencies: []
+requirement_refs:
+  - "FR-001"
+planning_base_branch: "main"
+merge_target_branch: "main"
+branch_strategy: "Planning artifacts for this mission were generated on main; completed changes must merge back into main."
+subtasks:
+  - "T001"
+  - "T002"
+authoritative_surface: "src/specify_cli/example/"
+execution_mode: "code_change"
+lane: "planned"
+owned_files:
+  - "src/specify_cli/example/**"
+task_type: "implement"
+tags: []
+history:
+  - at: "2026-05-04T00:00:00Z"
+    actor: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Status Tracking
+
+Status is tracked via the canonical event log (`status.events.jsonl`), not in WP frontmatter.
+Use `spec-kitty agent tasks move-task` to change WP status:
+
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

spec_kitty_cli-3.2.0rc2/kitty-specs/stable-320-p1-release-confidence-01KQTPZC/tasks/README.md

@@ -0,0 +1,87 @@
+# Tasks Directory
+
+This directory contains flat work package (WP) prompt files for the mission.
+
+## Current Structure
+
+```text
+tasks/
+|-- WP01-task-board-progress-semantics.md
+|-- WP02-dependency-drift-gate.md
+|-- WP03-fresh-workflow-smoke-evidence.md
+|-- WP04-release-evidence-and-deferrals.md
+`-- README.md
+```
+
+All WP files stay directly under `tasks/`. Do not create lane or status
+subdirectories.
+
+## Source Of Truth
+
+- `../wps.yaml` is the structured WP manifest used by the current planning pipeline.
+- `../tasks.md` is generated from `../wps.yaml` by `finalize-tasks`.
+- `../status.events.jsonl` and `../status.json` are the canonical status artifacts.
+- WP frontmatter carries execution metadata such as dependencies, requirement refs,
+  ownership, and branch strategy.
+
+## Required WP Frontmatter Shape
+
+Each WP file must include YAML frontmatter with the current fields used by
+`finalize-tasks` and `spec-kitty next`:
+
+```yaml
+---
+work_package_id: WP01
+title: Task Board Progress Semantics
+dependencies: []
+requirement_refs:
+  - FR-001
+subtasks:
+  - T001
+planning_base_branch: main
+merge_target_branch: main
+branch_strategy: Planning artifacts for this mission were generated on main.
+agent_profile: python-pedro
+role: implementer
+agent: codex
+model: ""
+execution_mode: code_change
+owned_files:
+  - src/specify_cli/cli/commands/agent/tasks.py
+authoritative_surface: src/specify_cli/
+history: []
+---
+```
+
+Planning-artifact WPs use `execution_mode: planning_artifact` and own paths under
+this mission directory. Code-change WPs own source and test paths.
+
+## Lane Model
+
+Current canonical lane values are:
+
+- `planned`
+- `claimed`
+- `in_progress`
+- `for_review`
+- `in_review`
+- `approved`
+- `done`
+- `blocked`
+- `canceled`
+
+Use workflow commands or `spec-kitty next` for normal progression. If manually
+inspecting status, prefer:
+
+```bash
+spec-kitty agent tasks status --mission stable-320-p1-release-confidence-01KQTPZC
+spec-kitty agent tasks list-tasks --mission stable-320-p1-release-confidence-01KQTPZC --json
+```
+
+Do not use legacy lane aliases in new instructions.
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Keep the directory flat.
+- Keep `work_package_id` aligned with the filename prefix.

spec_kitty_cli-3.2.0rc2/kitty-specs/stable-320-release-blocker-cleanup-01KQW4DF/tasks/README.md

@@ -0,0 +1,64 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. Status is tracked in `status.events.jsonl`, not in WP frontmatter.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+dependencies: []
+planning_base_branch: "main"
+merge_target_branch: "main"
+branch_strategy: "Planning artifacts were generated on main; completed changes must merge back into main."
+subtasks:
+  - "T001"
+  - "T002"
+phase: "Phase 1 - Setup"
+assignee: ""
+agent: ""
+shell_pid: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    agent: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Status Tracking
+
+Status is tracked via the canonical event log (`status.events.jsonl`), not in WP frontmatter.
+Use `spec-kitty agent tasks move-task` to change WP status:
+
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`