Remove hardcoded spec structure expectations (e.g., `## Requirements`, `### Requirement:`) in parsers, validators, and generators. This would enable support for custom schemas and different spec formats (e.g., `## Functional Requirements`, scenarios in separate files) without validation failures.
## Problem OpenSpec hardcodes spec structure expectations (## Requirements, ### Requirement:, #### Scenario: inline) throughout parsers, validators, and generators. This means custom schemas that define different formats (e.g., ## Functional Requirements, scenarios in separate verify.md files) fail validation even when their specs are correctly structured according to their own schema. This prevents OpenSpec from working with projects that have pre-existing specs in different formats. Real-world scenarios include: - Teams with specs created before adopting OpenSpec - Specs generated by other tools - Human-written specs following company/team conventions - Custom schemas that use different headers (e.g., `## Functional Requirements`) or separate verification files OpenSpec should adapt to existing spec formats, not impose it