Core concepts behind Spec-Driven Development. For quick start, see the main README.
Instead of rewriting entire specs, changes describe what's different:
## ADDED Requirements
### Requirement: CSV Export
The system SHALL support exporting data to CSV format.
#### Scenario: Export all observations
- GIVEN the user has observations stored
- WHEN the user requests CSV export
- THEN a CSV file is generated with all observations
- AND column headers match the observation fields
## MODIFIED Requirements
### Requirement: Data Export
The system SHALL support multiple export formats.
(Previously: The system SHALL support JSON export.)When the change is archived, these deltas merge into the main specs automatically.
Specs use standardized language for requirement strength:
| Keyword | Meaning |
|---|---|
| MUST / SHALL | Absolute requirement |
| SHOULD | Recommended, exceptions may exist |
| MAY | Optional |
1. Specs describe current behavior
2. Changes propose modifications (as deltas)
3. Implementation makes changes real
4. Archive merges deltas into specs
5. Specs now describe the new behavior
6. Next change builds on updated specs