| name | new-report |
| description | Create a sourced investigation, audit, benchmark, comparison, incident-analysis, or research report in the personal knowledge base. Use when the user says "write a report", "document the investigation", "capture the audit", "summarize the benchmark", or needs conclusions that are broader than a session or maintenance log. This skill writes a report from observed evidence and never performs unrelated remediation, commits, or publishes it. |
| allowed-tools | Read, Write, Bash |
New Report
Create a durable report under ~/docs/reports/.
Distinction
- A session log records work chronology.
- A maintenance log records an operational change or incident.
- A report answers a question through evidence and analysis.
Requirements
Use flat frontmatter with title, created, updated, status, kind: report, scope, observed-at, and related paths when available.
Include:
- Question or objective
- Scope and exclusions
- Methodology
- Sources and evidence
- Findings
- Analysis
- Conclusions
- Risks and limitations
- Recommendations
- Reproduction or verification steps
- Related decisions, plans, logs, standards, and configuration
Separate observation from inference. Date point-in-time measurements. Do not silently remediate findings while writing the report. Print the final path and stop.
