Work Packages: Unified Python CLI for Agents

Inputs: Design documents from /kitty-specs/008-unified-python-cli/ Prerequisites: plan.md (required), spec.md (user stories), research.md, data-model.md, quickstart.md

Tests: Testing requirements are explicit in spec.md (FR-026, FR-027) - all work packages include testing tasks to achieve 90%+ coverage for agent namespace.

Organization: Fine-grained subtasks (Txxx) roll up into work packages (WPxx). Each work package must be independently deliverable and testable.

Prompt Files: Each work package references a matching prompt file in /tasks/ generated by /spec-kitty.tasks. Lane status is stored in YAML frontmatter (lane: planned|doing|for_review|done). Treat this file as the high-level checklist; keep deep implementation detail inside the prompt files.

Parallelization Strategy: Phase 1 (WP01) is sequential foundation. Phases 2-5 (WP02-WP05) can execute in parallel across 4 independent streams. Phase 6 (WP06) requires all streams complete. Phase 7 (WP07) is final validation.

Subtask Format: [Txxx] [P?] Description

  • [P] indicates the subtask can proceed in parallel (different files/components).
  • Include precise file paths or modules.

Path Conventions

  • Python package: src/specify_cli/, tests/
  • Agent commands: src/specify_cli/cli/commands/agent/
  • Core utilities: src/specify_cli/core/
  • Migrations: src/specify_cli/upgrade/migrations/

Work Package WP01: Foundation Infrastructure (Priority: P0) 🎯 PREREQUISITE

Goal: Establish core agent CLI namespace and path resolution infrastructure for all parallel work streams. Independent Test: spec-kitty agent --help displays help text; path resolution works from main repo and worktree. Prompt: kitty-specs/008-unified-python-cli/tasks/WP01-foundation-infrastructure.md Phase: Phase 1 - Foundation (Sequential, Days 1-2) Stream: Foundation (must complete before any parallel work)

Included Subtasks

  • □ T001 Create agent command directory structure src/specify_cli/cli/commands/agent/
  • □ T002 Create src/specify_cli/cli/commands/agent/__init__.py with Typer sub-app registration
  • □ T003 [P] Create stub module src/specify_cli/cli/commands/agent/feature.py
  • □ T004 [P] Create stub module src/specify_cli/cli/commands/agent/tasks.py
  • □ T005 [P] Create stub module src/specify_cli/cli/commands/agent/context.py
  • □ T006 [P] Create stub module src/specify_cli/cli/commands/agent/release.py
  • □ T007 Register agent sub-app in src/specify_cli/cli/__init__.py
  • □ T008 Enhance src/specify_cli/core/paths.py with worktree detection logic
  • □ T009 Add environment variable support SPECIFY_REPO_ROOT to path resolution
  • □ T010 Ensure broken symlink handling (is_symlink() before exists())
  • □ T011 Create test infrastructure tests/unit/agent/ directory
  • □ T012 Create test infrastructure tests/integration/ directory
  • □ T013 Create pytest fixtures for worktree testing in tests/conftest.py
  • □ T014 Verify spec-kitty agent --help works and shows subcommands
  • □ T015 Unit test: Path resolution from main repo
  • □ T016 Unit test: Path resolution from worktree
  • □ T017 Unit test: Broken symlink handling

Implementation Notes

  • Phase 1 is SEQUENTIAL - blocks all parallel work (WP02-WP05)
  • Focus on minimal stubs to unblock parallel streams
  • Path resolution enhancement is critical for all agent commands
  • Test infrastructure must support both main repo and worktree execution

Parallel Opportunities

  • Stub modules (T003-T006) can be created in parallel
  • Test directories (T011-T012) can be created concurrently

Dependencies

  • None (starting package)

Risks & Mitigations

  • Risk: Foundation delays block all parallel work
  • Mitigation: Prioritize completion, keep scope minimal (stubs only, deep implementation in parallel phases)

Work Package WP02: Feature Management Commands (Priority: P1) 🎯 STREAM A

