Generating report
Skill qte77/claude-code-plugins/plugins/docs-generator/skills/generating-report
A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.
npx -y skills add qte77/claude-code-plugins --skill generating-reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generates structured reports including status updates, assessments, post-mortems, and executive summaries. Use when writing a report, creating a project status update, or documenting an incident post-mortem.
SKILL.md
2.2 KB, as published. Nobody here has run it
Report Generation
Target: $ARGUMENTS
Generate a structured report based on the requested type and topic.
References (MUST READ)
Read these before proceeding:
references/report-structure.md— Status, assessment, post-mortem, and executive report formats
Report Types
| Type | Trigger phrases | Output path |
|---|---|---|
| Status | "status report", "project status", "weekly update" | docs/reports/<date>-status-<slug>.md |
| Assessment | "assessment", "evaluation", "review" | docs/reports/<date>-assessment-<slug>.md |
| Post-mortem | "post-mortem", "incident report", "retrospective" | docs/reports/<date>-postmortem-<slug>.md |
| Executive | "executive summary", "exec summary", "briefing" | docs/reports/<date>-executive-<slug>.md |
Workflow
- Detect report type from arguments — default to Status if ambiguous
- Read reference for the matching report structure
- Glob for existing reports in
docs/reports/to maintain consistency - Gather context:
- Grep for recent changes, TODOs, or relevant code patterns
- Read project README or CHANGELOG if available
- WebSearch for external context if needed
- Generate the report using the appropriate structure
- Output location and suggest distribution/follow-up
Rules
- Always use ISO date format (YYYY-MM-DD) in filenames and content
- Include YAML frontmatter with title, date, type, and author fields
- Post-mortems must be blameless — focus on systems, not individuals
- Status reports must include blockers and next steps
- Executive summaries must fit on one page (roughly 500 words)
- Never fabricate metrics or data — mark unknown values as "TBD"