Back to Skills

orchestrate

verified

End-to-end project orchestration from idea to implementation. Use when user wants to build a complete project, implement an MVP, or says "build this app/feature". Coordinates product-design, architecture, task-decomposition skills, then delegates to task-spec-generator, task-implementer, and code-reviewer agents for execution. Resumable—introspects filesystem and git state to pick up where it left off if interrupted.

View on GitHub

Marketplace

porkbutts-n-taters

Porkbutts/porkbutts-n-taters

Plugin

vibe-coding

Repository

Porkbutts/porkbutts-n-taters
1stars

skills/orchestrate/SKILL.md

Last Verified

January 21, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/Porkbutts/porkbutts-n-taters/blob/main/skills/orchestrate/SKILL.md -a claude-code --skill orchestrate

Installation paths:

Claude
.claude/skills/orchestrate/
Powered by add-skill CLI

Instructions

# Orchestrate

Coordinate the full development lifecycle: requirements → architecture → tasks → implementation → review → merge.

## Prerequisites Check

Before starting, verify which artifacts exist:

| Artifact | Path | If Missing |
|----------|------|------------|
| PRD | `docs/PRD.md` | Invoke `/product-design` skill |
| Architecture | `docs/ARCHITECTURE.md` | Invoke `/architecture` skill |
| Tasks | `docs/TASKS.md` | Invoke `/task-decomposition` skill |

Use a general agent (opus) to invoke each missing skill in order. Proceed automatically—each skill handles its own user confirmation.

## Resume Detection

On startup, introspect state to determine where to resume. This makes the skill idempotent—safe to run repeatedly.

### Check sequence:

```bash
# 1. Check planning artifacts
ls docs/PRD.md docs/ARCHITECTURE.md docs/TASKS.md 2>/dev/null

# 2. Check task specs
ls docs/tasks/task-*.md 2>/dev/null

# 3. Check for in-progress worktrees
git worktree list | grep '.worktrees/task-'

# 4. Check for unmerged task branches
git branch --list 'task/*'

# 5. Parse TASKS.md for progress markers
grep -E '^\s*- \[(x| |🚧)\]' docs/TASKS.md
```

### Resume logic:

| State | Resume Point |
|-------|--------------|
| No `docs/PRD.md` | Start Phase 1 |
| No `docs/ARCHITECTURE.md` | Phase 1: architecture skill |
| No `docs/TASKS.md` | Phase 1: task-decomposition skill |
| No `docs/tasks/*.md` | Start Phase 2 |
| Task marked `🚧` in TASKS.md | Resume that task (check worktree exists) |
| Worktree exists but task not marked | Mark as `🚧`, resume implementation |
| Task `[x]` but branch still exists | Just needs merge/cleanup (step 7) |
| Branch exists, worktree missing | Recreate worktree, resume |
| All tasks `[x]`, no task branches | Complete—nothing to do |

### In-progress task recovery:

If a worktree exists at `.worktrees/task-<id>`:
1. Check if branch has uncommitted changes → continue implementation
2. Check if branch has commits ahead of main → needs review or merge
3. Ch

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
5470 chars