What problem does it solve? Writing and maintaining a large Software Requirements Specification (SRS) often leads to inconsistent terminology, concept confusion, leaked implementation details, and broken numbering. This Skill provides a structured methodology for authoring and iteratively refining SRS documents so they stay self-contained, consistent, and verifiable. ## Core Features & Use Cases - Standard SRS Structure: Canonical section layout (Introduction, Overall Description, Functional/Non-Functional Requirements, Statistics, Appendices) with a REQ-F-XXX requirement format, priority symbols, and bilingual terminology conventions. - Four-Phase Refinement Workflow: Understand the current document, propose changes before executing, apply edits from foundational sections outward, then update indexes, statistics, and the change log. - Pitfall Catalog & Renumbering: Hard-won lessons on concept separation (Editor Tab vs Dock Panel vs ToolBar Entry), safe bulk replacement, requirement renumbering scripts, and SVG/Mermaid diagram rendering rules for VS Code previews. - Use Case: When asked to "optimize this SRS" or add new requirements to a multi-thousand-line requirements document, the Skill guides concept alignment, AC extension versus new-requirement decisions, and post-edit consistency checks. ## Quick Start Ask the assistant to refine the attached SRS document by fixing concept confusion between tabs and panels and updating all section indexes and statistics accordingly.
