orchestrate

Automate end-to-end project orchestration from task classification to deployment.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/hidemaro-nsketch/_dotfiles --skill orchestrate-hidemaro-nsketch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/hidemaro-nsketch/_dotfiles/tree/main/pi/skills/orchestrate
Command: npx skills add https://github.com/hidemaro-nsketch/_dotfiles --skill orchestrate-hidemaro-nsketch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate provides a structured, automated end-to-end workflow for initiating and managing a full project lifecycle, reducing manual handoffs and ensuring consistency across phases.

Core Features & Use Cases

  • Tier classification and task scope determination.
  • Task-file creation (.claude/docs/decisions/task-{LINEAR_ID}-{feature}.md).
  • Sequential execution of startproject, team-implement, team-review, and deploy with gate controls.
  • Linear ID recognition and integration for ongoing task tracking.
  • Status management and progress reporting across all phases.

Quick Start

Provide a task description or a Linear ID to begin the full orchestration workflow.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I automate end-to-end project workflows from task classification to deployment?

Multi-phase development orchestration coordinates sequential execution of project initiation, team implementation, code review, and deployment stages with built-in gating rules and status management. It reduces manual handoffs by automatically classifying task tiers, creating task-files, and managing progress reporting across all phases.

Can I use Linear task IDs to trigger a full project orchestration workflow?

Yes, Linear task IDs are recognized and integrated for ongoing task tracking within the orchestration workflow. Providing a Linear ID allows the system to automatically determine task scope, create a corresponding task-file in the .claude/docs/decisions directory, and execute the coordinated workflow phases.

What is the best way to manage project gating rules between implementation and deployment phases?

Managing project gating rules is handled through sequential execution controls that enforce phase transitions between team implementation, team review, and deployment. The orchestration workflow applies these gate controls automatically, ensuring each phase meets requirements before progressing and maintaining status management throughout.

Do I need a Linear ID to start a project workflow, or can I provide a task description instead?

You do not need a Linear ID to start a project workflow; providing a standard task description is sufficient to begin the full orchestration process. The system performs tier classification and task scope determination from your description, generating the necessary task-files to initiate execution.

Why does my project workflow require tier classification before task-file creation?

Tier classification is required before task-file creation to determine the appropriate task scope and execution path for your project. This classification step ensures the subsequent phases of team implementation, review, and deployment are scaled and gated correctly based on the determined tier.