aoa-session-route-forks

To generate fork cards, provide reviewed session artifacts to the skill. It analyzes the evidence and outputs structured cards detailing predicted gains, costs, risks, owners, and stop conditions for each plausible next route.

A decision fork receipt is a traceability artifact emitted after analyzing session evidence. It documents the selected routing path among multiple branches, ensuring hidden decisions are visible and accountable for product planning.

You can clarify multiple plausible next routes by prompting the skill with your reviewed session. It surfaces explicit branch options, providing visible gain, cost, risk, and owner analysis to prevent stakeholder confusion.

Yes, session analysis supports engineering roadmaps by evaluating multiple branch options. It maps predicted gains against costs and risks while defining specific stop conditions for each potential engineering route.

You need access to session artifacts and reference schemas to emit decision fork receipts. The skill requires no external dependencies, relying solely on these inputs to generate traceable branch planning outputs.

Use fork cards for session analysis when a reviewed session concludes with several plausible moves. It is specifically designed for situations requiring visible gain, cost, risk, and owner analysis to finalize decisions.