Goal: Migrate feature lifecycle bash scripts to Python agent commands. Independent Test: spec-kitty agent create-feature "test-feature" --json creates worktree and returns JSON; commands work from main repo and worktree. Prompt: kitty-specs/008-unified-python-cli/tasks/WP02-feature-management-commands.md Phase: Phase 2 - Feature Commands (Stream A, Agent Alpha, Days 3-4) Stream: Stream A (can run in parallel with WP03, WP04, WP05 after WP01 complete)

Included Subtasks

  • □ T018 Create src/specify_cli/core/worktree.py module
  • □ T019 Implement create_feature_worktree(repo_root, feature_slug) in worktree.py
  • □ T020 Implement get_next_feature_number(repo_root) in worktree.py
  • □ T021 Implement setup_feature_directory(feature_dir) in worktree.py
  • □ T022 Implement validate_feature_structure(feature_dir) in worktree.py
  • □ T023 Implement create-feature command in src/specify_cli/cli/commands/agent/feature.py
  • □ T024 Implement check-prerequisites command with --json, --paths-only, --include-tasks flags
  • □ T025 Implement setup-plan command with --json flag in feature.py
  • □ T026 Ensure all feature commands support dual output (JSON for agents, Rich for humans)
  • □ T027 Unit test: worktree.py utilities (create, validate, number detection)
  • □ T028 Unit test: create-feature command
  • □ T029 Unit test: check-prerequisites command with all flag combinations
  • □ T030 Unit test: setup-plan command
  • □ T031 Integration test: Create feature from main repo and verify worktree created
  • □ T032 Integration test: Create feature from existing worktree and verify behavior
  • □ T033 Verify 90%+ test coverage for feature.py and worktree.py

Implementation Notes

  • Read bash scripts being replaced: .kittify/scripts/bash/create-new-feature.sh, check-prerequisites.sh, setup-plan.sh
  • Follow Python migration patterns in quickstart.md (pathlib, subprocess)
  • All commands must detect execution location automatically
  • JSON output must be parseable by agents for workflow orchestration

Parallel Opportunities

  • Unit tests (T027-T030) can run concurrently with implementation
  • Integration tests (T031-T032) can run after command implementation complete

Dependencies

  • Requires: WP01 complete (foundation infrastructure)
  • No conflicts with: WP03, WP04, WP05 (different modules)

Risks & Mitigations

  • Risk: Worktree symlink handling varies by platform
  • Mitigation: Use existing Windows fallback pattern (file copy), test on all platforms in Phase 7

Work Package WP03: Task Workflow Commands (Priority: P1) 🎯 STREAM B

Goal: Migrate task management bash scripts to Python agent commands. spec-kitty agent workflow implement WP01 Prompt: kitty-specs/008-unified-python-cli/tasks/WP03-task-workflow-commands.md Phase: Phase 3 - Task Commands (Stream B, Agent Beta, Days 5-6) Stream: Stream B (can run in parallel with WP02, WP04, WP05 after WP01 complete)

Included Subtasks

  • □ T034 Analyze existing src/specify_cli/tasks_support.py (850 lines argparse CLI)
  • □ T035 Convert argparse structure to Typer decorators in src/specify_cli/cli/commands/agent/tasks.py
  • □ T036 Implement move-task command with --to, --json flags (later evolved to workflow implement/review)
  • □ T037 Implement mark-status command for updating task checkbox status
  • □ T038 Implement list-tasks command with lane filtering and --json flag
  • □ T039 Implement add-history command for appending history entries
  • □ T040 Implement rollback-task command for undoing lane moves
  • □ T041 Implement validate-workflow command for metadata validation
  • □ T042 Ensure all task commands support dual output (JSON for agents, Rich for humans)
  • □ T043 Preserve all existing tasks_support.py functionality in migration
  • □ T044 Unit test: move-task command (all lane transitions) - later evolved to test workflow commands
  • □ T045 Unit test: mark-status command (checkbox state changes)
  • □ T046 Unit test: list-tasks command (filtering, JSON output)
  • □ T047 Unit test: add-history command (frontmatter updates)
  • □ T048 Unit test: rollback-task command (undo logic)
  • □ T049 Unit test: validate-workflow command (validation rules)
  • □ T050 Integration test: Full task workflow (planned → doing → for_review → done)
  • □ T051 Integration test: Task commands from main repo and worktree
  • □ T052 Verify 90%+ test coverage for tasks.py
  • □ T053 Deprecate or remove old tasks_support.py after migration

