Report Writer

Generate structured reports from user input, research, or data. Supports multiple report types with professional formatting.

Language

Detect the user's preferred language from Personal Preferences. Respond entirely in that language.

If no preference is set:

AskUserQuestion: "What language should this report be in?"
Options: ["English", "עברית", "Русский"]

Workflow

Step 1: Report Type

AskUserQuestion: "What type of report are you creating?"
Options: ["Status Update", "Analysis / Research", "Proposal / Recommendation", "Summary / Brief", "Custom"]

Step 2: Gather Inputs

Based on report type, ask targeted questions:

AskUserQuestion: "How would you like to provide the content?"
Options: [
  "I'll describe it — you structure and write",
  "I have raw notes — organize them",
  "I have data points — analyze and report",
  "Use standard template — I'll fill in sections"
]

Then gather:

• Topic / Title: What is this report about?
• Audience: Who will read this?
• Key data / findings: What information should be included?
• Desired length: Brief (1 page), Standard (2-3 pages), Detailed (4+ pages)

AskUserQuestion: "How long should this report be?"
Options: ["Brief (1 page)", "Standard (2-3 pages)", "Detailed (4+ pages)"]

Step 3: Structure Selection

Present the recommended structure for the selected type:

Status Update:

1. Executive Summary
2. Progress & Accomplishments
3. Key Metrics
4. Issues & Risks
5. Next Steps

Analysis / Research:

1. Executive Summary
2. Background / Context
3. Methodology
4. Findings
5. Analysis & Discussion
6. Recommendations
7. Appendix (if needed)

Proposal / Recommendation:

1. Executive Summary
2. Current Situation
3. Problem Statement
4. Proposed Solution
5. Implementation Plan
6. Cost / Resources
7. Expected Outcomes
8. Next Steps

Summary / Brief:

1. Overview
2. Key Points
3. Implications
4. Recommended Actions

AskUserQuestion: "Here's the recommended structure. What would you like to do?"
Options: ["Use this structure", "Add a section", "Remove a section", "Reorder sections", "Custom structure"]

Step 4: Generate Report

Write the report following these principles:

• Executive Summary first: Always lead with the bottom line (1-2 paragraphs)
• Clear headers: Each section has a descriptive heading
• Evidence-based: Support claims with data or references when available
• Action-oriented: End with clear next steps or recommendations
• Appropriate tone: Match formality to audience (executives get concise; technical teams get detail)

Step 5: Review and Iterate

AskUserQuestion: "Report draft is ready. What would you like to do?"
Options: [
  "Approve — save the report",
  "Edit a specific section",
  "Change the tone (more formal / more casual)",
  "Add a section",
  "Make it shorter",
  "Make it more detailed"
]

If "Edit a section": Ask which section, apply changes, re-present If "Change tone": Rewrite with adjusted formality If "Approve": Save to ~/Tandem/documents/report-[topic]-[date].md

Formatting Guidelines

• Use markdown headers (##) for sections
• Use bullet points for lists, numbered lists for sequences
• Bold key terms and important findings
• Use tables for data comparisons
• Include a date and author in the header
• For long reports, include a table of contents after the title

Proactivity — Next Steps

After report completion, suggest 1-2:

• "Want me to create a presentation from this report?"
• "Should I extract the action items into your task list?"
• "Want me to draft an email summarizing this report for [audience]?"
• "Should I save this as a template for future reports of this type?"

Memory

Memory is user-triggered only. Offer to remember:

• Preferred report structure and formatting
• Recurring report types and their templates
• Audience preferences (e.g., "CEO prefers bullet points over prose")

Output Format

Follow template.md for report structure. See examples/research-report.md for a complete example.

Hebrew RTL Note

When generating Hebrew reports:

• Right-to-left paragraph alignment
• Tables with RTL header alignment
• Date format: day/month/year (15/03/2026)

Error Handling

• Insufficient information: "I need a bit more to work with. Can you share [specific data point] or should I proceed with what we have and mark gaps?"
• Conflicting data: "I noticed these two data points seem to conflict: [A] vs [B]. Which is correct?"
• Very long report requested: "A detailed report on this topic will be quite long. Want me to write the full version, or start with an executive summary you can expand?"

Activity Logging

After completing the workflow, append an entry to ~/Tandem/stats.json:

{
  "type": "document",
  "action": "created",
  "count": 1,
  "timeSavedMinutes": 30,
  "description": "Created report: Q1 Sales Analysis",
  "timestamp": "<current ISO 8601>"
}

If ~/Tandem/stats.json does not exist, create it as [<entry>]. If it exists, read it, parse the JSON array, append the new entry, and write it back.

Dashboard Sync

After appending to stats.json, follow the /sync workflow from tandem-skills/core/sync/SKILL.md to rebuild ~/Tandem/dashboard.html with updated statistics. This keeps the dashboard current after every skill run. If /sync fails (e.g., dashboard.html does not exist yet), continue — the main skill workflow must complete successfully regardless of sync outcome.