What problem does it solve? When you have two versions of a technical document (such as two SRS drafts) and need to know what each does well, manually identifying complementary strengths and merging them without breaking the document's scope is slow and error-prone. This Skill provides a structured methodology to compare both documents, map their complementary strengths, and produce an optimized version that respects requirements-phase boundaries. ## Core Features & Use Cases - Dimensioned Strengths Analysis: Produces strengths tables for each document across six dimensions: structural, navigational, format, completeness, readability, and maintainability. - Complementarity Mapping: Explicitly maps each document's strengths to the other's gaps, then proposes an optimized table of contents with move/add annotations. - Phase-Boundary Discipline: Prevents injecting implementation details (API signatures, algorithms, class diagrams) into requirements-phase artifacts like an SRS. - Use Case: You have an SRS draft and a well-structured reference SRS. Ask to analyze both, extract the reference's navigation aids (quick-finders, per-section indexes, traceability matrices), and apply them to your draft while keeping your existing AC numbering and bilingual conventions. ## Quick Start Ask the agent to read document A and document B, analyze each one's strengths, and produce an optimized version of B with a before/after comparison.
