Repository navigation
Keep release work out of ADRs and Design Docs (v1.8.3) - #101
Merged
Merged
Conversation
The ADR guidance in both technical designers told them to keep release work and task phases in the Design Doc, which contradicted the Design Doc step that excludes release execution and the Work Plan's ownership of task order. The ADR guidance now leaves implementation design to the Design Doc and task order to the Work Plan. When a confirmed requirement describes release or production work, the designer had to choose between preserving the requirement and excluding that work. It now designs only the repository capability that work relies on, if any. Bump the package version to 1.8.3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
technical-designerandtechnical-designer-frontendsaid to keep release work and task phases in the Design Doc. That contradicted the Design Doc step that excludes release execution, and it put task ordering, which the Work Plan owns, into the Design Doc. Because task execution treats the Design Doc as its baseline, anything written there can become planned and implemented work.Changes
The rest of the chain was checked and left unchanged. The design template, document-reviewer criteria, and work-planner already exclude this work.
Validation
npm test: 29 automated tests passed.🤖 Generated with Claude Code