manage

Manage work item lifecycles through backend-specific adapters and status transitions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of manually tracking and updating work items across different backends by providing a unified, command-driven interface for lifecycle operations.

Core Features & Use Cases

  • Lifecycle Control: Easily archive, restore, or delete work items while maintaining state consistency.
  • Maintenance: Automatically identify and clean up stale work items that have been inactive for over a week.
  • Use Case: Use this skill to archive a completed feature branch task or to rename a work item title without losing its immutable ID history.

Quick Start

Use the manage skill to archive the work item with the ID feature-123.

Frequently Asked Questions about manage

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

FAQPage Schema
How do I automate work item lifecycle management across different backends?

Work item lifecycle management is automated by mapping abstract operations to backend-specific adapters, facilitating status transitions, renaming, and stale record cleanup within a defined project directory structure.

How do I archive a completed task without losing its immutable ID history?

To archive a completed task without losing its immutable ID history, use the command-driven interface to trigger lifecycle operations, which validates item existence and status before executing state changes.

Can I rename a work item title while maintaining state consistency?

Yes, you can rename a work item title while maintaining state consistency through the unified command interface, which validates item existence before executing the state change.

What is the best way to clean up stale work items that have been inactive?

The best way to clean up stale work items is to use the maintenance feature, which automatically identifies and cleans up records that have been inactive for over a week.

Does this workflow automation tool validate data before executing state changes?

Yes, this workflow automation tool ensures data integrity by validating item existence and status before executing any state changes or backend-specific adapter operations.

When should I not use automated lifecycle control for task management?

You should not use automated lifecycle control if your work items lack a defined project directory structure, as the adapter mapping and stale record cleanup depend on this organization to validate existence.