report-writing

Generate dual-format task completion reports as chat summaries and Markdown documents.

Updated Nov 15, 2025

Search Tags:#templates #documentation #reporting #knowledge-management #task-completion #audit-trails

Ready to run

npx skills add https://github.com/robin-collins/claude_code_skills --skill report-writing-robin-collins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: report-writing
Source: https://github.com/robin-collins/claude_code_skills/tree/main/report-writing
Command: npx skills add https://github.com/robin-collins/claude_code_skills --skill report-writing-robin-collins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill provides a standardized protocol to generate dual-format task completion reports that cover both immediate user-facing chat summaries and long-form technical documentation for audit trails and reproducibility.

Core Features & Use Cases

Generate two synchronized outputs: a concise chat interface report and a detailed Markdown document with implementation details.
Location and naming: reports/{specifications_document_name}/task_{task_number}_completed.md; follow the template in references/report-template.md.
Documentation structure: Copy of chat output, task overview, execution timeline, inputs/outputs, error handling, final status; QA and implementation guidelines support reproducibility and traceability.

Quick Start

Generate both outputs immediately for a completed task by invoking the report-writing workflow and placing the results under the reports/ directory.

Frequently Asked Questions about report-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a task completion report for audit trails and reproducibility?▼

Generate task completion reports by producing both a concise chat summary and a detailed Markdown document, ensuring audit trails and reproducibility through structured documentation of execution timelines, inputs, outputs, and QA checks.

What is the best way to document completed project tasks in Markdown?▼

Document completed project tasks using a standardized Markdown template that covers task overview, execution timeline, inputs, outputs, error handling, and final status to maintain comprehensive knowledge-management and traceability.

How do I structure technical documentation for completed project specifications?▼

Structure technical documentation by saving outputs to reports/{specification-name}/task_{task_number}_completed.md, aligning with a predefined report template to satisfy content, structure, and documentation requirements.

Can I create both a short chat summary and a detailed long-form report for the same task?▼

Create dual-format task reports by generating synchronized outputs: a concise chat interface summary for immediate review and a detailed Markdown document for long-form technical documentation.

What sections are required in a reproducible task completion report?▼

Required sections in a reproducible task completion report include a copy of the chat output, task overview, execution timeline, inputs, outputs, error handling, and final status, supported by implementation guidelines.

Are there limitations to using standardized reporting templates for task documentation?▼

Standardized reporting templates require strict adherence to predefined structures and naming conventions, meaning outputs must align with references/report-template.md to satisfy documentation and traceability requirements without deviation.