Sign in
Menu

Your agent should know
what your app is supposed to do.

Teach it the rules your team already knows: who can invite a teammate, how discounts work, what a refund must restore. Keep that knowledge connected to the tests.

Connect your agent Start with your application
reflow / Application knowledgeIllustrative example
team-access.mdRevision 3f2a · example

Team access

Expected behaviorAn invitation keeps the role the owner selected.

Owners can invite teammates as editors or viewers. Accepting an invitation must grant that role.

Referencessrc/team/invitations.ts/settings/team
Exercised by
  1. seed-data
  2. invite-member
  3. verify-role

Selected role = accepted role

Expired invitations: coverage not recorded.

checkout.mdRevision 3f2a · example

Checkout

Expected behaviorCharge the total shown at checkout.

Apply the customer’s discount before payment. The saved order and the receipt must show the same total.

Referencessrc/orders/checkout.ts/checkout
Exercised by
  1. seed-cart
  2. place-order
  3. verify-total

Cart total = payment = receipt

Multiple discount codes: behavior not documented.

refunds.mdRevision 3f2a · example

Refunds

Expected behaviorA full refund restores the balance and returns stock.

The customer receives the amount paid. The order is marked refunded and its items become available again.

Referencessrc/orders/refunds.ts/orders
Exercised by
  1. place-order
  2. refund-order
  3. verify-refund

Balance restored · stock returned

Partial refunds: coverage not recorded.

Rule, source and test coverage

Have your agent update the rules
when behavior changes.

A permissions change lets administrators invite teammates. The old knowledge page still says only owners can do it.

Your agent compares the source change with the application knowledge and proposes an update. Review the revised rule and the checks it affects alongside the code.

How agents maintain knowledge
reflow / Knowledge changeIllustrative example
Changed sourcesrc/team/permissions.ts
canInviteRemoved: role === "owner"Added: ["owner", "admin"].includes(role)
team-access.md3f2a → candidate

Who can invite a teammate?

Removed: Only owners can invite teammates.

Added: Owners and administrators can invite teammates.

The invitation must preserve the selected role.

Affected checks
invite-as-adminNew flow needed
verify-roleKeep existing assertion
Review the rule and its affected flows

Start by having your agent
learn the application.

Connect Reflow to your coding agent and ask it to explore. Review the rules it records, add your team’s context, then ask it to write the flows that check them.

Knowledge pages keep references to the behavior they describe and call out gaps that still need investigation.

Set up application learning
Ask your coding agent
Learn this app with Reflow. Load the application-onboarding and knowledge-corpus skills. Read the source and explore the running app. Map our terminology, business rules and important user journeys into the knowledge base. Show me what you learned and which areas you haven't explored.

Then ask: “Write a flow that checks the invitation preserves the selected role. Use flow-authoring and plugin-execution, and show me the plan.”

Turn an application rule
into a repeatable check.

Define your test graph