AI Project Orchestrator
Developer Official v1.0.0Multi-agent coordination workflow: structured push reviews, cross-repo drift detection, briefing generation, and a 3-way review loop (Architect → CTO → Orchestrator)
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 22 nodes
Orchestrator Cycle
Main orchestration workflow: push review → drift check → 3-way review loop → triage → issue management → briefing generation
Architect Review
Produces structured findings with code evidence, severity, classification, and confidence ratings
Briefing Generation
Reads git state, open issues, and cross-repo context to produce a slim BRIEFING.md per repo
CTO Response
Gate step — pressure-tests architect findings: accept, reject, or refine each finding
Issue Management
Updates GitHub Issues: comments with commit hashes, closes single-repo issues, removes labels for cross-repo
Push Review
Reviews a git push: diffs, commit messages, agent context — produces a structured summary and impact assessment
Schema Drift Check
Compares shared schemas and contracts across repos, flags divergence that could cause integration failures
Triage Decision
Converts review outcomes into GitHub Issues, watchpoints, or dismissals
Architect Findings
Produces structured review findings with code evidence, severity, classification, and confidence
Check Schema Drift
Compares shared schemas across repos and flags divergence with specific field-level evidence
CTO Pressure Test
Gate prompt — pressure-tests each architect finding and issues a pass/fail verdict for the review loop
Generate Briefing
Produces a slim BRIEFING.md for a repo agent session based on current state and review outcomes
Manage Issues
Executes GitHub Issue lifecycle actions: comments, closures, label updates, and new issue creation
Review Push
Analyses a git push and produces a structured summary with impact assessment
Triage Outcomes
Converts accepted review findings into GitHub Issues, watchpoints, or documented dismissals
LLM Service
Language model service for analysis, synthesis, and document generation
Briefing Protocol
Rules for context budget, priority ordering, cross-repo fact propagation, and the 140-line insight
Session Protocol
Agent session lifecycle: read briefing, work priority queue, commit, write .orchestrator-msg, push
BRIEFING.md Template
Template for generated briefings — the ~60 lines of session-specific work orders
CLAUDE.md Template
Template for repo-level agent instructions — the ~80 lines an agent reads at every session start
Post-Push Hook Script
Template for the post-push hook that reads .orchestrator-msg and logs to the orchestrator's inbox
Review Record Template
Structured template for the Architect → CTO → Orchestrator review record
Requirements 1 service, 1 permission, 1 data type
- LLM Service
- shell:execute
- source code
Security Passed
Detected
- Services:
- Permissions: shell:execute
- Data Handling:
Version history 1 release
Automated release v1.0.0
More from Developer
View all →Translation Pipeline
Translate content into multiple languages with quality review and comparative reporting
MCP PR Review Pipeline
Multi-agent pull request review via GitHub MCP — security, quality, and style agents with a human gate before posting
Bug Report Triage Pipeline
Classifies incoming bug reports, extracts structured details, and triages by severity using incident response guidelines