42 lines
1.3 KiB
Markdown
42 lines
1.3 KiB
Markdown
# Sprint 180 Plan: Strict Execution-Contract Taskitem Generation
|
|
|
|
## Context
|
|
Taskitems remain too generic for autonomous implementation. Generation must emit
|
|
deterministic execution contracts with concrete steps, files, tools, and tests.
|
|
|
|
## Goals
|
|
1. Add strict execution-contract mode to `whetstone_generate_taskitems`
|
|
2. Emit per-task execution contract metadata
|
|
3. Escalate tasks when specificity is below threshold
|
|
|
|
## Steps
|
|
|
|
### Step 1939: Strict contract mode for generation (10 tests)
|
|
Add `strictExecutionContract` input mode and deterministic output metadata.
|
|
|
|
### Step 1940: Execution hint extraction from requirements (10 tests)
|
|
Extract and normalize:
|
|
- `stepIds`
|
|
- `targetFiles`
|
|
- `requiredTools`
|
|
- `acceptanceCommands`
|
|
|
|
### Step 1941: Per-task contract packet emission (10 tests)
|
|
Emit `executionContract` object with:
|
|
- determinism/rollback contracts
|
|
- evidence artifacts
|
|
- risk + blocking policy
|
|
- `executionSpecificityScore`
|
|
|
|
### Step 1942: Strict-mode escalation for low-specificity tasks (8 tests)
|
|
If specificity below threshold:
|
|
- force `queueReady=false`
|
|
- force `escalate=true`
|
|
- append deterministic reason codes
|
|
|
|
### Step 1943: Sprint 180 Integration Summary (8 tests)
|
|
Add `editor/src/Sprint180IntegrationSummary.h`.
|
|
|
|
## Architecture Gate
|
|
- No strict-mode task may be queue-ready without execution-contract metadata.
|