nw-collapse-detection
nw-collapse-detection identifies when technical documentation inappropriately blends multiple content types (tutorials, how-tos, explanations, and references) in single documents, which confuses readers by serving no specific audience need well. Use this skill to audit documentation for anti-patterns like tutorials that assume too much knowledge, how-tos that teach basics before procedures, references that include narrative prose, or explanations that shift into step-by-step instructions, then apply the specified remediation strategies to split content appropriately.
git clone --depth 1 https://github.com/nWave-ai/nWave /tmp/nw-collapse-detection && cp -r /tmp/nw-collapse-detection/nWave/skills/nw-collapse-detection ~/.claude/skills/nw-collapse-detectionSKILL.md
# Collapse Detection Documentation collapse = types merge inappropriately, serving no audience well. ## Anti-Patterns ### Tutorial Creep Description: Tutorial explains "why" extensively | Detection: explanation >20% | Fix: extract to separate doc, link back ### How-to Bloat Description: How-to teaches basics first | Detection: teaching fundamentals before steps | Fix: link to tutorial, assume baseline ### Reference Narrative Description: Reference includes conversational prose | Detection: prose paragraphs in entries | Fix: move to explanation doc, keep factual ### Explanation Task Drift Description: Explanation ends with "do this" steps | Detection: step-by-step in explanation | Fix: move steps to how-to, link ### Hybrid Horror Description: Single doc tries all four types | Detection: 3+ quadrants in one doc | Fix: split with clear boundaries ## Detection Rules Flag collapse when: - >20% content from adjacent quadrant | Two user needs served simultaneously | Ambiguous user journey stage - "Why" in tutorials | Task steps in explanations | Teaching in how-tos | Narrative in references ## Bad Examples for Calibration ### Tutorial with Task Focus ```markdown # Getting Started If you need to deploy to production, follow these steps... ``` **Problem**: Assumes user knows what "deploy to production" means. A tutorial should assume nothing. ### How-to Teaching Basics ```markdown # How to Configure Authentication First, let's understand what authentication is. Authentication is... ``` **Problem**: Should assume user knows what authentication is. Link to a tutorial instead. ### Reference with Opinions ```markdown ## login(username, password) This is probably the most important function you'll use... ``` **Problem**: Reference should be factual, not opinionated. Remove "probably the most important" editorializing. ### Explanation with Steps ```markdown # Why We Use Microservices ... therefore, you should: 1. Create a service, 2. Deploy it... ``` **Problem**: Steps belong in a how-to guide. The explanation should end with reasoning and link to the how-to for action.
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof
Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement
5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.
Comprehensive architecture patterns, methodologies, quality frameworks, and evaluation methods for solution architects. Load when designing system architecture or selecting patterns.
Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.