Sales wants self-serve signup. Security wants SSO-only access. Both requests can be reasonable, but an agent cannot satisfy them without knowing which users and situations each rule applies to.
Make that decision before implementation. Keeping both requests visible helps the team resolve the conflict without quietly dropping one stakeholder’s requirement.
The input
The exact text of two overlapping requests, with their sources. Paste relevant excerpts from the documents or threads; a link alone does not explain the requirement.
The flow
1. Preserve both requests. Save the source text in Evidence with attribution. Start a brief for the shared problem, or attach the requests to an existing proposal.
2. Compare the proposed behavior. Ask your coding agent to identify contradictions, assumptions, and scope differences. Review its interpretation against the source text. A suggested conflict is something for the team to inspect, not a decision already made.
3. Put the choice in plain language. For the illustrative signup example: “Which customers can create an account without SSO?” Name the alternatives and the cost of each instead of hiding the disagreement inside a vague requirement.
4. Decide with the responsible stakeholders. Record the chosen behavior, its reason, the alternatives you rejected, and any condition that would reopen the decision. If nobody can decide yet, keep the question open.
5. Request and review the revision. Have the repository agent apply the agreed correction. Check that the outcomes and constraints now express one coherent policy. Approve that revision separately with Authorize implementation when the review is complete.
The output
- The conflicting requests preserved with their sources.
- A decision that states which behavior applies to which users.
- Reasoning that both stakeholders and the coding agent can inspect.
- Unresolved questions kept visible rather than treated as agreement.
Evidence that Security requested a rule establishes the source of the request. It does not by itself settle the trade-off with Sales. That remains the team’s decision.
Try it with two requests
Choose two requirements that touch the same flow. Write a concrete scenario where following one would violate the other. Use that scenario to agree the policy and check the revised proposal.
Related
Bring this workflow to your team.
Keep the evidence, decisions, and follow-up work together in your product.
Start with Pathmode