spec-structurelisted

The 4-file spec structure (1-description, 2-analysis, 3-solution, 4-status): what belongs in each file, the required sections, and the Tracking info fields. Use when: creating, analyzing, reviewing, implementing or archiving a spec; deciding which of the four files a piece of content belongs in. Do NOT use for: general documentation formatting (use the documentation skill), the workflow around the files (use the workflows skill).
ragnarwestad/aide · ★ 0 · Code & Development · score 75

Install: claude install-skill ragnarwestad/aide

# Spec structure ## Table of contents - [Overview](#overview) - [File structure](#file-structure) - [1-description](#1-description) - [2-analysis](#2-analysis) - [3-solution](#3-solution) - [4-status](#4-status) - [Workflow steps completed](#workflow-steps-completed) - [Separation of content](#separation-of-content) - [Templates](#templates) - [See also](#see-also) --- ## Overview 4 standardized files per issue/plan: ```text specs/<NN>-slug/ # flat structure ├── 1-description.md # (an issue key in the title is part of the slug) ├── 2-analysis.md ├── 3-solution.md └── 4-status.md ``` **Roles:** 1. **1-description.md** - Main entry point: The problem as reported 2. **2-analysis.md** - Detailed analysis: Mapping and findings 3. **3-solution.md** - Scope, behavior delta, acceptance criteria, risk and implementation plan with a TDD approach 4. **4-status.md** - Living document: Progress and status `/aide-implement`'s VERIFY phase adds a fifth, non-markdown file next to these four: `test-run.json`, written by `core/scripts/aide-record-test-run` and read by `core/scripts/aide-archive-spec`'s test-record gate — never written or read by a model. `aide-archive-spec`'s move step already `git mv`s the whole folder, so it needs no special handling of its own. --- ## File structure ### 1-description **Purpose:** Describe the problem as it was reported. **Structure:** ```markdown # [Title] ## Table of contents - Metadata - Description - Problem --