Implementation Notes

  • Read bash script being replaced: Thin wrappers that call tasks_cli.py
  • Preserve argparse logic but convert to cleaner Typer decorator syntax
  • Task commands are high-frequency operations for agents - robustness critical
  • Frontmatter YAML parsing must handle edge cases (malformed, missing fields)

Parallel Opportunities

  • Unit tests (T044-T049) can run concurrently with command implementation
  • Integration tests (T050-T051) can run after all commands implemented

Dependencies

  • Requires: WP01 complete (foundation infrastructure)
  • No conflicts with: WP02, WP04, WP05 (different modules)

Risks & Mitigations

  • Risk: YAML frontmatter parsing edge cases (ruamel.yaml behavior)
  • Mitigation: Comprehensive unit tests for malformed input, graceful error messages

Work Package WP04: Agent Context Management (Priority: P2) 🎯 STREAM C

Goal: Migrate agent context update bash script to Python. Independent Test: spec-kitty agent update-context --json updates CLAUDE.md with tech stack from plan; manual additions preserved. Prompt: kitty-specs/008-unified-python-cli/tasks/WP04-agent-context-management.md Phase: Phase 4 - Context Commands (Stream C, Agent Gamma, Day 7) Stream: Stream C (can run in parallel with WP02, WP03, WP05 after WP01 complete)

Included Subtasks

  • □ T054 Create src/specify_cli/core/agent_context.py module
  • □ T055 Implement parse_plan_for_tech_stack(plan_path) to extract tech stack from plan.md
  • □ T056 Implement update_agent_context(agent_type, tech_stack, feature_dir) for updating context files
  • □ T057 Implement preserve_manual_additions(content, markers) to preserve <!-- MANUAL ADDITIONS --> sections
  • □ T058 Support all 12 agent types (Claude, Gemini, Copilot, Cursor, Windsurf, etc.)
  • □ T059 Implement update-context command in src/specify_cli/cli/commands/agent/context.py
  • □ T060 Add --agent-type flag to specify which context file to update
  • □ T061 Add --json flag for agent-parseable output
  • □ T062 Ensure dual output mode (JSON for agents, Rich for humans)
  • □ T063 Unit test: parse_plan_for_tech_stack() with various plan.md formats
  • □ T064 Unit test: preserve_manual_additions() with edge cases (missing markers, nested content)
  • □ T065 Unit test: update_agent_context() for all 12 agent types
  • □ T066 Unit test: update-context command with all flag combinations
  • □ T067 Integration test: Update context for multiple agent types
  • □ T068 Integration test: Preserve manual additions across multiple updates
  • □ T069 Verify 90%+ test coverage for context.py and agent_context.py

Implementation Notes

  • Read bash script being replaced: .kittify/scripts/bash/update-agent-context.sh (600 lines)
  • Template processing must preserve user customizations between markers
  • Tech stack extraction from plan.md uses markdown parsing (find "## Technical Context" section)
  • Agent type detection should default to current agent if not specified

Parallel Opportunities

  • Unit tests (T063-T066) can run concurrently with implementation
  • Integration tests (T067-T068) can run after command complete

Dependencies

  • Requires: WP01 complete (foundation infrastructure)
  • No conflicts with: WP02, WP03, WP05 (different modules)

Risks & Mitigations

  • Risk: Manual additions marker format changes break preservation logic
  • Mitigation: Strict marker format validation, warn if markers not found

Work Package WP05: Final Feature Lifecycle Commands (Priority: P2) 🎯 STREAM D

