SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsreport-template

report-template

Data & analytics

View repository

Updated 10-15 22:11

About this skill

The Synthesizer's Manual

"Data is not information. Information is not knowledge. Knowledge is not wisdom." — T.S. Eliot

Your goal is to transform raw analysis data intowisdom usable by architects。

⚠️ Mandatory Self-Correction

[!IMPORTANT] Before generating the report, youmustperform a self-check:

  1. "Are the build boundaries found by build-inspector and the IPC boundaries found by runtime-inspector consistent?"
  2. "Do the highly coupled file pairs found by git-forensics cross build boundaries?"
  3. "Are the missing components identified by concept-modeler related to the discovered risks?"
  4. "Is this report complete enough?"

⚡ Quick Start

  1. Read the template (MANDATORY): Use view_file references/REPORT_TEMPLATE.md. Your reportmustmatch this structure exactly.
  2. Synthesize all findings: Aggregate the outputs from the following sources:
    • build-inspector → Build Roots, Topology
    • runtime-inspector → IPC Surfaces, Contract Status
    • git-forensics → Coupling Pairs, Hotspots
    • concept-modeler → Entities, Missing Components
  3. Draft the report: Organize the logical connections according to the template.
  4. Publish (CRITICAL): Youmustuse write_to_file to save to genesis/v{N}/00_SCOUT_REPORT.md。forbiddento only print to chat. Ensure that the genesis/v{N}/ directory exists.

✅ Completion Checklist

Before moving to the next phase, verify:

  • Output file has been created: genesis/v{N}/00_SCOUT_REPORT.md
  • Contains: System Fingerprint, Component Map, Risk Matrix, Feature Landing Guide
  • User has confirmed the findings

🛠️ Synthesis Ritual

1. Executive Summary

  • Elevator pitch: Describe the health of the system in 30 seconds.
  • Focus: Technical debt, critical risks, reliability.

2. Dark Matter Detection

  • Do not merely list what exists.List what is missing。
  • Checklist: Logging? Error handling? CI/CD? Secret management? Version handshake?

3. Cross-Verification

  • build-inspector says "Unified management by Workspace"?
  • git-forensics says "High coupling crosses build roots"?
  • Conclusion: Hidden logical coupling discovered → Refactoring target。

4. Human Checkpoint

  • Mandatory user confirmation: "Is this report complete?"
  • Before this report is signed off, entering the Blueprint phase is forbidden。

🛡️ Master's Code

  1. No hallucination: Every claim must link to a source file.
  2. Brutal honesty: Speak bluntly. If it is a mess, call it a mess.
  3. Action-oriented: Every issue listed must imply a solution (refactor/rewrite/keep).

🧰 Toolbox

  • references/REPORT_TEMPLATE.md: Main report template.

Consumers

The direct consumers of this report are those in the /blueprint phase:

  • System Architect: Rely on your risk list to design mitigation strategies.
  • Complexity Guard: Rely on your findings to audit RFC complexity.

The quality of your analysisdirectly determinesthe quality of the next phase's design.