task-completion

Verify tests, build, and linter before closing beads issues.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kirvin/agent-dev-harness --skill task-completion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-completion
Source: https://github.com/kirvin/agent-dev-harness/tree/main/plugins/kf/skills/task-completion
Command: npx skills add https://github.com/kirvin/agent-dev-harness --skill task-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures thorough task completion by verifying requirements before closing beads issues and conducting a lessons-learned retro.

Core Features & Use Cases

  • Verification Before Completion: Checks tests, build, linter, and end-to-end feature functionality.
  • Lessons-Learned Retro: Prompts for a post-mortem reflection to improve future workflows.
  • Use Case: When closing a beads issue, run this skill to verify the issue is complete, then perform a mini-retro to document lessons learned and create improvement issues.

Quick Start

Run this skill to close beads issues with non-trivial changes, using the command 'close-task-completion <issue-id>'.

Frequently Asked Questions about task-completion

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

FAQPage Schema
How do I verify tests and build status before closing a beads issue?

To verify tests and build status before closing a beads issue, you can use a task completion skill that checks tests, build, and linter status. This ensures all end-to-end feature functionality passes before final closure.

What is a lessons-learned retro and when do I need it for task closure?

A lessons-learned retro is a post-mortem reflection conducted during issue closure to improve future workflows. You need it when closing beads issues with non-trivial changes to identify friction points and systemic issues.

How do I run a post-mortem retro to document friction points after issue resolution?

Run a post-mortem retro by prompting for reflection on the completed task to document friction points and systemic issues. This process addresses workflow friction and generates improvement issues for future development cycles.

Can I use automated verification for linter and build checks when completing a task?

Yes, you can use automated verification for linter and build checks when completing a task. This verification ensures thorough closure by confirming tests, build, and linter pass before an issue is officially closed.

What is the best way to identify systemic issues during software issue closure?

The best way to identify systemic issues during software issue closure is conducting a lessons-learned retro. It prompts post-mortem reflection to address friction points and create improvement issues for future workflows.

When should I not use a post-mortem retro for task closure?

You should not use a post-mortem retro for task closure when dealing with trivial changes. This verification and retro process is designed specifically for closing beads issues that involve non-trivial changes and require thorough documentation.