spec-structure

Topics in the source

• Spec structure
• Table of contents
• Overview
• File structure
• 1-description
• Acceptance criteria in EARS
• 2-analysis
• 3-solution

Overview File structure 1-description Acceptance criteria in EARS 2-analysis 3-solution 4-status Separation of content Templates -- Four files per spec, in specs/ -slug/ (an issue key in the title is part of the slug): 1. 1-description.md — the problem as reported 2. 2-analysis.md — what the investigation found 3. 3-solution.md — the solution and its plan, test first 4. 4-status.md — progress, updated as the work goes Each file is created from its template, and its headings are the structure to fill in. A fifth file, test-run.json, is written by aide-record-test-run and read by aide-archive-spec; no model writes or reads it. The details a step needs only in some runs — the Tracking info lines, approach marks, the lines the runner writes, the acceptance rows in a new round — are in the aide-analyze skill's spec-files.md reference. -- The description is written as given, never rewritten. It holds no code, no files to change and no estimate: those belong in the solution Acceptance criteria are optional: a flat bullet list, the id in bold (AC-n:), one sentence per id in one of the five EARS patterns below. Ids are additive: never renumbered or reused An ## Out of scope section is optio

This is an excerpt. Refer to the complete source and its current requirements.