Goal: Complete feature lifecycle by migrating accept and merge bash wrappers to Python. Independent Test: spec-kitty agent feature accept --json and spec-kitty agent feature merge --json execute successfully; bash wrappers eliminated. Prompt: kitty-specs/008-unified-python-cli/tasks/WP05-final-feature-lifecycle-commands.md Phase: Phase 5 - Completion Commands (Stream D, Agent Delta, Day 8) Stream: Stream D (can run in parallel with WP03, WP04 after WP01-WP02 complete)

Included Subtasks

  • □ T070 Analyze existing tasks_cli.py accept and merge implementations
  • □ T071 Implement accept command in src/specify_cli/cli/commands/agent/feature.py
  • □ T072 Implement merge command with auto-retry logic from merge-feature.sh
  • □ T073 Unit tests for accept and merge commands
  • □ T074 Integration test: Full feature lifecycle (create → accept → merge)
  • □ T075 Verify 90%+ test coverage for new commands

Implementation Notes

  • Bash wrappers to replace: accept-feature.sh, merge-feature.sh (thin wrappers around tasks_cli.py)
  • Leverage existing Python implementation in scripts/tasks/tasks_cli.py
  • Migrate auto-retry logic from merge-feature.sh (auto-navigate to latest worktree if in wrong location)
  • Extract find_latest_feature_worktree() utility from common.sh

Parallel Opportunities

  • Unit tests (T073) can run concurrently with implementation
  • Integration test (T074) can run after both commands implemented

Dependencies

  • Requires: WP01-WP02 complete (foundation + feature.py exists)
  • No conflicts with: WP03, WP04 (different commands within feature.py)

Risks & Mitigations

  • Risk: Auto-retry logic may not work correctly across platforms
  • Mitigation: Test on all platforms, preserve SPEC_KITTY_AUTORETRY env var behavior

Work Package WP06: Cleanup & Migration (Priority: P0) 🎯 SEQUENTIAL

Goal: Remove all bash scripts, update slash command templates, create upgrade migration for existing projects. Independent Test: Upgrade migration successfully updates test project; all bash scripts removed; all slash commands reference spec-kitty agent commands. Prompt: kitty-specs/008-unified-python-cli/tasks/WP06-cleanup-and-migration.md Phase: Phase 6 - Cleanup & Migration (Sequential, Days 9-10) Dependencies: Requires WP01-WP05 ALL complete (all command streams finished)

Included Subtasks

  • □ T092 Create src/specify_cli/upgrade/migrations/m_0_10_0_python_only.py migration script
  • □ T093 Implement bash script detection in .kittify/scripts/bash/
  • □ T094 Implement slash command template scanning in .claude/commands/*.md
  • □ T095 Implement template update logic (replace bash script calls with spec-kitty agent equivalents)
  • □ T096 Implement worktree bash script copy cleanup
  • □ T097 Implement custom modification detection (diff against templates)
  • □ T098 Implement idempotent execution with version tracking in .kittify/metadata.yaml
  • □ T099 Add warning messages for custom bash modifications that cannot auto-migrate
  • □ T100 Delete entire scripts/bash/ directory from repository
  • □ T101 Delete entire .github/workflows/scripts/ directory from repository
  • □ T102 Update .gitignore if needed (remove bash script entries)
  • □ T103 Scan and update all slash command templates in .claude/commands/*.md
  • □ T104 Update mission templates in templates/missions/*/command-templates/
  • □ T105 Update CONTRIBUTING.md documentation (remove bash sections, add agent commands)
  • □ T106 Update README.md documentation (document spec-kitty agent namespace)
  • □ T107 Create migration guide for custom bash script modifications
  • □ T108 Unit test: Migration script detection logic
  • □ T109 Unit test: Template update logic (bash → Python command replacement)
  • □ T110 Unit test: Idempotent execution (run migration twice, verify no changes second time)
  • □ T111 Integration test: Upgrade migration on test project with bash scripts
  • □ T112 Integration test: Upgrade migration on test project with custom modifications
  • □ T113 Verify all bash scripts removed from main repository
  • □ T114 Verify all slash commands updated to reference spec-kitty agent commands

