write-final-report

Append a standardized Final Report section to approved software tickets.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/qmu/workaholic --skill write-final-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-final-report
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/write-final-report
Command: npx skills add https://github.com/qmu/workaholic --skill write-final-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill fills the final reporting gap by automatically appending a standardized Final Report section to a ticket, ensuring consistent documentation of outcomes and effort.

Core Features & Use Cases

  • Append a structured "## Final Report" block plus an optional "### Discovered Insights" subsection to completed tickets.
  • Enforce the required effort value from the approved set and document it in the ticket frontmatter.
  • Use after implementation to summarize changes, capture outcomes, and prepare a concise PR description for handoff.

Quick Start

Use the write-final-report skill on an approved ticket to attach the final report, including effort and optional insights.

Frequently Asked Questions about write-final-report

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

FAQPage Schema
How do I automate final ticket reports for project management workflows?

Automate final ticket reports by appending a standardized Final Report section to the ticket file, capturing effort and summarizing outcomes after implementation approval. This ensures consistent documentation across software-ticket workflows.

What effort values are allowed when documenting final ticket reports?

Final ticket reports enforce exact effort values from an allowed set: 0.1h, 0.25h, 0.5h, 1h, 2h, and 4h. The selected value is documented directly in the ticket frontmatter to maintain accurate effort tracking.

How do I add discovered insights to a completed software ticket?

Add discovered insights to completed tickets by appending an optional "### Discovered Insights" subsection within the Final Report block. This captures valuable findings for future reference across project management workflows.

Can I generate a PR description from final ticket documentation?

Yes, final ticket documentation prepares a concise PR description for handoff during the final reporting phase. It summarizes changes and captures outcomes after implementation to streamline code review.

Does write-final-report require a specific ticket template?

Yes, write-final-report leverages the preloaded template from update-ticket-frontmatter to append required sections. This ensures the Final Report block integrates correctly with existing ticket structures.

When should I attach a final report to a software ticket?

Attach a final report after implementation approval to close the final reporting gap. This phase captures effort, summarizes outcomes, and optionally documents discovered insights for future reference.