Project Orchestrator
Purpose
The orchestrator turns a raw request into an approved plan by running the canonical pipeline in ../../system/ORCHESTRATION_WORKFLOW.md and delegating each stage to the right specialist skill. It owns gate enforcement, context discipline, and coordination — not the implementation of every domain.
When to Use
- Any new project, enhancement, feature, or multi-step request.
- Any request whose type or scope is unclear and must be classified and planned.
- Whenever multiple specialist skills must be sequenced and their outputs reconciled.
- Not needed for a trivial, single-file change with an obvious, approved scope — use the specific specialist skill directly.
Inputs
- The user request (verbatim) and any attached files, links, or repo.
- Current state in
../../projects/current/ (if a project is active) — CURRENT_STATUS.md first.
- The system rules in
../../system/ (canonical).
Discovery Questions
Ask only what blocks a correct plan (≈5 at most) — and in the same reply give a clearly labelled provisional apps + stack proposal under your stated assumptions, with how each answer would change it (../../system/ORCHESTRATION_WORKFLOW.md §4). Gate 2 still waits for the answers and the scenarios.
- What outcome does success look like, and for whom?
- Is there an existing codebase, or is this greenfield?
- Are there fixed constraints (platforms, deadlines, existing stack, compliance)?
- Does it handle money or sensitive PII (raises security/testing priority)?
- Any hard exclusions (things explicitly out of scope)?
Responsibilities
- Classify the request (delegate to
request-classification).
1a. Assemble the minimum sufficient context (delegate to context-engineering; ../../system/CONTEXT_MANAGEMENT_RULES.md) — scenarios first, a reason for every item, escalation only on a trigger.
- Inspect provided files and repository (delegate to
existing-project-audit when a codebase exists).
- Extract requirements (delegate to
requirements-analysis).
- Separate confirmed facts, assumptions, and questions — keep these three lists explicit.
4a. Specify the behavior change in Gherkin (delegate to
testing/gherkin-specifications; contract ../../system/GHERKIN_RULES.md). Does this change observable behavior? Yes or unsure → find existing scenarios, update or add them. No → record why and skip.
- Determine required applications (delegate to
application-selection).
- Recommend stack and alternatives (delegate to
stack-recommendation), with the version baseline from technology-governance — new project: latest stable, verified, compatible; existing project: the installed stack unless an upgrade trigger applies (../../system/TECHNOLOGY_GOVERNANCE_RULES.md).
- Wait for approval — Gate 2 (
../../system/QUALITY_GATES.md): the scenarios, plus apps and stack when they change. It fires for every behavior change.
- Design architecture from the approved scenarios (delegate to
architecture-design, repository-architecture).
- Select only relevant skills (
../../system/SKILL_SELECTION_RULES.md).
- Generate dynamic phases (delegate to
task-planning; ../../system/PHASE_GENERATION_RULES.md).
- Generate work items and tasks (
task-planning, feature-planning, bug-investigation, etc.).
- Add testing and security requirements (
testing-strategy, security-review).
- Propose Git and GitHub workflow (
git-workflow, github-repository).
- Stop before implementation until Gate 4 is approved.
- Hand off to tracking — on approval,
project-management assigns IDs and estimates and writes the roadmap and first week (../../system/PROJECT_MANAGEMENT_RULES.md).
- Route tracking requests — status, week planning/review, blockers, reports, and meetings (type project tracking) go straight to
project-management; bugs and mid-project additions go through its intake so they get an ID, a week, and a scope check.
The orchestrator coordinates specialists; it must not become the implementation agent for every domain.
Required Workflow
Request
→ request-classification
→ context-engineering → minimum sufficient context; escalate only on evidence
→ existing-project-audit (if code exists)
→ requirements-analysis → record confirmed / assumptions / questions
→ gherkin-specifications → the behavior change as scenarios (skip only if no observable change)
→ application-selection
→ stack-recommendation + technology-governance (versions, docs, keep-or-change)
── GATE 2: user approval (behavior + applications + stack) ──
→ architecture-design + repository-architecture
→ select relevant skills
→ dynamic phases + task-planning (+ feature/bug/refactor/migration planning)
→ testing-strategy + security-review requirements
→ git-workflow + github-repository proposal
── GATE 4: user approval (phases + tasks) ──
→ project-management: IDs, estimates, ROADMAP, PHASE-NN, WEEK-01, CURRENT_STATUS
→ STOP. Hand off to specialists for implementation, week by week.
Record stage and gate status in CURRENT_STATUS.md in ../../projects/current/ after each stage.
Re-entry: if CURRENT_STATUS.md exists, resume from it — never restart the pipeline. A project already past Gate 4 is in tracking: route the request by type instead of re-planning.
Decision Rules
- If requirements are ambiguous and the ambiguity changes the plan → ask; otherwise proceed with a stated assumption.
- If a codebase exists → audit before proposing changes.
- If work divides safely and parallelism helps → propose multi-agent (
../../system/MULTI_AGENT_RULES.md); else single-agent.
- If a specialist skill covers a stage → delegate; do not reimplement its logic inline.
- If a gate's inputs are unresolved → stop at the gate; do not "proceed to be helpful."
- If the request is a bug or new work on a tracked project →
project-management intake first (duplicate check, ID, priority, week); new scope that changes the approved plan returns here as a SCOPE CHANGE for Gate 4.
- If the request only asks about or updates progress →
project-management; no gates re-run.
Rules
.ai/ is canonical; never duplicate system rules — reference them.
- No application code, dependency install, or stack commitment before Gates 2 and 4.
- Keep the three lists (confirmed / assumptions / questions) visible through planning.
- Coordinate, don't monopolize: delegate domain work to specialists.
- Keep
../../projects/current/ current; be honest about done vs proposed.
Anti-Patterns
- Becoming the single agent that writes all code across all domains.
- Skipping classification or the audit and jumping to a stack.
- Presenting a stack before applications are selected and approved.
- Starting implementation before Gate 4.
- Loading every skill "to orchestrate" (violates token rules).
Validation Checklist
Definition of Done
A complete, approved plan exists in ../../projects/current/: classification, requirements (with the three lists), selected applications, approved stack, architecture, relevant skills, dynamic phases, tasks with acceptance criteria, testing/security requirements, and a proposed git/GitHub workflow — with Gates 2 and 4 approved and implementation not yet begun.
Related Skills
request-classification, existing-project-audit, requirements-analysis, application-selection, stack-recommendation, architecture-design, repository-architecture, task-planning, project-management, feature-planning, bug-investigation, refactor-planning, migration-planning, testing-strategy, security-review, git-workflow, github-repository, ai-output-review.
Related Knowledge
../../knowledge/ (project architecture/domain, once populated).
Related References
../../references/ topic folders relevant to the request (loaded selectively).
Context Loading Guidance
- Requires: the request,
../../system/OPERATING_RULES.md, ORCHESTRATION_WORKFLOW.md, QUALITY_GATES.md, and ../../projects/current/.
- Does not require: application source detail, unrelated references, historical work items, or every other skill's body.
- May load: the specialist skill for the current stage only.
- Stop when: the plan is approved (Gate 4) and handed to
project-management — do not implement.
Token Efficiency Guidance
Load specialists one stage at a time and unload them after. Summarize each stage's output into ../../projects/current/ rather than carrying full working context forward. Reference system rules by path; never paste them.
1---2name: project-orchestrator3description: Use as the lead skill for any non-trivial request. It drives the full request→approval pipeline (classify, audit, requirements, applications, stack, architecture, phases, tasks) and coordinates specialist skills. It plans and delegates; it does not implement every domain itself, and it stops before implementation until gates are approved. After approval it hands the plan to project-management for weekly tracking.4metadata:5 source: https://skillmd.com/skills/ahtishamshahzad/project-orchestrator6---78# Project Orchestrator910## Purpose1112The orchestrator turns a raw request into an approved plan by running the canonical pipeline in `../../system/ORCHESTRATION_WORKFLOW.md` and delegating each stage to the right specialist skill. It owns gate enforcement, context discipline, and coordination — not the implementation of every domain.1314## When to Use1516- Any new project, enhancement, feature, or multi-step request.17- Any request whose type or scope is unclear and must be classified and planned.18- Whenever multiple specialist skills must be sequenced and their outputs reconciled.19- **Not** needed for a trivial, single-file change with an obvious, approved scope — use the specific specialist skill directly.2021## Inputs2223- The user request (verbatim) and any attached files, links, or repo.24- Current state in `../../projects/current/` (if a project is active) — `CURRENT_STATUS.md` first.25- The system rules in `../../system/` (canonical).2627## Discovery Questions2829Ask only what blocks a correct plan (≈5 at most) — and in the same reply give a clearly labelled **provisional** apps + stack proposal under your stated assumptions, with how each answer would change it (`../../system/ORCHESTRATION_WORKFLOW.md` §4). Gate 2 still waits for the answers and the scenarios.30- What outcome does success look like, and for whom?31- Is there an existing codebase, or is this greenfield?32- Are there fixed constraints (platforms, deadlines, existing stack, compliance)?33- Does it handle money or sensitive PII (raises security/testing priority)?34- Any hard exclusions (things explicitly out of scope)?3536## Responsibilities37381. **Classify the request** (delegate to `request-classification`).391a. **Assemble the minimum sufficient context** (delegate to `context-engineering`; `../../system/CONTEXT_MANAGEMENT_RULES.md`) — scenarios first, a reason for every item, escalation only on a trigger.402. **Inspect provided files and repository** (delegate to `existing-project-audit` when a codebase exists).413. **Extract requirements** (delegate to `requirements-analysis`).424. **Separate confirmed facts, assumptions, and questions** — keep these three lists explicit.434a. **Specify the behavior change in Gherkin** (delegate to `testing/gherkin-specifications`; contract `../../system/GHERKIN_RULES.md`). Does this change observable behavior? Yes or unsure → find existing scenarios, update or add them. No → record why and skip.445. **Determine required applications** (delegate to `application-selection`).456. **Recommend stack and alternatives** (delegate to `stack-recommendation`), with the version baseline from `technology-governance` — new project: latest stable, verified, compatible; existing project: the installed stack unless an upgrade trigger applies (`../../system/TECHNOLOGY_GOVERNANCE_RULES.md`).467. **Wait for approval** — Gate 2 (`../../system/QUALITY_GATES.md`): the scenarios, plus apps and stack when they change. It fires for every behavior change.478. **Design architecture** from the approved scenarios (delegate to `architecture-design`, `repository-architecture`).489. **Select only relevant skills** (`../../system/SKILL_SELECTION_RULES.md`).4910. **Generate dynamic phases** (delegate to `task-planning`; `../../system/PHASE_GENERATION_RULES.md`).5011. **Generate work items and tasks** (`task-planning`, `feature-planning`, `bug-investigation`, etc.).5112. **Add testing and security requirements** (`testing-strategy`, `security-review`).5213. **Propose Git and GitHub workflow** (`git-workflow`, `github-repository`).5314. **Stop before implementation** until Gate 4 is approved.5415. **Hand off to tracking** — on approval, `project-management` assigns IDs and estimates and writes the roadmap and first week (`../../system/PROJECT_MANAGEMENT_RULES.md`).5516. **Route tracking requests** — status, week planning/review, blockers, reports, and meetings (type *project tracking*) go straight to `project-management`; bugs and mid-project additions go through its intake so they get an ID, a week, and a scope check.5657The orchestrator **coordinates specialists**; it must not become the implementation agent for every domain.5859## Required Workflow6061```62Request63 → request-classification64 → context-engineering → minimum sufficient context; escalate only on evidence65 → existing-project-audit (if code exists)66 → requirements-analysis → record confirmed / assumptions / questions67 → gherkin-specifications → the behavior change as scenarios (skip only if no observable change)68 → application-selection69 → stack-recommendation + technology-governance (versions, docs, keep-or-change)70 ── GATE 2: user approval (behavior + applications + stack) ──71 → architecture-design + repository-architecture72 → select relevant skills73 → dynamic phases + task-planning (+ feature/bug/refactor/migration planning)74 → testing-strategy + security-review requirements75 → git-workflow + github-repository proposal76 ── GATE 4: user approval (phases + tasks) ──77 → project-management: IDs, estimates, ROADMAP, PHASE-NN, WEEK-01, CURRENT_STATUS78 → STOP. Hand off to specialists for implementation, week by week.79```8081Record stage and gate status in `CURRENT_STATUS.md` in `../../projects/current/` after each stage.8283**Re-entry:** if `CURRENT_STATUS.md` exists, resume from it — never restart the pipeline. A project already past Gate 4 is in tracking: route the request by type instead of re-planning.8485## Decision Rules8687- If requirements are ambiguous and the ambiguity changes the plan → ask; otherwise proceed with a stated assumption.88- If a codebase exists → audit before proposing changes.89- If work divides safely and parallelism helps → propose multi-agent (`../../system/MULTI_AGENT_RULES.md`); else single-agent.90- If a specialist skill covers a stage → delegate; do not reimplement its logic inline.91- If a gate's inputs are unresolved → stop at the gate; do not "proceed to be helpful."92- If the request is a bug or new work on a tracked project → `project-management` intake first (duplicate check, ID, priority, week); new scope that changes the approved plan returns here as a `SCOPE CHANGE` for Gate 4.93- If the request only asks about or updates progress → `project-management`; no gates re-run.9495## Rules9697- `.ai/` is canonical; never duplicate system rules — reference them.98- No application code, dependency install, or stack commitment before Gates 2 and 4.99- Keep the three lists (confirmed / assumptions / questions) visible through planning.100- Coordinate, don't monopolize: delegate domain work to specialists.101- Keep `../../projects/current/` current; be honest about done vs proposed.102103## Anti-Patterns104105- Becoming the single agent that writes all code across all domains.106- Skipping classification or the audit and jumping to a stack.107- Presenting a stack before applications are selected and approved.108- Starting implementation before Gate 4.109- Loading every skill "to orchestrate" (violates token rules).110111## Validation Checklist112113- [ ] Request classified.114- [ ] Existing repo audited (or greenfield noted).115- [ ] Requirements extracted; confirmed/assumptions/questions separated.116- [ ] Behavior specified as approved-ready Gherkin scenarios (or "no observable change" recorded).117- [ ] Applications selected with justification.118- [ ] Stack recommended with alternatives.119- [ ] Gate 2 approval recorded.120- [ ] Architecture + repository structure designed.121- [ ] Relevant skills selected (not all).122- [ ] Dynamic phases + tasks generated.123- [ ] Testing + security requirements attached.124- [ ] Git/GitHub workflow proposed.125- [ ] Stopped before implementation pending Gate 4.126- [ ] After approval: roadmap, IDs, and the first week handed to `project-management`.127128## Definition of Done129130A complete, approved plan exists in `../../projects/current/`: classification, requirements (with the three lists), selected applications, approved stack, architecture, relevant skills, dynamic phases, tasks with acceptance criteria, testing/security requirements, and a proposed git/GitHub workflow — with Gates 2 and 4 approved and implementation not yet begun.131132## Related Skills133134`request-classification`, `existing-project-audit`, `requirements-analysis`, `application-selection`, `stack-recommendation`, `architecture-design`, `repository-architecture`, `task-planning`, `project-management`, `feature-planning`, `bug-investigation`, `refactor-planning`, `migration-planning`, `testing-strategy`, `security-review`, `git-workflow`, `github-repository`, `ai-output-review`.135136## Related Knowledge137138`../../knowledge/` (project architecture/domain, once populated).139140## Related References141142`../../references/` topic folders relevant to the request (loaded selectively).143144## Context Loading Guidance145146- **Requires:** the request, `../../system/OPERATING_RULES.md`, `ORCHESTRATION_WORKFLOW.md`, `QUALITY_GATES.md`, and `../../projects/current/`.147- **Does not require:** application source detail, unrelated references, historical work items, or every other skill's body.148- **May load:** the specialist skill for the **current** stage only.149- **Stop when:** the plan is approved (Gate 4) and handed to `project-management` — do not implement.150151## Token Efficiency Guidance152153Load specialists one stage at a time and unload them after. Summarize each stage's output into `../../projects/current/` rather than carrying full working context forward. Reference system rules by path; never paste them.