tasks

Converts specs and architecture into milestone-driven task files with dependencies and acceptance criteria.

41|4|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/etr/groundwork --skill tasks-etr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/etr/groundwork/tree/main/skills/tasks
Command: npx skills add https://github.com/etr/groundwork --skill tasks-etr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts product specifications and architecture into actionable implementation tasks that can be scheduled, tracked, and executed.

Core Features & Use Cases

  • Converts PRD and architecture into milestone-driven task plans that map to real delivery work.
  • Produces standardized TASK-xxx files per milestone with explicit goals, action items, dependencies, and acceptance criteria.
  • Integrates with next-task workflows to enable automated handoffs and progress tracking across teams.
  • Reads design-system context when present to surface frontend-design tasks and ensure consistency.

Quick Start

Provide a milestone-based task breakdown derived from the PRD and architecture, formatted for review.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I convert a PRD and architecture into actionable implementation tasks?

To convert a PRD and architecture into actionable implementation tasks, you use a milestone-driven task generation process that maps specifications to standardized TASK-xxx files with explicit goals, action items, dependencies, and acceptance criteria.

How do I generate milestone-based task breakdowns for software delivery?

Milestone-based task breakdowns are generated by parsing product specifications and architecture into milestone definitions, mapping dependencies, and producing standardized TASK-format items ready for scheduling and execution.

Can a task generation workflow map dependencies across design-system and frontend contexts?

Yes, task generation workflows can map dependencies across frontend-design tasks by reading design-system context when present, ensuring standardized task items maintain consistency across software projects and design-system contexts.

What is the best way to standardize task generation for next-task workflow integration?

Standardizing task generation for next-task workflow integration requires producing standardized TASK-format files per milestone, enabling automated handoffs and progress tracking across teams during execution.

Do I need architecture specifications to generate milestone-driven task plans?

Yes, you need product specifications and architecture inputs to generate milestone-driven task plans, as these inputs are converted into actionable implementation tasks that map to real delivery work.

What are the limitations of automated task generation from product specifications?

Automated task generation from product specifications is limited by the detail in the provided PRD and architecture, meaning insufficient design-system context or unclear milestone definitions will reduce the accuracy of dependency mapping and task output.