Stats
Actions
Tags
From report-forge
Defines report types, audience guidance, tone standards, and agent recruitment logic. Auto-invoked on report generation to ensure appropriate methodology.
How this skill is triggered — by the user, by Claude, or both
Slash command
/report-forge:report-methodologyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides reasoning guidance for report generation. It defines the eight report types, their purposes, audiences, tone requirements, and agent recruitment patterns.
This skill provides reasoning guidance for report generation. It defines the eight report types, their purposes, audiences, tone requirements, and agent recruitment patterns.
Purpose: High-level overview for leadership and non-technical stakeholders Audience: Executives, product leaders, business stakeholders Length: 2-3 pages Tone: Business-focused, clear, concise, minimal technical jargon Agents: investigator, synthesizer (analyst skipped for efficiency)
Key themes: Overview, key findings (3-5 points), recommendations, next steps
Purpose: Detailed technical analysis for engineering teams Audience: Engineers, architects, technical leads Length: 5-10 pages Tone: Technical, thorough, analytical Agents: investigator, analyst, synthesizer
Key themes: Context, technical analysis, implementation details, trade-offs, recommendations
Purpose: Market and competitor research Audience: Product managers, executives, strategy team Length: 3-5 pages Tone: Strategic, comparative, insight-driven Agents: investigator, analyst, synthesizer
Key themes: Market context, competitor comparison, strengths & gaps, strategic recommendations
Purpose: System design evaluation and recommendations Audience: Architects, senior engineers, technical leads Length: 4-8 pages Tone: Architectural, evaluative, forward-looking Agents: investigator, analyst, synthesizer
Key themes: Current architecture, strengths, weaknesses, recommendations, migration path
Purpose: Performance metrics, bottlenecks, and optimization opportunities Audience: Engineers, SREs, technical leads Length: 3-6 pages Tone: Data-driven, metrics-focused, actionable Agents: investigator, analyst, synthesizer
Key themes: Metrics, bottlenecks, root causes, optimization opportunities, implementation plan
Purpose: Post-incident analysis and learning Audience: Engineering teams, leadership, SREs Length: 3-5 pages Tone: Objective, blameless, learning-focused Agents: investigator, analyst, synthesizer
Key themes: Incident summary, timeline, root cause, impact assessment, action items
Purpose: Periodic progress assessment Audience: Teams, leadership, stakeholders Length: 4-6 pages Tone: Reflective, progress-focused, forward-looking Agents: investigator, synthesizer (analyst skipped for efficiency)
Key themes: Period summary, achievements, metrics, challenges, outlook
Purpose: Evaluation of new initiative viability Audience: Product managers, executives, engineering leads Length: 5-8 pages Tone: Evaluative, balanced, recommendation-driven Agents: investigator, analyst, synthesizer
Key themes: Proposal overview, technical feasibility, resource requirements, risk assessment, recommendation (go/no-go)
Categories organize reports by domain. Each report has exactly one primary category:
| Category | Domain |
|---|---|
architecture | System design, patterns, technical decisions |
performance | Speed, scalability, resource usage |
security | Vulnerabilities, compliance, best practices |
integration | Third-party systems, APIs, data flows |
feature-analysis | Feature evaluation, user impact |
operations | DevOps, deployment, monitoring |
technical-debt | Code quality, refactoring needs |
competitive | Market analysis, competitor features |
user-research | User behavior, feedback analysis |
business-metrics | KPIs, ROI, business impact |
Different report types use different agent combinations:
investigator + synthesizer only (skip analyst for efficiency):
executive-summary – straightforward assembly, minimal interpretation neededquarterly-review – progress report, straightforward data collectioninvestigator + analyst + synthesizer (full pipeline):
technical-deep-dive – needs detailed interpretationcompetitive-analysis – needs strategic interpretationarchitecture-review – needs pattern analysis and evaluationperformance-analysis – needs metric interpretation and root cause analysisincident-postmortem – needs root cause analysis and learning extractionfeasibility-study – needs risk/opportunity assessmentSet confidence levels based on data availability and investigation completeness:
High Confidence:
Medium Confidence:
Low Confidence:
Adopt the appropriate tone for each report type:
Executive Summary: Business language, clear value statements, avoid technical jargon, focus on outcomes and decisions
Technical Deep Dive: Technical precision, detailed explanations, appropriate use of technical terms, focus on implementation
Competitive Analysis: Strategic perspective, comparative framing, market context, focus on positioning and differentiation
Architecture Review: Architectural thinking, system-level view, design patterns, focus on structure and evolution
Performance Analysis: Data-driven, metrics-focused, quantitative, focus on measurements and optimization
Incident Postmortem: Objective, blameless, timeline-based, focus on learning and prevention
Quarterly Review: Reflective, balanced (achievements + challenges), progress-oriented, focus on trajectory
Feasibility Study: Evaluative, risk-aware, recommendation-oriented, focus on viability and go/no-go decision
Match content depth to the intended audience:
Leadership (Executives, Product Managers):
Technical Teams (Engineers, Architects):
Cross-functional (Mixed Audiences):
npx claudepluginhub jeremybrice/the-forge --plugin report-forgeAdapts analytical findings to stakeholder audiences (executives, product teams, engineers, data teams) by adjusting framing, detail level, and format. Useful for narratives, decks, reports when audience specified.
Writes and audits business reports, briefing documents, and information reports for answer-first structure, precision, hierarchy, and navigability. Use when a report buries its findings, is written for the writer rather than the reader, or lacks clear structure. Triggers: 'write a report', 'report writing', 'business report', 'briefing document', 'information report', 'research summary', 'the report isn't clear', 'buries the findings'.
Creates consulting-grade reports and executive presentations using SCQA/SCR structure, Pyramid Principle for strategic assessments, board decks, and due diligence.