[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ENWR704N8AC7JVYZ22CKB":3,"skill-same:01M74ENWR704N8AC7JVYZ22CKB":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M74ENWR704N8AC7JVYZ22CKB","structural-completeness-verification",null,"Structural Completeness Verification","CarlosCaPe\u002Foctorato","CarlosCaPe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39838249?v=4","01M72WXX4ZRR8MBH1EP1QND2FQ","dataqbs","01M72WXX5NA7YCKRSJ54GW1GQ8",18,"MIT","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fstructural-completeness-verification\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: structural-completeness-verification\ndescription: \"Structural Completeness Verification\"\nmetadata:\n  short-description: \"Structural Completeness Verification\"\n  original-index: 43\n---\n\n# Structural Completeness Verification\n\n## What\n\nA systematic approach to ensuring technical documents have complete structural integrity — no orphan headers, no missing sections, no broken hierarchies, and no promised content that doesn't exist.\n\n## Why\n\nStructural incompleteness manifests as:\n- **Orphan headers**: `### 4.3 Analysis` with no content below\n- **Missing sections**: TOC promises §5 but document jumps from §4 to §6\n- **Broken hierarchy**: `#### 2.1.1` appears under `## 3` (wrong parent)\n- **Dangling references**: \"See Section 7\" when Section 7 doesn't exist\n- **Promised deliverables**: \"Part Three will contain...\" but Part Three is empty\n\nThese defects signal incomplete work and erode reader confidence.\n\n## Structural Integrity Rules\n\n| Rule | Description | Violation Example |\n|------|-------------|-------------------|\n| **Header-content pairing** | Every header has content below it | `### Analysis` followed immediately by `### Results` |\n| **Sequential numbering** | Sections numbered without gaps | §1, §2, §4 (missing §3) |\n| **Hierarchy consistency** | Child sections under correct parent | `#### 2.1.1` under `## 3` instead of `## 2` |\n| **TOC-body alignment** | Every TOC entry exists in body | TOC shows \"5. Recommendations\" but §5 missing |\n| **Promise fulfillment** | Every \"will contain\" \u002F \"see below\" delivers | \"Details below\" with no details |\n\n## How\n\n### Header Hierarchy Extraction\n\n```bash\n# Extract all headers with line numbers\ngrep -n '^#' document.md\n\n# Expected output shows clean hierarchy:\n# 10:# Title\n# 25:## 1. Introduction\n# 45:### 1.1 Background\n# 60:### 1.2 Scope\n# 80:## 2. Analysis\n# ...\n```\n\n### Structural Validation Script\n\n```javascript\nconst fs = require('fs');\nconst doc = fs.readFileSync('document.md', 'utf8');\nconst lines = doc.split('\\n');\n\nlet issues = [];\nlet lastHeaderLine = -1;\nlet lastHeaderLevel = 0;\nlet lastHeaderText = '';\n\nlines.forEach((line, i) => {\n  const headerMatch = line.match(\u002F^(#{1,6})\\s+(.+)\u002F);\n  \n  if (headerMatch) {\n    const level = headerMatch[1].length;\n    const text = headerMatch[2];\n    \n    \u002F\u002F Check for empty section (header immediately followed by header)\n    if (lastHeaderLine === i - 1) {\n      issues.push(`Line ${lastHeaderLine + 1}: Empty section \"${lastHeaderText}\"`);\n    }\n    \n    \u002F\u002F Check for hierarchy skip (e.g., ## followed by ####)\n    if (level > lastHeaderLevel + 1) {\n      issues.push(`Line ${i + 1}: Hierarchy skip - \"${text}\" (level ${level}) under level ${lastHeaderLevel}`);\n    }\n    \n    lastHeaderLine = i;\n    lastHeaderLevel = level;\n    lastHeaderText = text;\n  }\n});\n\n\u002F\u002F Check if document ends with empty section\nif (lastHeaderLine === lines.length - 1 || lastHeaderLine === lines.length - 2) {\n  issues.push(`Line ${lastHeaderLine + 1}: Document ends with empty section \"${lastHeaderText}\"`);\n}\n\nissues.forEach(issue => console.log(issue));\nconsole.log(`\\nTotal issues: ${issues.length}`);\n```\n\n### Section Numbering Audit\n\n```bash\n# Extract section numbers\ngrep -oE '^#{1,4}\\s+[0-9]+(\\.[0-9]+)*' document.md | \\\n  sed 's\u002F^#* \u002F\u002F' | \\\n  sort -t. -k1,1n -k2,2n -k3,3n\n\n# Look for:\n# - Missing numbers (1, 2, 4 — where's 3?)\n# - Duplicate numbers (two §2.3 sections)\n# - Out-of-order numbers (3.2 before 3.1)\n```\n\n### Promise Tracking\n\nSearch for forward references and verify they resolve:\n\n```bash\n# Find forward references\ngrep -n \"below\\|following\\|next section\\|will contain\\|see §\\|Part.*will\" document.md\n\n# For each, verify the promised content exists\n```\n\n## Structural Completeness Checklist\n\n```markdown\n## Before Publishing: Structure Audit\n\n### Header Integrity\n- [ ] No empty sections (header with no content)\n- [ ] No orphan headers (### without parent ##)\n- [ ] Consistent numbering scheme throughout\n- [ ] No duplicate section numbers\n\n### TOC Alignment (if TOC exists)\n- [ ] Every TOC entry has matching section\n- [ ] Every major section appears in TOC\n- [ ] TOC page numbers \u002F links are accurate\n\n### Promise Fulfillment\n- [ ] Every \"see below\" has content below\n- [ ] Every \"Part X will contain\" has content in Part X\n- [ ] Every \"to be completed\" is either complete or explicitly marked ⏳\n\n### Reference Resolution\n- [ ] Every §X.Y reference points to existing section\n- [ ] Every \"Appendix X\" reference has matching appendix\n- [ ] Every \"Table N\" reference has matching table\n```\n\n## Common Structural Failures\n\n| Failure | Cause | Prevention |\n|---------|-------|------------|\n| Empty sections | Outline created, content never added | Write content immediately after header |\n| Missing sections | Content deleted, header orphaned | Delete header with content |\n| Number gaps | Section removed, others not renumbered | Renumber after deletions |\n| Hierarchy breaks | Copy-paste from different document | Adjust header levels after paste |\n| Promise decay | \"Will add later\" → forgotten | Track promises, resolve before publish |\n\n## When to Use\n\n- **After outlining**: Verify skeleton is valid before adding content\n- **After major edits**: Structural changes cascade\n- **Before publishing**: Full structural audit\n- **After merging**: Combined documents may have structural conflicts\n\n## Real-World Example\n\nFrom the Acme Corp TDD:\n\n**Structural challenge:** Inserting new §6 (366 lines) between existing §5 and Part Two.\n\n**Verification performed:**\n1. New §6 has proper hierarchy: `### 6` → `#### 6.1` → `##### 6.1.1`\n2. No empty sections — every header has content\n3. Part Two remained \"Part Two\" (not renumbered to \"Part Three\")\n4. Charter Traceability table references §6.1–§6.6 all resolve\n\n**Result:** Script confirmed all 8 deliverable rows showed valid section references, no orphan headers in new content.\n\n## Related Skills\n\n- `38_document_semantic_coherence.md` — Structure is a coherence dimension\n- `39_cross_reference_integrity.md` — References depend on structure\n- `11_gap_analysis_pattern.md` — Find what's missing\n","# Structural Completeness Verification\n\n## What\n\nA systematic approach to ensuring technical documents have complete structural integrity — no orphan headers, no missing sections, no broken hierarchies, and no promised content that doesn't exist.\n\n## Why\n\nStructural incompleteness manifests as:\n- **Orphan headers**: `### 4.3 Analysis` with no content below\n- **Missing sections**: TOC promises §5 but document jumps from §4 to §6\n- **Broken hierarchy**: `#### 2.1.1` appears under `## 3` (wrong parent)\n- **Dangling references**: \"See Section 7\" when Section 7 doesn't exist\n- **Promised deliverables**: \"Part Three will contain...\" but Part Three is empty\n\nThese defects signal incomplete work and erode reader confidence.\n\n## Structural Integrity Rules\n\n| Rule | Description | Violation Example |\n|------|-------------|-------------------|\n| **Header-content pairing** | Every header has content below it | `### Analysis` followed immediately by `### Results` |\n| **Sequential numbering** | Sections numbered without gaps | §1, §2, §4 (missing §3) |\n| **Hierarchy consistency** | Child sections under correct parent | `#### 2.1.1` under `## 3` instead of `## 2` |\n| **TOC-body alignment** | Every TOC entry exists in body | TOC shows \"5. Recommendations\" but §5 missing |\n| **Promise fulfillment** | Every \"will contain\" \u002F \"see below\" delivers | \"Details below\" with no details |\n\n## How\n\n### Header Hierarchy Extraction\n\n```bash\n# Extract all headers with line numbers\ngrep -n '^#' document.md\n\n# Expected output shows clean hierarchy:\n# 10:# Title\n# 25:## 1. Introduction\n# 45:### 1.1 Background\n# 60:### 1.2 Scope\n# 80:## 2. Analysis\n# ...\n```\n\n### Structural Validation Script\n\n```javascript\nconst fs = require('fs');\nconst doc = fs.readFileSync('document.md', 'utf8');\nconst lines = doc.split('\\n');\n\nlet issues = [];\nlet lastHeaderLine = -1;\nlet lastHeaderLevel = 0;\nlet lastHeaderText = '';\n\nlines.forEach((line, i) => {\n  const headerMatch = line.match(\u002F^(#{1,6})\\s+(.+)\u002F);\n  \n  if (headerMatch) {\n    const level = headerMatch[1].length;\n    const text = headerMatch[2];\n    \n    \u002F\u002F Check for empty section (header immediately followed by header)\n    if (lastHeaderLine === i - 1) {\n      issues.push(`Line ${lastHeaderLine + 1}: Empty section \"${lastHeaderText}\"`);\n    }\n    \n    \u002F\u002F Check for hierarchy skip (e.g., ## followed by ####)\n    if (level > lastHeaderLevel + 1) {\n      issues.push(`Line ${i + 1}: Hierarchy skip - \"${text}\" (level ${level}) under level ${lastHeaderLevel}`);\n    }\n    \n    lastHeaderLine = i;\n    lastHeaderLevel = level;\n    lastHeaderText = text;\n  }\n});\n\n\u002F\u002F Check if document ends with empty section\nif (lastHeaderLine === lines.length - 1 || lastHeaderLine === lines.length - 2) {\n  issues.push(`Line ${lastHeaderLine + 1}: Document ends with empty section \"${lastHeaderText}\"`);\n}\n\nissues.forEach(issue => console.log(issue));\nconsole.log(`\\nTotal issues: ${issues.length}`);\n```\n\n### Section Numbering Audit\n\n```bash\n# Extract section numbers\ngrep -oE '^#{1,4}\\s+[0-9]+(\\.[0-9]+)*' document.md | \\\n  sed 's\u002F^#* \u002F\u002F' | \\\n  sort -t. -k1,1n -k2,2n -k3,3n\n\n# Look for:\n# - Missing numbers (1, 2, 4 — where's 3?)\n# - Duplicate numbers (two §2.3 sections)\n# - Out-of-order numbers (3.2 before 3.1)\n```\n\n### Promise Tracking\n\nSearch for forward references and verify they resolve:\n\n```bash\n# Find forward references\ngrep -n \"below\\|following\\|next section\\|will contain\\|see §\\|Part.*will\" document.md\n\n# For each, verify the promised content exists\n```\n\n## Structural Completeness Checklist\n\n```markdown\n## Before Publishing: Structure Audit\n\n### Header Integrity\n- [ ] No empty sections (header with no content)\n- [ ] No orphan headers (### without parent ##)\n- [ ] Consistent numbering scheme throughout\n- [ ] No duplicate section numbers\n\n### TOC Alignment (if TOC exists)\n- [ ] Every TOC entry has matching section\n- [ ] Every major section appears in TOC\n- [ ] TOC page numbers \u002F links are accurate\n\n### Promise Fulfillment\n- [ ] Every \"see below\" has content below\n- [ ] Every \"Part X will contain\" has content in Part X\n- [ ] Every \"to be completed\" is either complete or explicitly marked ⏳\n\n### Reference Resolution\n- [ ] Every §X.Y reference points to existing section\n- [ ] Every \"Appendix X\" reference has matching appendix\n- [ ] Every \"Table N\" reference has matching table\n```\n\n## Common Structural Failures\n\n| Failure | Cause | Prevention |\n|---------|-------|------------|\n| Empty sections | Outline created, content never added | Write content immediately after header |\n| Missing sections | Content deleted, header orphaned | Delete header with content |\n| Number gaps | Section removed, others not renumbered | Renumber after deletions |\n| Hierarchy breaks | Copy-paste from different document | Adjust header levels after paste |\n| Promise decay | \"Will add later\" → forgotten | Track promises, resolve before publish |\n\n## When to Use\n\n- **After outlining**: Verify skeleton is valid before adding content\n- **After major edits**: Structural changes cascade\n- **Before publishing**: Full structural audit\n- **After merging**: Combined documents may have structural conflicts\n\n## Real-World Example\n\nFrom the Acme Corp TDD:\n\n**Structural challenge:** Inserting new §6 (366 lines) between existing §5 and Part Two.\n\n**Verification performed:**\n1. New §6 has proper hierarchy: `### 6` → `#### 6.1` → `##### 6.1.1`\n2. No empty sections — every header has content\n3. Part Two remained \"Part Two\" (not renumbered to \"Part Three\")\n4. Charter Traceability table references §6.1–§6.6 all resolve\n\n**Result:** Script confirmed all 8 deliverable rows showed valid section references, no orphan headers in new content.\n\n## Related Skills\n\n- `38_document_semantic_coherence.md` — Structure is a coherence dimension\n- `39_cross_reference_integrity.md` — References depend on structure\n- `11_gap_analysis_pattern.md` — Find what's missing\n",{"name":5,"metadata":24,"description":7},{"original-index":25,"short-description":7},43,"master","b4414608cd5a3f87d1525b518f1c6add8363540d","skills\u002Fstructural-completeness-verification",6,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato","https:\u002F\u002Fwww.dataqbs.com\u002Foctorato","https:\u002F\u002Fgithub.com\u002FCarlosCaPe","www.dataqbs.com"," AI-powered data engineering\r\n& consulting\r\n\r\nWe build data platforms that turn complexity into clarity — from cloud architecture and ETL pipelines to AI-driven","2026-11-14 00:21:00",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add CarlosCaPe\u002Foctorato --skill structural-completeness-verification",{"tool":42,"command":43},"bunx","bunx skills add CarlosCaPe\u002Foctorato --skill structural-completeness-verification",{"tool":45,"command":46},"pnpm","pnpm dlx skills add CarlosCaPe\u002Foctorato --skill structural-completeness-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fstructural-completeness-verification\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"skill.json","REFERENCE","参考文档",171,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fstructural-completeness-verification\u002Fskill.json",[57,66,74,81,89,97],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74EVAA4A4B4AKR5TT732GP4","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74EV4WMRDKP2NQS4YWR8PXH","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74EV05MHTXKEXD4B2QJEYTF","workspace-skill-discovery","Discover and include ALL skills across the workspace — not just global ones. Use at the start of every session or when the user asks about available skills. Ensures project-level skills (under .claude\u002Fskills\u002F or skills\u002F in any repo) are never missed.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-skill-discovery\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74ETV78525B4VP2F28Z6NRD","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M74ETR75NF67WGVEN7288ACV","winui-app","Create, build and design WinUI 3 desktop apps with C# and the Windows App SDK following Microsoft's official guidance and CommunityToolkit. Covers XAML, navigation, theming, accessibility and deployment.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M74ETJFRNPPNSQZ36C6HD6CW","windows-brain-script-portability","Scripts in ~\u002F.claude\u002Fscripts\u002F that run on a Windows brain: use the python3.cmd shim and not bare python3, and reconfigure stdout to UTF-8 if you print symbols. Use it when writing a brain script or triaging a Windows-only crash.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwindows-brain-script-portability\u002FSKILL.md",[],[]]