zenigame-todo-add

Add validated tasks to the Alpha Factory TODO list after verifying design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Alpha Factory teams often need to track design tasks; this tool ensures that new TODO entries are created only when conceptual and detailed designs exist, reducing missing references and miscommunication.

Core Features & Use Cases

  • Validates presence of conceptual-design.md and detailed-design.md in the specified devnotes directory before adding.
  • Creates a structured TODO entry with id, title, theme, summary, priority, mode, and a link to the design location, along with a timestamp.
  • Supports conditional targeting and integrates with the local TODO workflow to streamline project management.

Quick Start

Invoke the skill with a title, theme, summary, and devnotes_dir to create a new TODO entry.

Frequently Asked Questions about zenigame-todo-add

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

FAQPage Schema
How do I add a validated task to a TODO list when design docs are missing?

Adding a validated task to a TODO list requires verifying conceptual-design.md and detailed-design.md exist first. This tool automates task creation by checking your devnotes directory, preventing new entries when required design documents are absent.

How do I structure a TODO entry with priority, theme, and mode for project management?

Structuring a TODO entry with priority, theme, and mode involves specifying these fields during creation. The tool enforces validation rules for summary length, priority defaults, and mode options, recording metadata and linking to the design location for traceability.

What's the best way to automate task creation from devnotes to ensure traceability?

Automating task creation from devnotes ensures traceability by linking the TODO entry directly to the design location. This approach validates prerequisites and records timestamps automatically, reducing missing references and miscommunication across team workflows.

Does this task validation approach support conditional targeting in project management?

Task validation does support conditional targeting within the local TODO workflow. You can specify optional conditional targets when invoking the tool, which validates inputs and integrates the conditions into the structured TODO entry metadata.

Why does adding a TODO task fail when conceptual or detailed design files are absent?

Adding a TODO task fails because validation requires conceptual-design.md and detailed-design.md to exist in the specified devnotes directory. The tool enforces these input validation rules and returns clear error messages when the prerequisite files are missing.

Can I use automation to enforce input validation rules for TODO task fields?

You can use automation to enforce input validation rules for TODO task fields including theme, summary length, priority defaults, and mode options. The tool validates these parameters upon invocation and provides clear error messages for any invalid inputs.