Repository navigation
Keep requirement hearings and PRDs within the repository change - #197
Merged
Merged
Conversation
requirement-analyzer returned its own user-facing questions, including exclusion questions, without the convergence criteria that keep unrequested capabilities out of the hearing. Scope Confirmation also listed every unresolved product, UX, or operational question, which is wider than the hearing's one question per field below `ready`. The analyzer now returns scope and cost evidence only, and User decisions follows Hearing Step 1. The requirement criteria define a build-relevant item, so preconditions satisfied outside the repository change enter the hearing only from the user's wording. The PRD completeness check no longer asks for every stakeholder perspective. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Later design, review, and test selection treat PRD content as governing, but nothing kept release execution, organizational approval, and similar preconditions out of it. prd-creator also searched for regulatory facts on its own, and the PRD template invited delivery and sequencing risks, which belong to work planning. The PRD definition now states the same boundary the Design Doc already has, unless the user's wording raises such a precondition. The WebSearch trigger no longer lists regulatory facts, and PRD risks are limited to product risks that can change scope, success criteria, or acceptance. 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>
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.
Summary
ready.🤖 Generated with Claude Code