task-orchestration

Enforce documentation-first development with sequential task execution and progress tracking.

14|1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/jpoutrin/product-forge --skill task-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-orchestration
Source: https://github.com/jpoutrin/product-forge/tree/main/plugins/product-design/skills/task-orchestration
Command: npx skills add https://github.com/jpoutrin/product-forge --skill task-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves?

Implementing multi-step features or working through task lists often lacks systematic execution, documentation review, and consistent progress tracking, leading to errors, delays, and rework. This Skill enforces documentation-first development and systematic task execution.

Core Features & Use Cases

  • Documentation-First Enforcement: A mandatory principle that requires documentation review as the first sub-task for any coding task, ensuring best practices are followed.
  • Sequential Execution Protocol: Guidelines for working on one task at a time, completing all sub-tasks, and requiring user confirmation before proceeding.
  • Automatic Behaviors: Initializes task tracking, executes tasks systematically, updates progress mechanically (e.g., markdown checkboxes), and communicates progress clearly.
  • Quality Assurance Checklist: A checklist to ensure documentation compliance and other quality standards are met before marking any task complete.
  • Use Case: Starting a new feature implementation by first reviewing relevant documentation, systematically working through a task list, ensuring all sub-tasks are completed before moving on, or tracking and reporting progress on a complex task.

Quick Start

Use the task-orchestration skill to outline the 'Documentation-First Enforcement' principle for a new coding task.

Frequently Asked Questions about task-orchestration

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

FAQPage Schema
How do I enforce documentation-first development in my workflow?

Documentation-first development requires reviewing relevant docs as the first sub-task before coding. Task orchestration automates this enforcement by making documentation review mandatory, ensuring best practices are applied before implementation begins on any feature or multi-step work.

What's the best way to systematically execute a complex task list with progress tracking?

Systematic execution means completing one task at a time, finishing all sub-tasks, and requiring user confirmation before advancing. Task orchestration automates progress tracking with live updates—like markdown checkboxes—and ensures sequential completion, reducing errors and rework across feature implementations.

How can I track progress on multi-step feature implementation?

Progress tracking updates automatically as you complete each sub-task, with mechanical updates like checkbox marks. Task orchestration provides clear progress communication and QA checklists to verify documentation compliance and quality standards before marking tasks complete.

When should I use a documentation-first approach for task management?

Use documentation-first task management when starting new features, working through complex task lists, or coordinating QA and development workflows. It's essential when consistency, error prevention, and explicit sign-off before proceeding are required across team members.

Can task orchestration work with existing project management workflows?

Task orchestration applies to task lists, feature implementations, and any multi-step work requiring sequential execution. It integrates into existing developer workflows by adding documentation-first enforcement and automatic progress updates without replacing your current tools.

What quality checks does task orchestration enforce?

Task orchestration includes a QA checklist verifying documentation compliance and other quality standards before marking tasks complete. This ensures documentation review happens first, all sub-tasks finish, and explicit user confirmation occurs before proceeding to the next phase.