td

Generate retrospective documents with Git context, task details, test results, and errors, then comment on GitHub or Jira issues.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/goffity/dev-km --skill td
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: td
Source: https://github.com/goffity/dev-km/tree/main/skills/td
Command: npx skills add https://github.com/goffity/dev-km --skill td

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating detailed post-task retrospectives, ensuring that all relevant information, context, and outcomes are captured efficiently.

Core Features & Use Cases

  • Automated Retrospective Generation: Creates retrospective documents with Before/After context.
  • Session Documentation: Captures Git context, user input on tasks, test status, and errors.
  • Issue Integration: Comments directly on associated GitHub or Jira issues.
  • Use Case: After completing a development task, use this Skill to automatically generate a summary of what was done, any issues encountered, and the final status, which is then added as a comment to the relevant issue tracker.

Quick Start

Run /td done to create a retrospective for a completed task.

Frequently Asked Questions about td

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

FAQPage Schema
How do I generate a post-task retrospective from Git history?

You can generate a post-task retrospective by capturing Git context, test results, and user-provided task details. The Skill compiles this data into a structured document with Before/After context and updates your issue tracker.

Can I automatically comment on GitHub issues after a task is done?

Yes, you can automatically comment on associated GitHub issues after a task is done. The Skill integrates with issue trackers to post generated retrospective summaries and update task status directly.

What is included in an automated development session documentation?

Automated session documentation includes captured Git context, user input on tasks, test status, and encountered errors. It provides a comprehensive summary of outcomes and context for development retrospectives.

Do I need the gh command line tool to update task status?

Yes, you need the gh command line tool installed to update task status and integrate with issue trackers. This dependency allows the Skill to comment on associated GitHub issues directly.

Does this retrospective generator support automated documentation updates and commit workflows?

Yes, the retrospective generator supports automated documentation updates and commit workflows. It streamlines capturing task outcomes and integrating them into your existing project documentation.