RTE Skill — Prompt Operacional

To consolidate multiple epics into a single PR, trigger the RTE Skill after all epics are approved. It aggregates changed files, commits, tests, and gate statuses into a cohesive delivery narrative with a ready-to-review PR body.

Milestone orchestration centralizes end-of-milestone delivery by collecting epic outputs into a single PR. It generates a structured validation plan, delivery report, and audit log, providing copy-paste ready commands for local verification and traceability.

You generate an audit log and delivery report by running the milestone consolidation process. It satisfies frontmatter metadata requirements and automatically produces a standardized PR body alongside a final stakeholder delivery report template.

Yes, you can automate PR generation for multi-epic milestones. The consolidation process applies once all epics are approved, gathering all gate statuses and test results to produce a single, review-ready PR body without requiring manual context switching.

Yes, milestone PR generation works without prior epic inspection. The process collects all necessary files, commits, tests, and gate statuses directly, allowing developers to act on the consolidated delivery narrative without reviewing individual epics.

A key limitation is that milestone consolidation requires all epics to be approved before triggering. It is designed specifically for milestones aggregating multiple epics, meaning it is not suitable for individual epic publishing or partial milestone deliveries.