Implementation Notes

  • Follow precedent from m_0_9_0_frontmatter_only.py migration
  • Migration version must be tracked in .kittify/metadata.yaml for idempotency
  • Custom modification detection uses git diff or file hash comparison
  • Template updates must preserve user customizations outside bash script calls

Parallel Opportunities

  • Documentation updates (T105-T107) can run in parallel with migration implementation
  • Unit tests (T108-T110) can run concurrently

Dependencies

  • Requires: WP01-WP05 ALL complete (cannot delete bash scripts until Python equivalents working)
  • Blocks: WP07 (validation phase)

Risks & Mitigations

  • Risk: Custom bash modifications break automated migration
  • Mitigation: Detect modifications, warn user, provide manual migration guide
  • Risk: Breaking changes during migration period disrupt active users
  • Mitigation: Clear upgrade documentation, release notes, automated migration via spec-kitty upgrade

Work Package WP07: Testing & Validation (Priority: P0) 🎯 SEQUENTIAL

Goal: Validate all workflows work end-to-end, cross-platform compatibility, performance targets met. Independent Test: All spec-kitty workflows complete without errors; upgrade migration works; CI passes on Windows, macOS, Linux. Prompt: kitty-specs/008-unified-python-cli/tasks/WP07-testing-and-validation.md Phase: Phase 7 - Validation (Sequential, Day 11) Dependencies: Requires WP06 complete (all implementation finished)

Included Subtasks

  • □ T115 Test full feature workflow: /spec-kitty.specify → creates feature
  • □ T116 Test plan workflow: /spec-kitty.plan → creates plan, updates context
  • □ T117 Test tasks workflow: /spec-kitty.tasks → generates tasks
  • □ T118 Test implement workflow: /spec-kitty.implement → moves tasks through lanes
  • □ T119 Test review workflow: /spec-kitty.review → validates and marks done
  • □ T120 Test accept workflow: /spec-kitty.accept → acceptance validation
  • □ T121 Test merge workflow: /spec-kitty.merge → merges and cleans up
  • □ T122 Test release workflow: spec-kitty agent build-release --dry-run → verify packages created
  • □ T123 Test release workflow in GitHub Actions CI environment
  • □ T124 Create test project with old bash structure for upgrade testing
  • □ T125 Run spec-kitty upgrade on test project and verify migration succeeded
  • □ T126 Test all workflows in upgraded project (verify no regressions)
  • □ T127 Run CI tests on macOS (main development platform)
  • □ T128 Run CI tests on Linux (production platform)
  • □ T129 Run CI tests on Windows (verify file copy fallback works)
  • □ T130 Measure command execution time for simple commands (target <100ms)
  • □ T131 Measure command execution time for complex commands (target <5s)
  • □ T132 Verify performance meets baseline (no measurable overhead vs bash)
  • □ T133 Calculate test coverage for src/specify_cli/cli/commands/agent/ namespace
  • □ T134 Verify 90%+ test coverage achieved (FR-026, FR-027)
  • □ T135 Verify zero path-related errors in agent execution logs
  • □ T136 Document any edge cases discovered during validation

Implementation Notes

  • This is the final validation gate before merge
  • All workflows must complete without manual intervention
  • Cross-platform testing validates Windows symlink fallback works
  • Performance measurement establishes baseline for future regressions

Parallel Opportunities

  • Workflow tests (T115-T121) can run in parallel after infrastructure ready
  • Platform tests (T127-T129) can run concurrently
  • Performance tests (T130-T132) can run in parallel with coverage analysis

Dependencies

  • Requires: WP06 complete (everything implemented, bash scripts deleted, migration created)
  • Blocks: None (final phase before merge)

Risks & Mitigations

  • Risk: Edge cases discovered late require significant rework
  • Mitigation: Comprehensive unit/integration testing in WP02-WP05 reduces risk
  • Risk: Cross-platform issues on Windows
  • Mitigation: Early testing in Phase 1, existing fallback patterns validated in research phase

