Workspace Feature Brief: {feature_title}

Source: workspace-brief.md

# Workspace Feature Brief: {feature_title}

> **ID:** WKSP-{XXXX}
> **Version:** 1
> **Status:** Draft
> **Last Updated:** {date}
> **Author:** Workspace Orchestrator

## Feature Description
<!-- sniper:managed:description:start -->
{One-paragraph description of the cross-repo feature}
<!-- sniper:managed:description:end -->

## Affected Repositories
<!-- sniper:managed:affected-repos:start -->
| Repository | Role | Why Affected | Work Scope |
|-----------|------|-------------|------------|
| | | | |
<!-- sniper:managed:affected-repos:end -->

## New Interfaces
<!-- sniper:managed:new-interfaces:start -->
| Interface | Type | Between | Description |
|-----------|------|---------|-------------|
| | REST API / Shared Type / Event | repo-a ↔ repo-b | |
<!-- sniper:managed:new-interfaces:end -->

## Modified Interfaces
<!-- sniper:managed:modified-interfaces:start -->
| Contract | Current Version | Change Description | Breaking? |
|----------|----------------|-------------------|-----------|
| | | | |
<!-- sniper:managed:modified-interfaces:end -->

## Dependency Ordering
<!-- sniper:managed:dependency-ordering:start -->
Based on the workspace dependency graph:

### Wave 1
- **{repo}** — {what it produces that others need}

### Wave 2
- **{repo}** — {depends on Wave 1 outputs}

### Wave 3
- **{repo}** — {depends on Wave 2 outputs}
<!-- sniper:managed:dependency-ordering:end -->

## Risks & Considerations
<!-- sniper:managed:risks:start -->
- {risk or consideration}
<!-- sniper:managed:risks:end -->