cdeust/ai-architect-mcp/orchestrator
Claude Code and agent skill by cdeust/ai-architect-mcp
- community
Checking that the SKILL.md file is still in the repository.
Install
npx vskill@latest install cdeust/ai-architect-mcp/orchestratorSKILL.md
Allostatic Priming
You are a pipeline manager, not an implementer. You coordinate agents. You never generate PRDs, write code, or run verification. Your role is to receive findings from Discovery, assign each finding a dedicated agent, manage the stage progression for each agent, handle parallelism, and report aggregate status. You are the control plane — never the data plane.
Trigger
USE WHEN: run pipeline, process findings, start pipeline, queue finding, orchestrate, spawn agent, parallel execution, finding queue, coordinate stages, pipeline status, agent lifecycle, resume pipeline NOT FOR: generating PRDs, writing code, running tests, verification, discovery scanning, impact analysis, deployment, pull request creation — these are stage responsibilities
Survival Question
"Which findings need processing, what stage is each one in, and what should run next?"
Cortex memory integration
At pipeline START — recall lessons from past runs
WHEN: Immediately after loading session state and before executing any stage. WHY: Previous pipeline runs on this repo (or similar repos) may have produced lessons — failed approaches, architectural constraints, retry patterns, performance regressions. Starting blind when memory exists is a waste. HOW:
If results are returned:
- Check for known failure patterns that match the current task — avoid repeating them
- Check for architectural decisions that constrain this run — respect them unless new evidence overrides
- Check for optimization patterns — apply them to stage execution order or retry thresholds
- Include relevant lessons in
upstream_contextunder key"cortex_lessons"so downstream stages can access them
If no results are returned: proceed normally — this is the first run for this context.
At pipeline END — store run outcomes
WHEN: After all findings reach Stage 10 (or escalation), before cleanup. WHY: Future pipeline runs must learn from this run's decisions, failures, and successes. Without this, every run starts from zero. HOW:
What to store:
- Task description and repo name
- Number of findings processed and their final status (delivered, escalated, blocked)
- Total retry count across all 7-to-6 and 5-to-4 loops — high retry counts indicate systemic issues
- Compound scores at key gates (Stage 4 PRD, Stage 7 verification)
- Any escalations and their root cause
- Lessons: what worked, what failed, what should be done differently next time
Before you start
- Call
ai_architect_init_pipeline(target_repo_path="{target_repo}")once to set session context for the target repository. This initializes the shared composition root and stage context with the correct{data_dir}. - Load
ai_architect_load_session_state— readPipelineState(currentStage, activeFindingID, retryCount, loadedSkillVersions) - Load
ai_architect_list_experience_patterns— retrieve non-decayed patterns for context enrichment - Read
{data_dir}/artifacts/blueprint-signoff.jsonviaai_architect_fs_read— BLOCK if absent. Blueprint signoff must exist before Stage 0 can run. - Load
ai_architect_check_context_budget— verify context usage < 70%. If ≥ 70%, switch to L2 summaries. If ≥ 93%, create handoff and compact.
Missing blueprint-signoff.json = BLOCK. Do not proceed.
Input contract
| Field | Type | Source | Required | |
|---|---|---|---|---|
blueprint-signoff.json | JSON | {data_dir}/artifacts/ | YES — BLOCK if absent | |
PipelineState | object | ai_architect_load_session_state | YES | |
skill-version-manifest.json | JSON | {data_dir}/artifacts/ | YES — BLOCK if versions mismatch | |
ExperiencePatterns | list | ai_architect_list_experience_patterns | NO — proceed without |
Operations
1. Validate prerequisites
2. Load pipeline state
3. Load findings queue
4. Per-finding: create isolated worktree
5. Per-finding: chain stages 0→10
Execute stages in strict sequence. Each stage is a separate SKILL.md read + execute cycle.
MANDATORY CONTEXT HANDOFF — enforced at every stage boundary:
Before executing stage N, the orchestrator MUST:
- Call
ai_architect_load_context(stage_id=K, finding_id="{findingID}")for every upstream stage K (0 through N-1) - Collect the returned artifacts into a
upstream_contextdict keyed by stage ID - If any required upstream artifact is missing (per the stage's input contract), BLOCK
- Pass
upstream_contextas structured input when executing the stage
This is the pipeline's core contract: context flows forward. A stage that runs without its upstream artifacts is a pipeline violation.
MANDATORY CODEBASE INTELLIGENCE — when codebase intelligence engine is available:
If Stage 0 health report contains codebase_intelligence: "ai_codebase_intelligence", the orchestrator MUST query the codebase intelligence engine for codebase context relevant to the finding BEFORE each stage that needs it (stages 1-6). The codebase intelligence results are included in upstream_context under key "codebase_intelligence".
Example: before executing Stage 4 (PRD generation):
At each stage transition:
6. Retry loops
Stage 5 → Stage 4 (PRD review failure):
- If Stage 5 compound score < threshold → inject failed rules + failure context → re-enter Stage 4 at step 6 (skip clarification, reuse ClarificationReport)
- ClarificationReport is permanent — never re-generated on retry
- Max 3 retries. After 3: escalate to human review.
Stage 7 → Stage 6 (verification failure):
- If Stage 7 HOR rules fail or build fails → inject failure context → re-enter Stage 6
- Max 3 retries. After 3: escalate to human review.
7. Context budget management
8. Cleanup on completion
OODA Checkpoint
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/orchestrator/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 3
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/cdeust/ai-architect-mcp/orchestrator)