1. Connect FlowRail
Follow the installation guide in your project, restart the supported agent session, and confirm the FlowRail MCP connection. Keep the design specification in the same project.
2. Describe the requirement
Be explicit about access, destinations and failure handling. For example, an invoice feature could have this requirement:
# Invoice approval An authenticated user may approve an invoice only if it belongs to their organization. Check ownership before changing the invoice. Reject unauthorized requests without changing its status.
Use the flowrail-design-review skill to review my specification before implementing it. Show me the security requirements and anything that needs clarification.
Wait for the review to complete. The skill records the active review in .flowrail/context.json so supported subsequent checks can attach their evidence to it. An incomplete or failed review needs attention before implementation proceeds.
4. Implement and follow the evidence
Ask your agent to implement the reviewed feature. FlowRail checks supported proposed code writes. A denied write returns a finding for the agent to address; an incomplete design-bound check pauses for retry. Open the corresponding review in your dashboard to see findings and later evidence together.
A passing write does not settle every requirement. If evidence lives in another file or service, the requirement can remain not established. The review can stay open after an individual write passes.