Dependency & Execution Summary

Execution Order: 1. WP01 (Foundation) - SEQUENTIAL, must complete first 2. WP02-WP05 (Commands) - PARALLEL after WP01 complete

3. WP06 (Cleanup) - SEQUENTIAL after WP02-WP05 complete 4. WP07 (Validation) - SEQUENTIAL after WP06 complete

  • WP02 (Feature: create, check, setup) - Stream A
  • WP03 (Tasks) - Stream B
  • WP04 (Context) - Stream C
  • WP05 (Feature: accept, merge) - Stream D (needs WP02)

Critical Path: WP01 (2d) → Longest stream (2d) → WP06 (2d) → WP07 (1d) = ~7 days minimum

Parallelization Benefit: 4 command streams (6 days work) execute concurrently, reducing calendar time to ~2 days.

MVP Scope: WP01 + WP02 + WP03 (Foundation + Feature + Tasks) = Minimum viable for agent workflows

Coordination Sync Points:

  • Sync 1 (Day 2): WP01 complete → Parallel streams begin
  • Sync 2 (Day 6): WP02+WP03 complete → Verify basic workflows
  • Sync 3 (Day 8): WP02-WP05 complete → Begin cleanup
  • Sync 4 (Day 10): WP06 complete → Begin validation

Subtask Index (Reference)

spec-kitty agent workflow implement WP03

spec-kitty agent workflow implement WP03

