An agent can start from an approved proposal and still get stuck because a required API, migration, or earlier change is missing. Review the dependencies before assigning the next intent so the engineer has the foundations the proposal assumes.
The input
Several related proposals and the current state of their prerequisites. The product’s Intents list is a starting point for finding them; its order reflects recent updates, not a dependency schedule.
The flow
1. Identify the prerequisites. Read each proposal’s scope, constraints, and recorded relations. Distinguish a true dependency from work that is merely related. Ask the engineer to check assumptions about APIs, data, and infrastructure.
2. Confirm what is available. Open the prerequisite intents and inspect their implementation and checks. A Shipped label means work landed; it does not prove that every contract the next change needs works as expected.
3. Agree the order. Start with the prerequisite work that the chosen outcome depends on. Record the dependency and the reason for the sequence. If a prerequisite is unavailable, revise the plan explicitly rather than asking the agent to invent a substitute.
4. Review the next proposal. Resolve its open questions and requested changes, check readiness, and obtain authorization for the revision the agent will use. A position in a list is not permission to build.
5. Hand over current context. Have the connected coding agent read the repository intent and current review state. Run the checks that cover its dependencies as well as the feature itself. Revisit the sequence when a prerequisite changes.
The output
- Prerequisites named and checked before the next implementation starts.
- A deliberate build order with its reasoning recorded.
- An authorized proposal that uses the available contracts.
- Missing dependencies raised for review instead of silently replaced with stubs.
Try it with two related intents
Choose one intent that depends on another. Name the exact behavior or contract it needs, check whether that is available, and confirm that its proposal and verification checks use the same assumption.
Related
Bring this workflow to your team.
Keep the evidence, decisions, and follow-up work together in your product.
Start with Pathmode