orchestrator-pack

Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.

QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.

Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.

Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.

Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.

Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.

Review design.md and tasks.yaml for completeness and quality. Use when reviewing a design before implementation.

Produce design.md and tasks.yaml from discovery. Use when designing a feature, drafting an approach, or breaking work into tasks.

Diagnose a bug and write a diagnosis brief. Use when investigating failures, root-causing bugs, or starting a bugfix.

Generate visual diagrams (flowchart, sequence, class, state, ER, C4) via draw.io. This skill should be used when the user says 'draw a diagram', 'visualize the architecture', 'create a flowchart', 'sequence diagram for X', 'show me the class hierarchy', or asks for any visual representation of code or systems.

Run the unified orchestrator health check. Use when user says "doctor", "/doctor", "health check", "check orchestrator health", or before debugging dispatch/contract errors.

Remove AI writing patterns from text. This skill should be used when the user says 'humanize', 'make this sound human', 'remove AI patterns', 'rewrite naturally', or asks to edit text to sound less AI-generated.

Brainstorm ideas, explore designs, and build a prioritized backlog. Use when the user wants new feature ideas, backlog management, or says "ideate", "brainstorm", "what should we build".

Implement pending tasks from tasks.yaml (or derive from ticket context). Use when coding a change, implementing a feature, or executing implementation tasks.

Reflect on a completed run and propose workflow/prompt improvements. Use when learning from a run, writing retros, or improving workflows.

This skill should be used when the user asks to "create a Linear issue", "file a ticket", "open a Linear ticket", "update a Linear issue", "check a Linear ticket", "add a label to a ticket", "assign an issue", "close a ticket", or any time a workflow step needs to create/read a Linear ticket. Also use when reading or writing ticket_id in state.yaml.

Workflow router — detects intent and loads the right schema. This skill should be used when the user says 'orchestrate', 'start a feature', 'fix a bug', or describes development work that maps to a workflow type (feature, bugfix, autopilot).

Use PAL MCP to invoke external CLI models (Codex, Claude) for cross-model code review, artifact review, consensus, and deep analysis. Triggers when you need an independent model's perspective — code reviews, spec reviews, architectural debates, or second opinions. Also use when the user says "ask codex", "cross-model review", "get a second opinion", or "use PAL".

Run the patch workflow — implement a small, well-scoped change with no design phase. Use when the ticket already has a clear implementation path and design artifacts are not needed. Skips explore, design, and design-review.

Set up portless named .localhost dev URLs for any project. Detects project type (static, Vite, Next.js, Express, etc.), adds the dev script with portless, installs dependencies, and verifies the setup works. Use when adding a new project to the portless dev environment or when the user says "add portless", "set up dev server", "named localhost", or "portless".

Phase quality review against the project quality bar. Use when reviewing implementation quality, scoring a phase, or gating merge readiness.

QA failed — move ticket back to In Progress. Branch is retained; developer resumes work on it. Use when QA finds issues that need fixes before re-review.

Run the design workflow schema (explore → design → design-review). Prefer /orchestrate --schema design. The design skill-step lives under config/steps/design.

Run the implement workflow schema. Prefer /orchestrate --schema implement. The implement skill-step lives under config/steps/implement.

Create feature specification via the orchestrate workflow. Delegates to /orchestrate for init and a full workflow run. Use when the user says 'specify', 'create spec', 'write specification'.

Systematic debugging — reproduce, trace, hypothesize, verify. This skill should be used when the user says 'debug this', 'why is this failing', 'trace the error', 'find the root cause', or encounters a bug, test failure, or unexpected behavior that needs methodical investigation.

UX design critique with staff-level evaluation. Use when reviewing UI/UX, critiquing designs, or before shipping a UI feature.

Design and validate UI/UX through prototyping and critique. Use when designing interfaces or producing UX artifacts.

Create orchestrator workflows from any user goal. Web-searches how similar real-world workflows are structured, breaks them into steps, classifies each step as shell (script) or prompt (charter directory), then scaffolds config/workflows and config/steps. Use when the user asks to create a workflow, design a pipeline, build a multi-step process (course creator, content, dev, ops, research), or says workflow-creator or custom orchestrator schema.