task-orchestration

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.