moai-alfred-todowrite-pattern

Auto-initialize TodoWrite from Plan agent outputs with status transitions.

1|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/kivo360/quickhooks --skill moai-alfred-todowrite-pattern-kivo360
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-alfred-todowrite-pattern
Source: https://github.com/kivo360/quickhooks/tree/main/.claude/skills/moai-alfred-todowrite-pattern
Command: npx skills add https://github.com/kivo360/quickhooks --skill moai-alfred-todowrite-pattern-kivo360

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TodoWrite auto-initialization and task-tracking patterns to bootstrap and maintain progress across projects.

Core Features & Use Cases

  • Auto-initialization from Plan output
  • Status tracking for tasks (pending, in_progress, completed)
  • Smooth integration with Alfred commands
  • Lightweight, batch-friendly workflow

Quick Start

Run Skill("moai-alfred-todowrite-pattern") to auto-initialize TodoWrite from a Plan output and start tracking.

Frequently Asked Questions about moai-alfred-todowrite-pattern

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

FAQPage Schema
How do I auto-initialize task tracking from planning output?

Auto-initialization from plan output bootstraps TodoWrite directly from Plan agent results, eliminating manual task entry and ensuring consistent task-tracking format across planning and execution phases within Alfred workflows.

Can I automate task status transitions through the workflow lifecycle?

Automated status transitions move tasks from pending to in_progress to completed as they flow through planning, execution, and reporting phases, maintaining consistent progress tracking without manual status updates.

How do I integrate task tracking with Alfred's 4-Step Workflow?

TodoWrite pattern integration within Alfred contexts accepts Plan agent outputs directly, auto-populates task data in TodoWrite format, and maintains backward compatibility with manual TodoWrite usage across workflow steps.

What format does task tracking expect from Plan output?

Task tracking consumes structured Plan agent outputs and converts them into TodoWrite format automatically, applying consistent schema for task fields, status values, and metadata required for batch-friendly workflow execution.

Does this pattern work with existing manual task tracking?

Backward compatibility preserves manual TodoWrite usage while enabling auto-initialization from Plan output, allowing teams to transition gradually from manual to automated task tracking without breaking existing workflows.