implement

# Implement End-to-end workflow for taking MCP work items from queue to PR. This skill composes the schema-driven planning (spec-quality), implementation, review (review-quality), and git/PR workflow into a single pipeline. **Usage:** - `/implement <item-id>` — work on a specific item - `/implement` — with context about what to work on - Can process single items or multiple items in batch --- ## Step 1 — Assess the Work Load the item(s) and determine the execution tier and interaction mode. For each item, call `get_context(itemId=...)` to understand: - Current role and gate status - Schema tag (feature-implementation, bug-fix, etc.) - Existing notes already filled - Dependencies and blocked status **Execution tier** — classify by this table (canonical source shared with the Workflow Orchestrator output style; edit the fragment, not this copy): <!-- BEGIN GENERATED:tier-classification | source: claude-plugins/task-orchestrator/output-styles/_fragments/tier-classification.md · regen: node claude-plugins/task-orchestrator/output-styles/generate.mjs --> | Criteria | Tier | Pipeline | |----------|------|----------| | 1-2 files, known fix, no migration/new API | **Direct** | Orchestrator edits, tests, reviews inline | | 3-10 files, single logical unit, clear or explorable scope | **Delegated** | Single subagent, separate review agent | | 11+ files, multiple independent work streams, dependency edges | **Parallel** | Worktree agents, full pipeline | **Force-UP signals** (bu...