Subtask IDSummaryWork PackagePriorityParallel?
T001Create agent directory structureWP01P0No
T002Create agent __init__.pyWP01P0No
T003Create feature.py stubWP01P0Yes
T004Create tasks.py stubWP01P0Yes
T005Create context.py stubWP01P0Yes
T006Create release.py stubWP01P0Yes
T007Register agent sub-appWP01P0No
T008Enhance paths.py with worktree detectionWP01P0No
T009Add SPECIFY_REPO_ROOT env var supportWP01P0No
T010Ensure broken symlink handlingWP01P0No
T011Create tests/unit/agent/WP01P0Yes
T012Create tests/integration/WP01P0Yes
T013Create pytest fixturesWP01P0No
T014Verify agent --help worksWP01P0No
T015Unit test: Path resolution main repoWP01P0Yes
T016Unit test: Path resolution worktreeWP01P0Yes
T017Unit test: Broken symlink handlingWP01P0Yes
T018Create worktree.py moduleWP02P1No
T019Implement create_feature_worktree()WP02P1No
T020Implement get_next_feature_number()WP02P1No
T021Implement setup_feature_directory()WP02P1No
T022Implement validate_feature_structure()WP02P1No
T023Implement create-feature commandWP02P1No
T024Implement check-prerequisites commandWP02P1No
T025Implement setup-plan commandWP02P1No
T026Ensure dual output for feature commandsWP02P1No
T027Unit test: worktree.py utilitiesWP02P1Yes
T028Unit test: create-feature commandWP02P1Yes
T029Unit test: check-prerequisites commandWP02P1Yes
T030Unit test: setup-plan commandWP02P1Yes
T031Integration test: Create feature from mainWP02P1Yes
T032Integration test: Create feature from worktreeWP02P1Yes
T033Verify 90%+ coverage feature.pyWP02P1No
T034Analyze existing tasks_support.pyWP03P1No
T035Convert argparse to Typer in tasks.pyWP03P1No
T037Implement mark-status commandWP03P1No
T038Implement list-tasks commandWP03P1No
T039Implement add-history commandWP03P1No
T040Implement rollback-task commandWP03P1No
T041Implement validate-workflow commandWP03P1No
T042Ensure dual output for task commandsWP03P1No
T043Preserve tasks_support.py functionalityWP03P1No
T045Unit test: mark-status commandWP03P1Yes
T046Unit test: list-tasks commandWP03P1Yes
T047Unit test: add-history commandWP03P1Yes
T048Unit test: rollback-task commandWP03P1Yes
T049Unit test: validate-workflow commandWP03P1Yes
T050Integration test: Full task workflowWP03P1Yes
T051Integration test: Tasks from both locationsWP03P1Yes
T052Verify 90%+ coverage tasks.pyWP03P1No
T053Deprecate old tasks_support.pyWP03P1No
T054Create agent_context.py moduleWP04P2No
T055Implement parse_plan_for_tech_stack()WP04P2No
T056Implement update_agent_context()WP04P2No
T057Implement preserve_manual_additions()WP04P2No
T058Support all 12 agent typesWP04P2No
T059Implement update-context commandWP04P2No
T060Add --agent-type flagWP04P2No
T061Add --json flagWP04P2No
T062Ensure dual output for context commandsWP04P2No
T063Unit test: parse_plan_for_tech_stack()WP04P2Yes
T064Unit test: preserve_manual_additions()WP04P2Yes
T065Unit test: update_agent_context() all typesWP04P2Yes
T066Unit test: update-context commandWP04P2Yes
T067Integration test: Multiple agent typesWP04P2Yes
T068Integration test: Preserve manual additionsWP04P2Yes
T069Verify 90%+ coverage context.pyWP04P2No
T070Analyze tasks_cli.py accept/mergeWP05P2No
T071Implement accept commandWP05P2No
T072Implement merge command w/ auto-retryWP05P2No
T073Unit tests: accept/merge commandsWP05P2Yes
T074Integration test: Full lifecycleWP05P2Yes
T075Verify 90%+ coverageWP05P2No
T092Create m_0_10_0_python_only.pyWP06P0No
T093Implement bash script detectionWP06P0No
T094Implement template scanningWP06P0No
T095Implement template update logicWP06P0No
T096Implement worktree cleanupWP06P0No
T097Implement custom modification detectionWP06P0No
T098Implement idempotent executionWP06P0No
T099Add custom modification warningsWP06P0No
T100Delete scripts/bash/ directoryWP06P0No
T101Delete .github/workflows/scripts/WP06P0No
T102Update .gitignoreWP06P0No
T103Update .claude/commands/*.md templatesWP06P0No
T104Update mission templatesWP06P0No
T105Update CONTRIBUTING.mdWP06P0Yes
T106Update README.mdWP06P0Yes
T107Create migration guideWP06P0Yes
T108Unit test: Migration detectionWP06P0Yes
T109Unit test: Template updatesWP06P0Yes
T110Unit test: Idempotent executionWP06P0Yes
T111Integration test: Upgrade with bashWP06P0Yes
T112Integration test: Upgrade with custom modsWP06P0Yes
T113Verify bash scripts deletedWP06P0No
T114Verify templates updatedWP06P0No
T115Test specify workflowWP07P0Yes
T116Test plan workflowWP07P0Yes
T117Test tasks workflowWP07P0Yes
T118Test implement workflowWP07P0Yes
T119Test review workflowWP07P0Yes
T120Test accept workflowWP07P0Yes
T121Test merge workflowWP07P0Yes
T122Test release dry-runWP07P0Yes
T123Test release in CIWP07P0No
T124Create test project for upgradeWP07P0No
T125Run upgrade on test projectWP07P0No
T126Test workflows in upgraded projectWP07P0Yes
T127Run CI on macOSWP07P0Yes
T128Run CI on LinuxWP07P0Yes
T129Run CI on WindowsWP07P0Yes
T130Measure simple command performanceWP07P0Yes
T131Measure complex command performanceWP07P0Yes
T132Verify performance baselineWP07P0No
T133Calculate test coverageWP07P0No
T134Verify 90%+ coverage achievedWP07P0No
T135Verify zero path errorsWP07P0No
T136Document edge casesWP07P0No

<!-- status-model:start -->

Canonical Status (Generated)

<!-- status-model:end -->

  • WP01: done
  • WP02: done
  • WP03: done
  • WP04: done
  • WP05: done
  • WP06: done
  • WP07: done