skills.rest
kent013
kent013COMMUNITY
Explore all skills by this author →
WebsiteGitHub

zenigame-todo-close

Close or obsolete Alpha Factory TODO items by updating documentation trails.

Updated Apr 17, 2026
Search Tags:#automation#workflow#documentation#project-management#todo-management
One-click install
npx skills add https://github.com/kent013/zenigame-fx --skill zenigame-todo-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zenigame-todo-close
Source: https://github.com/kent013/zenigame-fx/tree/main/.claude/skills/_archived/zenigame-todo-close
Command: npx skills add https://github.com/kent013/zenigame-fx --skill zenigame-todo-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces manual overhead by reliably moving TODOs between Open, Closed, and Obsoleted states in the Alpha Factory workflow and updating the public TODO documents.

Core Features & Use Cases

  • Close an Open TODO by ID and remove it from the Open list, moving it to the Closed table with a timestamp.
  • Obsolete a TODO by ID and transfer it to the Obsoleted list, including a reason for future reference.
  • Validate inputs and provide clear progress updates in the docs to maintain auditable task history.

Use Case: When a TODO is completed or deprecated, this skill updates both the in-file Open/Conditional lists and the centralized Closed/Obsoleted sections to reflect current status.

Quick Start

Run the zenigame-todo-close skill with a todo_id to close the Open entry and update the Closed table; include --obsolete and --reason to move it to Obsoleted.

Frequently Asked Questions about zenigame-todo-close

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

FAQPage Schema
How do I close an open TODO item and update project documentation automatically?▼

To close an open TODO item, use the zenigame-todo-close skill with a todo_id to move it from the Open list to the Closed table with a timestamp, updating the documentation trail automatically.

What's the best way to mark a project TODO as obsolete with a reason?▼

To mark a project TODO as obsolete, run the skill with --obsolete and --reason parameters, transferring the item to the Obsoleted list with your specified reason for future reference.

How does TODO status transition work in the Alpha Factory workflow?▼

TODO status transition in the Alpha Factory workflow enables Open to Closed or Open/Conditional to Obsoleted state movements, validating arguments and updating both in-file lists and centralized documentation sections.

Can I track why a TODO was deprecated without manually editing the documentation?▼

Yes, you can track why a TODO was deprecated by using the --reason parameter during obsolescence, which automatically records your explanation in the updated public TODO documents.

Does closing a TODO validate inputs before updating the task history?▼

Yes, closing a TODO validates all input arguments before updating the documentation, ensuring only properly identified items transition states to maintain an auditable task history.

When should I obsolete a conditional TODO instead of closing it?▼

You should obsolete a conditional TODO instead of closing it when the task is deprecated or no longer relevant, using the --obsolete flag to transfer it to the Obsoleted list rather than the Closed table.

Related Skills

Explore More Product & Management Skills→
kent013kent013

zenigame-fx-todo-close

Move Alpha Factory TODO entries between Open and Closed sections with validation.

Community
Intermediate
sssemilsssemil
2

task-worker

Automate task processing from workspace/tasks/todo/ through in-progress and done states.

Community
Advanced
kent013kent013

zenigame-fx-todo-add

Validate design document presence before adding Alpha Factory TODOs.

Community
Intermediate
ChrisFmlycChrisFmlyc

close

Guide users through closing work items with multiple closure options.

Community
Advanced