| name | annual-report-writer |
| description | Plan and write annual reports that combine strategy, performance, financial context, governance, impact, and forward-looking narrative into a clear stakeholder document. Use when work involves annual summaries for companies, nonprofits, startups, public-interest organizations, or internal business reviews. Do not use for generic blog writing, investor-relations legal advice, or standalone financial statement preparation. |
Annual Report Writer
Build annual reports that are credible, structured, and genuinely useful to stakeholders. The job is to turn a year of activity into a coherent, evidence-backed narrative that explains performance, context, priorities, risks, and next steps without drifting into empty corporate language.
Scope
Use this skill for:
- annual report structure and planning
- executive letter drafting
- year-in-review narrative writing
- KPI/impact summary writing
- governance and strategy sections
- stakeholder-facing performance summaries
- nonprofit impact reporting
- integrated narrative that connects data, milestones, risks, and future direction
Use this skill when
Use this skill when the task needs:
- a full annual report or annual review document
- synthesis of operational, financial, strategic, and impact information
- clean narrative structure for investors, board members, donors, customers, staff, or partners
- executive-summary writing grounded in real performance
- transformation of scattered yearly updates into one coherent report
Do not use this skill when
Do not use this skill for:
- audited financial statement preparation
- legal/regulatory filing advice beyond narrative drafting
- generic marketing copy with no annual-report structure
- a quarterly update unless the format intentionally mirrors annual reporting
Inputs to gather
Before writing, identify:
- organization type: public company, private company, startup, nonprofit, foundation, internal business unit
- primary audience: shareholders, donors, board, staff, customers, regulators, partners
- reporting requirements or mandatory sections
- year’s major events, metrics, wins, setbacks, and risks
- financial context and any approved figures
- leadership messages and strategic priorities
- brand voice and tone expectations
If numbers or claims are not verified, flag them rather than smoothing over gaps.
Output expectations
Return outputs such as:
- annual report outline
- section-by-section draft
- CEO/executive letter
- performance and KPI narrative
- impact summary
- governance/risk summary
- editorial recommendations for structure and clarity
- report messaging hierarchy
Use headings and section architecture clearly. Tie narrative claims to evidence.
Working method
1. Start with audience and purpose
An annual report can serve different purposes:
- investor confidence and strategic clarity
- board oversight and governance transparency
- donor trust and impact communication
- internal alignment and accountability
- public-facing reputation and legitimacy
The report must be written for the primary reader, not as a generic corporate artifact.
2. Build the report around the year’s real story
A strong annual report usually answers:
- what changed this year?
- what mattered most?
- what improved, what slipped, and why?
- how does the organization measure progress?
- what risks and constraints shaped the year?
- what comes next?
Do not build the report as a pile of sections with no narrative spine.
3. Balance narrative and evidence
Each major claim should be supported by:
- KPI movement
- financial context
- examples or initiatives
- customer/beneficiary/market signals
- operational outcomes
Avoid statements like “we had a transformative year” unless the report proves it.
4. Structure the report cleanly
Common section architecture may include:
- executive/CEO/chair letter
- year in review
- strategy and priorities
- operating highlights or business performance
- KPI/impact snapshot
- financial overview
- governance / leadership / risk
- outlook or next-year priorities
Tailor the exact structure to the organization type.
5. Write honestly about tradeoffs and setbacks
A credible report acknowledges:
- missed targets
- external headwinds
- strategic shifts
- lessons learned
- areas still in progress
Stakeholder trust rises when the report sounds real, not airbrushed.
6. Keep the language clear and executive-readable
Strong annual report writing should be:
- concise
- evidence-backed
- specific
- low-jargon where possible
- internally consistent across sections
- strong enough to quote or excerpt elsewhere
7. Make sections work independently and together
Readers often skim only parts of the report.
Each section should stand alone, while still reinforcing the overall story.
That means:
- no contradictory messages across sections
- no repeated empty filler
- metrics used consistently
- narrative progression from reflection → explanation → outlook
Adjacent skill boundaries
- financial-analyst: may interpret financial performance in depth; this skill writes the stakeholder-facing annual narrative
- technical-writer / documentation-writer: structure and clarity overlap, but this skill is specialized for annual-report conventions and stakeholder messaging
- copywriter: more campaign/persuasion oriented; this skill emphasizes credibility, structure, and year-in-review synthesis
- proposal-writer: future-facing persuasion; this skill is retrospective and accountability-oriented
Quality bar
A strong result should:
- reflect the organization’s actual year, not generic corporate filler
- align structure to audience and purpose
- make metrics and impact readable
- acknowledge challenges honestly
- connect performance to strategy and future direction
- be clean enough to guide design/layout downstream
References to use
Use prompt.md for response style and narrative posture.
Use guides/qa-checklist.md before finalizing.
Use examples/README.md for output patterns.
Use meta/skill.json for boundaries and metadata.
