rai-epic-plan

To sequence epic stories into a milestone-driven implementation plan, you apply a planning skill to the epic scope document. It appends a plan section defining story order with rationale, 2–4 milestones, tracking tables, and top sequencing risks for human review.

The best way to plan parallel workstreams for multi-component features is to sequence epic stories with integration checkpoints. This approach defines a critical path with scheduled integration testing and walking skeleton milestones to enable concurrent execution.

To track progress and dependencies for an epic release plan, you append a tracking table with velocity assumptions to the scope file. This exposes the critical path and measurable checkpoints so teams can execute with reduced risk and clearer priorities.

You need to apply risk-first or walking-skeleton strategies for story sequencing when converting an unsequenced list of epic stories into an actionable plan. These strategies document why each story is placed where it is to expose dependencies and critical paths.

Yes, you can use epic planning on a scope document without predefined milestones. The process takes an unsequenced scope.md file and automatically defines 2–4 milestones, including walking skeleton and E2E integration checkpoints, with verifiable success criteria.

Story sequencing for single-component features may not fully utilize the parallel workstreams and scheduled integration testing milestones designed for multi-component epics. It is optimized for complex features requiring ordering, dependencies, and multiple integration checkpoints.