task-maker

Parse PRDs and generate Git-ready task files with push-level segmentation.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tazagame/claude-setting-v0.1-fsd-next-etc --skill task-maker-tazagame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-maker
Source: https://github.com/tazagame/claude-setting-v0.1-fsd-next-etc/tree/main/.claude/skills/task-maker
Command: npx skills add https://github.com/tazagame/claude-setting-v0.1-fsd-next-etc --skill task-maker-tazagame

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD-driven teams waste time translating requirements into actionable task units; this Skill automates that translation by creating Git-friendly push and subtask files from a PRD.

Core Features & Use Cases

  • PRD-driven task generation: analyzes a PRD to produce todo and done task files with push-level segmentation.
  • Structured task hygiene: enforces independent deployment units and 3-7 sub-tasks per push.
  • Workflow alignment: designed for PRD -> task-maker -> task-runner pipelines in Git-based projects.

Quick Start

Provide the PRD file path and Task-Maker will generate the todo/tasks structure and initial push tasks.

Frequently Asked Questions about task-maker

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

FAQPage Schema
How do I generate Git-ready task breakdowns from a PRD?

To generate Git-ready task breakdowns from a PRD, provide the PRD file path to automate the translation of requirements into structured todo and done task files with push-level segmentation.

How does push-level segmentation work for project management tasks?

Push-level segmentation for project management tasks works by enforcing independent deployment units, ensuring each Git push corresponds to a testable unit containing 3-7 structured subtasks.

Can I integrate PRD-driven task generation into my existing Git workflow?

Yes, you can integrate PRD-driven task generation into your Git workflow by running it within a PRD to task-runner pipeline to automatically generate structured task files for Git-based projects.

Do I need a specific PRD format to generate todo and done task structures?

You need a PRD file path to generate todo and done task structures, as the system parses the document to embed reference materials, images, and rules directly into the generated task files.

What is the best way to automate task generation for product development?

The best way to automate task generation for product development is using a PRD-driven pipeline that analyzes requirements and outputs structured todo files segmented into independent, testable push units.