# Feature Spec: [Feature Name]

**Source:** [issue link]
**Status:** Draft

---

## Overview
> [Brief description of the feature and why it's needed]

## Requirements
- [Functional requirement 1]
- [Functional requirement 2]
- [Functional requirement 3]

## Success and Verification
_Define the proof before implementation. These are planned checks, not claims that verification has already passed. Keep criteria specific to this feature's scope; omit checks that don't apply._

### Successful Outcome
[What can the user accomplish when this work is complete? Describe the observable result.]

### Verification Criteria and Methods
_Each required outcome needs a suitable check and a clear passing result. Include important failure cases as well as the happy path. Reference the Edge Cases section where relevant so expected behavior and verification stay aligned._

| Criterion | How to verify | Passing result |
|-----------|---------------|----------------|
| [Required behavior or outcome] | [Test, walkthrough, measurement, or review, including relevant inputs] | [Specific observable evidence or threshold] |
| [Important failure or edge case] | [How to exercise the condition] | [Expected handling and observable result] |

### End-to-End Proof
_Describe the main user journey to exercise from start to finish. Check the actual outcome, not just whether individual components pass tests._

- **Environment:** [Local / staging / production, as appropriate to the requested scope]
- **Starting state and inputs:** [Required setup and representative data]
- **Steps:** [User actions from start to finish]
- **Expected final result:** [What must be observable when the journey completes]
- **Evidence to capture:** [Relevant test output, screenshot, persisted record, measurement, or review result]

### What Must Not Break
_Existing behavior that must still work, and how to check it. Omit for a new project when nothing exists yet._

| Existing behavior | How to verify it still works |
|-------------------|------------------------------|
| [Behavior to preserve] | [Relevant regression check] |

### Verification Constraints
_Note checks that need user review, unavailable credentials, external access, or a longer observation period. If blocked, report the specific criterion that remains unverified; a substitute check does not establish the original outcome._

- [Constraint, affected criterion, and what is needed to complete verification — or "None"]

## Edge Cases
| Scenario | Expected Behavior |
|----------|-------------------|
| [Edge case 1] | [How to handle] |
| [Edge case 2] | [How to handle] |

## UI/UX Notes
> [Design considerations, if applicable]

## Technical Approach

### Scope of Changes
> [High-level areas and likely affected files. Label confirmed repository evidence separately from inferred scope.]

### API Changes
> [New or modified endpoints, if any]

### Schema Changes
> [New or modified tables/fields, if any]

### Implementation Notes
> [Key decisions, patterns to follow, gotchas]

## Not in Scope
- [Explicit exclusion for this feature]