feat(product-lens-reviewer): domain-agnostic activation criteria and strategic consequences#481
Merged
Merged
Conversation
…strategic consequences The product-lens persona was only activating on consumer-product vocabulary (user stories, market claims, business justification), missing developer tools, internal platforms, and other products where the "are we building the right thing?" question is equally valuable. Activation criteria now test for challengeable premise claims and strategic weight rather than domain-specific vocabulary. The agent gains a product context section (external vs internal vs hybrid) that shifts analysis weights, and step 2 expands from narrow path-dependency checks to full strategic consequences: trajectory, identity impact, adoption dynamics, opportunity cost, and compounding direction. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 518fec9517
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…ne documents
Leg 1 criteria ("problem framing", "goal statements") were broad enough
to match nearly every requirements/plan document, making product-lens
effectively always-on. Tightened each bullet to require genuinely
challengeable premises rather than mere existence of problem framing.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Merged
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
1 participant
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
The product-lens persona was only activating on consumer-product vocabulary ("user stories," "market claims," "business justification"), so it never fired when reviewing plans for developer tools, internal platforms, plugins, or SDKs — even though "are we building the right thing?" is equally valuable in those contexts.
Three changes:
Test plan
🤖 Generated with Claude Code