Cross-Repo Implementation Plan: {feature_title}
Source:
workspace-plan.md
markdown
# Cross-Repo Implementation Plan: {feature_title}
> **Feature:** WKSP-{XXXX}
> **Version:** 1
> **Status:** Draft
> **Last Updated:** {date}
> **Author:** Workspace Orchestrator
> **Contracts:** {list of contract files}
## Per-Repo Work Breakdown
<!-- sniper:managed:repo-breakdown:start -->
### {repo-name} (Wave {N})
**Repo Feature ID:** SNPR-{XXXX}
**Stories:**
| Story | Description | Contract Refs |
|-------|-------------|---------------|
| | | |
**Dependencies from other repos:** {what this repo needs from previous waves}
**Produces for other repos:** {what this repo provides to subsequent waves}
<!-- sniper:managed:repo-breakdown:end -->
## Sprint Wave Ordering
<!-- sniper:managed:wave-ordering:start -->
| Wave | Repositories | Parallel? | Depends On |
|------|-------------|-----------|------------|
| 1 | | Yes | — |
| 2 | | | Wave 1 |
| 3 | | | Wave 2 |
<!-- sniper:managed:wave-ordering:end -->
## Integration Validation Criteria
<!-- sniper:managed:validation-criteria:start -->
### Between Wave 1 and Wave 2
- [ ] {contract item to validate}
### Between Wave 2 and Wave 3
- [ ] {contract item to validate}
### Final Integration
- [ ] {end-to-end check}
<!-- sniper:managed:validation-criteria:end -->
## Rollback Plan
<!-- sniper:managed:rollback:start -->
If integration validation fails at any wave boundary:
1. {step}
<!-- sniper:managed:rollback:end -->