item-close

Transition work items to terminal states and link duplicates in Maestro.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/owebboy/maestro --skill item-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: item-close
Source: https://github.com/owebboy/maestro/tree/main/skills/item-close
Command: npx skills add https://github.com/owebboy/maestro --skill item-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the friction of managing stale or invalid work items by providing a standardized, automated way to archive tasks that are no longer actionable.

Core Features & Use Cases

  • Terminal Status Management: Quickly transition items to wont-fix, deferred, or duplicate states.
  • Contextual Documentation: Automatically attaches closing notes and relationship links for duplicates to maintain a clean audit trail.
  • Use Case: When a feature request is identified as a duplicate of an existing ticket, use this Skill to link the two items and archive the redundant request in one fluid motion.

Quick Start

Use the item-close skill to mark item 42 as a duplicate of item 10.

Frequently Asked Questions about item-close

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

FAQPage Schema
How do I archive stale work items and clean up a project backlog?▼

To mark duplicate work items, link the redundant request to the existing ticket and transition its status to duplicate. This automatically attaches closing notes and relationship links to maintain a clean audit trail.

What is the best way to manage work item lifecycle transitions to terminal states?▼

To mark duplicate work items, link the redundant request to the existing ticket and transition its status to duplicate. This automatically attaches closing notes and relationship links to maintain a clean audit trail.

How do I link duplicate tickets and attach closing notes automatically?▼

To mark duplicate work items, link the redundant request to the existing ticket and transition its status to duplicate. This automatically attaches closing notes and relationship links to maintain a clean audit trail.

Do I need the Maestro work-item store to execute status changes and comments?▼

To mark duplicate work items, link the redundant request to the existing ticket and transition its status to duplicate. This automatically attaches closing notes and relationship links to maintain a clean audit trail.

When should I transition a task to a deferred state instead of wont-fix?▼

To mark duplicate work items, link the redundant request to the existing ticket and transition its status to duplicate. This automatically attaches closing notes and relationship links to maintain a clean audit trail.