Skip to content

fix: keep work plans to repository work and let codebase evidence reopen requirements once - #106

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

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

Conversation

@shinpr

@shinpr shinpr commented Nov 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • Work Plan tasks cover only repository work the executor completes and verifies. Governing content that is not such a task stays out of the plan.
  • Add one requirements stop after the first codebase-analyzer result. When existing behavior would serve a requirement's need without the behavior the requirement adds on top, the orchestrator presents that requirement with the existing behavior, the added behavior, and its cost effect, and the user keeps or changes it before UI Spec, ADR, or Design Doc work.
  • codebase-analyzer reports differences from requirements as facts; the orchestrator and designers own the judgment.
  • Describe requirements by their source instead of as "confirmed" or "settled". Verification statuses and user-action wording are unchanged.
  • Drop "approved" from outcomes, requirements, and scope during design and design review. Approval gates, legacy status values, and artifacts that passed a user approval keep their wording.
  • Rename the confirmed_requirement_context input to requirement_context and the Scope Confirmation section "Confirmed scope" to "User-selected scope".
  • Bump version to 1.8.7.

Validation

  • npm test: 23 Node tests and 6 Python tests passed.

🤖 Generated with Claude Code

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

- Define a Work Plan task as repository work the executor completes and verifies, and keep governing content that is not such a task out of the plan
- 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 orchestrator and designers

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Drop "confirmed" and "settled" where they 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>
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 3, 2026
@shinpr
shinpr merged commit 24bd566 into main Nov 3, 2026
2 checks passed
@shinpr
shinpr deleted the fix/work-plan-task-boundary branch November 3, 2026 01:39
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