Quickstart: Implement Review Retrospect Reliability
Environment
For purely local fixture and artifact-validation commands that do not touch hosted auth, tracker, SaaS sync, or sync finalization, run with sync disabled:
SPEC_KITTY_ENABLE_SAAS_SYNC=0 <command>
On this computer, any command path that touches hosted auth, tracker, SaaS sync, or sync finalization must use:
SPEC_KITTY_ENABLE_SAAS_SYNC=1 <command>
Planning Artifacts
SPEC_KITTY_ENABLE_SAAS_SYNC=0 uv run spec-kitty agent mission check-prerequisites \
--mission implement-review-retrospect-reliability-01KQQSCW \
--json
Focused Test Targets
Review-cycle boundary:
uv run pytest tests/review/test_cycle.py -q
Rejection transition:
uv run pytest tests/integration/review/test_reject_from_in_review.py -q
Fix-mode pointer loading:
uv run pytest tests/agent/test_workflow_review_cycle_pointer.py -q
Next routing:
uv run pytest tests/next/test_finalized_task_routing.py -q
Retrospective missing record:
uv run pytest tests/cli/test_agent_retrospect_missing_record.py -q
Required Smoke Flow
1. Create or load a temporary mission fixture with finalized tasks. 2. Move a WP into review. 3. Reject it with a review feedback file. 4. Verify the artifact frontmatter and canonical pointer. 5. Verify fix-mode can load that pointer. 6. Approve or complete the WP. 7. Verify spec-kitty next routes from task/WP state. 8. Verify agent retrospect has a first-class path on the completed mission.
Acceptance Checks
Before mission acceptance, run the targeted tests above plus any directly impacted existing tests:
uv run pytest tests/review tests/integration/review tests/integration/test_implement_review_retrospect_smoke.py tests/status/test_transitions.py tests/status/test_emit.py tests/next tests/cli/test_agent_retrospect_synthesize.py tests/cli/test_agent_retrospect_missing_record.py -q
If a verification command touches hosted auth, tracker, SaaS sync, or sync finalization, document why sync is in scope and run the command with the environment requested for that verification.