Use when the user says "/harness:report", "create a report", "summarize this", "show me the status", "generate a report on", or wants to create stakeholder-ready documentation aggregating findings from briefs, specs, and the codebase.
Generate clear, sourced reports for stakeholders. Aggregate from briefs, specs, prototypes, and codebase inspection.
Check for .harness/kb/stack-profile.md. If missing, tell the user to run /harness:init first.
.harness/kb/stack-profile.md — for high-level context
Scan documents/shapings/ (or target_dir) for related briefs, specs, and design docs
Load domain-relevant KB files based on report topic
Load identity context from ~/.harness/identity/ for full stakeholder-calibrated output:
~/.harness/identity/company.md (domain context), (communication voice), and (preferences)~/.harness/identity/brand.md~/.harness/identity/operator.md/harness:identity-company, /harness:identity-brand, or /harness:identity-operator to personalize reports."| Type | Best for | Key outputs |
|---|---|---|
| Feature Landscape | What exists across the codebase for a domain | Capability inventory, gaps, diagrams |
| Feasibility Assessment | Can we do it? + What would it take? + Risks | Combines shape + ground findings, effort breakdown |
| Architecture Overview | System components and relationships | Data flow diagrams, component inventory, API endpoints |
| Progress Summary | Aggregate status of ongoing work | Status of all specs/briefs in target_dir |
Ask if not clear:
What type of report? (landscape / feasibility / architecture / progress)
What domain or scope? (specific feature, entire system, recent work)
Output format? (markdown in target_dir — default)
From briefs/specs: Scan target_dir for recent artifacts and aggregate findings.
From codebase (READ-ONLY operations only):
Database schema and relationships
API endpoint listing
UI component inventory
Job/async system inventory
Git history for recent changes (if relevant)
From KB files: Load domain-relevant KB files for context.
Structure:
Executive Summary — 2-3 sentences with the key finding or recommendation
Scope — What this report covers and does not cover
Findings — Sourced findings with evidence:
Reference specific files, tables, components by name and path
Include Mermaid diagrams where they clarify relationships
Include data tables for structured information
Recommendations — Numbered, with rationale
Sources — List all files, KB entries, and codebase paths consulted
Save to {target_dir}/{date}-{topic}-report.md with frontmatter:
---