一键导入
design-report
Generate status reports for design documentation. Use when creating documentation summaries, tracking progress, or preparing documentation reviews.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate status reports for design documentation. Use when creating documentation summaries, tracking progress, or preparing documentation reviews.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | design-report |
| description | Generate status reports for design documentation. Use when creating documentation summaries, tracking progress, or preparing documentation reviews. |
| allowed-tools | Read, Glob, Bash(jq *) |
| context | fork |
| agent | design-doc-agent |
Generates comprehensive status reports for design documentation, including progress metrics, health scores, and actionable recommendations.
This skill analyzes design documentation to provide insights into documentation quality, completeness, and health. It calculates progress metrics, assigns health scores, identifies issues (stale docs, orphans, sync lag), and provides prioritized recommendations for improvement.
Full report:
/design-docs:design-report
Module-specific:
/design-docs:design-report effect-type-registry
JSON output:
/design-docs:design-report --format=json
Focus on health:
/design-docs:design-report --focus=health
module: Limit to specific module (default: all)format: Output format (markdown, json, html) (default: markdown)focus: Report focus (progress, health, gaps, all) (default: all)include-archived: Include archived docs (default: false)High-level report generation process:
For detailed implementation steps, see supporting documentation below.
When you need detailed information, load the appropriate supporting file:
See instructions.md for:
Load when: Generating reports or need implementation details
See metrics-calculation.md for:
Load when: Need formula details or implementing custom metrics
See report-formats.md for:
Load when: Generating output or need format specifications
See examples.md for:
Load when: User needs examples or clarification
INFO: No design documents found in {module}
This is normal for new modules. Run /design-docs:design-init to create your first
design doc.
WARNING: Invalid frontmatter in {file}
Issue: {error-description}
Impact: Document excluded from report
Fix: Run /design-docs:design-validate {module} to identify and fix issues
Works well with:
/design-docs:design-review - Review docs flagged in report/design-docs:design-validate - Fix frontmatter issues/design-docs:design-update - Improve metrics by updating docs/design-docs:design-sync - Sync never-synced or stale docs/design-docs:design-link - Resolve orphaned documentsA successful report:
Generate cross-reference graph showing relationships between design documents. Use when visualizing doc dependencies, finding related docs, or understanding documentation structure.
Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.
Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.
Style rules for LLM context files (CLAUDE.md, AGENTS.md and their .local variants). Fires automatically when these files are opened. Enforces on-demand loading patterns, proper @-reference syntax and lean context structure.
Split large CLAUDE.md into child files. Use when context files exceed word limits, are too verbose, or cover multiple distinct topics that should be separate.
Validate CLAUDE.md structure, formatting, and quality. Use when checking context files for compliance, ensuring proper structure, or verifying before commits.