## Purpose
[Describe the overall goal and scope of this specification. What user experience or system behavior is being designed? Who are the primary users/stakeholders?]
## Principles / Experience Goals
[Optional: List the key design principles or experience goals that guide this specification. Examples:
- **Clarity first:** Prioritize understandable output
- **Speed:** Minimize latency and cognitive load
- **Safety:** Prevent accidental destructive actions
- **Composability:** Work well with other tools and commands]
## Scope
[Define what is IN scope and what is OUT of scope. Help readers understand boundaries and where this specification stops.]
## Detailed Specification
[The main body of the specification. This can be organized in whatever way makes sense:
- Command behaviors and syntax
- User interaction flows
- Output formats and examples
- Error handling and edge cases
- Performance characteristics
- Accessibility requirements]
### [Subsection Title]
[Detailed specification content...]
## Examples
[Optional but highly recommended: Provide concrete examples showing:
- Common use cases
- Edge cases
- Expected output
- Error scenarios]
## Verification / Acceptance Criteria
[How to verify this specification is correctly implemented:
- Observable behaviors
- Test scenarios
- Quality attributes
- Integration points]
## Related Requirements
[Optional: Cross-reference related requirements, specifications, or design decisions.]