Skip to content

Keep work plan tasks to repository work and let codebase evidence reopen requirements once - #199

Merged
shinpr merged 3 commits into
mainfrom
fix/work-plan-task-boundary
Nov 2, 2026
Merged

shinpr merged 3 commits into
mainfrom
fix/work-plan-task-boundary

Conversation

@shinpr

@shinpr shinpr commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • A Work Plan task is defined once, in documentation-criteria, as repository work the executor completes and verifies during implementation. work-planner, document-reviewer, the plan template, and the plan recipes reference that definition, and rules that turned every uncovered obligation into an added task are removed.
  • The planning flow adds one requirements stop after the first codebase-analyzer result. When existing behavior already serves a requirement's need and falls short only of extra behavior the requirement specifies, the user sees that evidence and its cost effect and keeps or changes the requirement before UI Spec, ADR, or Design Doc work.
  • codebase-analyzer reports differences from requirements as facts and leaves the judgment to the orchestrator and designers. It no longer records or drops a candidate because it falls short of a requirement.
  • Requirements, outcome, scope, and value boundaries are no longer labeled "confirmed" or "settled". Where provenance matters, the text names the source (user-selected, orchestrator-selected, convergence record). Verification and user-action uses of "confirm" are unchanged.
  • The confirmed_requirement_context input is renamed to requirement_context across agents and recipes, and the Scope Confirmation section "Confirmed scope" is renamed to "User-selected scope".
  • Bump version to 0.29.6.

🤖 Generated with Claude Code

shinpr and others added 3 commits November 3, 2026 06:57
…pening after codebase analysis

- Define a Work Plan task as repository work the executor completes and verifies, and remove coverage rules that turned uncovered obligations into added tasks
- Add a requirements stop after the first codebase-analyzer result when existing behavior falls short of a requirement only by extra behavior it specifies
- Limit codebase-analyzer to reporting differences from requirements as facts, leaving the judgment to the parent and designers

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Drop "confirmed" where it marked requirements, outcome, scope, and value boundaries as fixed; name the source (user-selected, orchestrator-selected, convergence record) only where provenance matters
- Rename the confirmed_requirement_context input to requirement_context across agents and recipes
- Rename the Scope Confirmation section "Confirmed scope" to "User-selected scope"
- Keep verification and user-action senses of confirm unchanged

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@shinpr shinpr self-assigned this Nov 2, 2026
@shinpr
shinpr merged commit 085ba79 into main Nov 2, 2026
1 check passed
@shinpr
shinpr deleted the fix/work-plan-task-boundary branch November 2, 2026 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant