Skip to content

Find existing code by responsibility and give implementers ownership of what they build - #201

Merged
shinpr merged 1 commit into
mainfrom
fix/cross-task-ownership
Nov 11, 2026
Merged

shinpr merged 1 commit into
mainfrom
fix/cross-task-ownership

Conversation

@shinpr

@shinpr shinpr commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • Ownership: Executors and designers own how the codebase is built and maintain what they leave behind. The outcome, requirements, and non-goals stay with the user's recorded decisions.
  • Finding existing code: coding-principles Reference Representativeness separates the two ways existing code relates to a change.
    • Code that depends on the change is reached through references.
    • Code that already holds the same responsibility may share no name with the change. It is found through position, role, input, and purpose.
    • Search stops once the candidates that could change the result have been read and judged. A search that finds nothing shows only that the search found nothing.
    • Executors, reviewers, analyzers, and the verifier now point to this section instead of restating it.
  • Reuse decisions: A second implementation of a responsibility that already has an owner counts as added design surface. separate requires evidence of different contracts or change reasons.
  • Findings outside the change: Executors report problems they observed but left unhandled. The orchestrator routes them through review and the completion report.
  • Review re-runs: A passed review is re-checked when a later correction changes the evidence it relied on.
  • Frontend rules: typescript-rules is merged into coding-principles/references/frontend.md. Frontend executors, the frontend quality fixer, the code reviewer, and recipe-front-adjust read that reference.
  • Comments and skeletons:
    • Code comments avoid document and section references, which drift as the documents change.
    • Test-selection notes are removed when a skeleton becomes an executable test.
  • Bump version to 0.31.0.

🤖 Generated with Claude Code

…of what they build

- Give executors and designers ownership of how the codebase is built, while the user keeps the outcome, requirements, and non-goals
- Find code that holds the same responsibility through position, role, input, and purpose as well as references; stop after the candidates that could change the result are read, not after a search finds nothing
- Count a second implementation of an existing responsibility as added design surface, and separate only on evidence of different contracts or change reasons
- Let executors report findings outside the change and route them through review
- Re-check passed reviews when a later correction changes the evidence they relied on
- Merge typescript-rules into coding-principles/references/frontend.md and have frontend agents read it
- Keep document and section references out of code comments, and drop test-selection notes when a skeleton becomes executable
- Bump version to 0.31.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@shinpr shinpr self-assigned this Nov 11, 2026
@shinpr
shinpr merged commit e9118a0 into main Nov 11, 2026
1 check passed
@shinpr
shinpr deleted the fix/cross-task-ownership branch November 11, 2026 09:40
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