~aod-deliver

Automate delivery retrospectives and log results to GitHub Issues and knowledge docs.

86|21|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/davidmatousek/tachi --skill aod-deliver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ~aod-deliver
Source: https://github.com/davidmatousek/tachi/tree/main/.claude/skills/~aod-deliver
Command: npx skills add https://github.com/davidmatousek/tachi --skill aod-deliver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to conduct a structured delivery retrospective at the end of a feature, capturing delivery metrics, surprises, and lessons learned, and feeding them back into discovery while creating an institutional knowledge base.

Core Features & Use Cases

  • Validate the Definition of Done, capture estimated vs. actual durations, and surface blockers.
  • Log surprises and feed ideas back into discovery via GitHub Issues, then archive insights in the Institutional Knowledge docs.
  • Write a delivery entry (delivery.md) under specs/{NNN}-*/ and append to docs/INSTITUTIONAL_KNOWLEDGE.md for long-term knowledge.
  • Post retrospective metrics and outcomes back to the related GitHub Issue and backlog, preserving an auditable trail.

Quick Start

Run /aod.deliver after you finish work on a feature to start the delivery retrospective.

Frequently Asked Questions about ~aod-deliver

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

FAQPage Schema
How do I conduct a delivery retrospective for a completed feature?

To conduct a delivery retrospective, run the /aod.deliver command after closing a feature. It validates the Definition of Done, captures estimated versus actual duration metrics, logs surprises, and writes a delivery entry under specs/{NNN}-*/.

How do I capture lessons learned and log them to GitHub Issues?

You can capture lessons learned by running a delivery retrospective that logs surprises and feeds follow-up ideas back into discovery via GitHub Issues, preserving an auditable trail of retrospective outcomes.

What is a delivery retrospective and when do I need to run one?

A delivery retrospective is a structured process for capturing metrics, surprises, and lessons learned when closing a feature. You need it to validate the Definition of Done and build an institutional knowledge base.

How do I update institutional knowledge docs after finishing a feature?

To update institutional knowledge docs, the delivery retrospective automatically appends captured insights to docs/INSTITUTIONAL_KNOWLEDGE.md while writing a delivery.md file, ensuring long-term knowledge retention.

Can I track estimated versus actual delivery metrics for feature development?

Yes, you can track delivery metrics by running the retrospective workflow which captures estimated versus actual durations, surfaces blockers, and posts retrospective outcomes back to the related GitHub Issue.

What's the best way to automate end-to-end delivery tracking and follow-up creation?

The best way to automate delivery tracking is using a structured retrospective workflow that validates completion, captures metrics, creates follow-up ideas in GitHub Issues, and archives project artifacts without manual intervention.