English — Official English version of docs-analysis.
Document Requirements Analysis (English)
Analyzes all concept and requirements documents, checks their requirements against the current code, and creates a consolidated difference report.
Overview & Purpose
Analyzes all concept and requirements documents in the ../docs/ folder, checks their requirements against the current code, and creates a consolidated difference report.
Naming Convention
Prefix and Suffix
All analyzed documents receive:
- Prefix:
conN_ where N = analysis version (1, 2, 3, ...)
- Suffix:
_XX where XX = fulfillment percentage (rounded to nearest 10)
Archiving Threshold
- >= 75% fulfilled: Document is moved to
../docs/_archive/
- < 75% fulfilled: Document stays in
../docs/ with prefix/suffix
- Threshold configurable (default: 75)
Process
Phase 1: Collect Documents
- List all *.md and *.txt files in ../docs/ (root)
- Filter out README.txt
Phase 2: Extract Requirements
For each document:
- Read content
- Identify requirements (checklists, tables, MISSING/TODO markers)
- Categorize: Structure, Code, API, DB Schema, CLI, Feature
Phase 3: Code Verification
For each requirement:
- Determine verification method (Glob, Grep, Read)
- Execute verification
- Mark as: FULFILLED, PARTIAL, MISSING
Phase 4: Assessment
- Count fulfilled vs. open requirements
- Calculate fulfillment percentage (%)
- Decide: archive (>= 75%) or keep (< 75%)
Phase 5: Generate Output
- Create REQUIREMENTS_ANALYSIS.md (summary)
- Create consense_diff.md (only open requirements, by priority)
Phase 6: Versioning
- Scan for highest conN_ prefix
- New version = highest + 1
Phase 7: Rename and Move
- Apply new prefix/suffix to documents
- Archive or keep
Output
| File |
Description |
conN_REQUIREMENTS_ANALYSIS.md |
Complete analysis (version N) |
consense_diff_N.md |
Consolidated open requirements |
_archive/conN_*_XX.* |
Archived (>=75%) documents |
Priority Classification
| Priority |
Criteria |
| P1 |
Core functionality missing, system unusable |
| P2 |
Important feature missing, workaround possible |
| P3 |
Nice-to-have, improves UX |
| P4 |
Cosmetic, documentation, code quality |
Changelog
1.0.0 (2026-03-15)
Ported from BACH v3.8.0 | Standalone Version
1---2name: en-43description: <img src="banner.png" width="100%" alt="docs-analysis banner">4---56<img src="banner.png" width="100%" alt="docs-analysis banner">78> **English** — Official English version of `docs-analysis`.91011# Document Requirements Analysis (English)1213> Analyzes all concept and requirements documents, checks their requirements against the current code, and creates a consolidated difference report.1415---1617## Overview & Purpose1819Analyzes all concept and requirements documents in the ../docs/ folder, checks their requirements against the current code, and creates a consolidated difference report.2021---2223## Naming Convention2425### Prefix and Suffix26All analyzed documents receive:27- **Prefix:** `conN_` where N = analysis version (1, 2, 3, ...)28- **Suffix:** `_XX` where XX = fulfillment percentage (rounded to nearest 10)2930### Archiving Threshold31- **>= 75% fulfilled:** Document is moved to `../docs/_archive/`32- **< 75% fulfilled:** Document stays in `../docs/` with prefix/suffix33- **Threshold configurable** (default: 75)3435---3637## Process3839### Phase 1: Collect Documents40- List all *.md and *.txt files in ../docs/ (root)41- Filter out README.txt4243### Phase 2: Extract Requirements44For each document:45- Read content46- Identify requirements (checklists, tables, MISSING/TODO markers)47- Categorize: Structure, Code, API, DB Schema, CLI, Feature4849### Phase 3: Code Verification50For each requirement:51- Determine verification method (Glob, Grep, Read)52- Execute verification53- Mark as: FULFILLED, PARTIAL, MISSING5455### Phase 4: Assessment56- Count fulfilled vs. open requirements57- Calculate fulfillment percentage (%)58- Decide: archive (>= 75%) or keep (< 75%)5960### Phase 5: Generate Output61- Create REQUIREMENTS_ANALYSIS.md (summary)62- Create consense_diff.md (only open requirements, by priority)6364### Phase 6: Versioning65- Scan for highest conN_ prefix66- New version = highest + 16768### Phase 7: Rename and Move69- Apply new prefix/suffix to documents70- Archive or keep7172---7374## Output7576| File | Description |77|------|-------------|78| `conN_REQUIREMENTS_ANALYSIS.md` | Complete analysis (version N) |79| `consense_diff_N.md` | Consolidated open requirements |80| `_archive/conN_*_XX.*` | Archived (>=75%) documents |8182---8384## Priority Classification8586| Priority | Criteria |87|:--------:|----------|88| P1 | Core functionality missing, system unusable |89| P2 | Important feature missing, workaround possible |90| P3 | Nice-to-have, improves UX |91| P4 | Cosmetic, documentation, code quality |9293---9495## Changelog9697### 1.0.0 (2026-03-15)98- Ported from BACH v3.8.099100---101102*Ported from BACH v3.8.0 | Standalone Version*
ellmos-ai