zenigame-fx-todo-close

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates the lifecycle management of Alpha Factory TODOs by closing or obsoleting tasks, moving them between Open/Conditional and Closed/Obsoleted lists, and updating the documentation accordingly.

Core Features & Use Cases

  • Close TODO items from docs/alpha_factory/TODO.md and move them to docs/alpha_factory/TODO-closed.md as Closed.
  • Obsolete TODO items by moving them to the Obsoleted section with a mandatory reason.
  • Validate inputs and provide clear errors when required fields are missing, ensuring auditability and traceability.

Quick Start

Run the owner command to close a specific TODO by its ID, optionally marking it as obsolete with a reason.

Frequently Asked Questions about zenigame-fx-todo-close

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

FAQPage Schema
How do I automate closing TODO items in markdown documentation?▼

Automating TODO closure moves entries from open lists to a closed markdown file. This skill targets docs/alpha_factory/TODO.md, validates inputs, and moves items to TODO-closed.md to update documentation accordingly.

How do I mark a TODO item as obsoleted instead of closed?▼

Obsoleting a TODO moves it to a dedicated section in the closed markdown file. This skill enforces that obsolete actions require a mandatory reason to ensure auditability and traceability for the task.

What happens if required fields are missing when closing TODO tasks?▼

Missing required fields trigger validation errors that prevent the TODO task from closing. This skill validates inputs during lifecycle management and provides clear errors to ensure documentation traceability.

Do I need any external dependencies to manage my TODO workflow?▼

No external dependencies are needed to manage the TODO workflow. This skill operates independently to automate lifecycle management by validating inputs and moving entries between markdown documentation files.

Can I move conditional TODO items to a closed status in bulk?▼

Moving conditional TODO items to closed status requires targeting specific entries in markdown files. This skill automates moving items between Open/Conditional and Closed/Obsoleted sections, updating the documentation accordingly.