agent-project-orchestrator

Define project contracts and orchestrate agent-based lifecycles for Claude and Codex environments.

18|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dachent/skills --skill agent-project-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-project-orchestrator
Source: https://github.com/dachent/skills/tree/main/archive/agent-project-orchestrator
Command: npx skills add https://github.com/dachent/skills --skill agent-project-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This package provides a historical reference for a durable project-control model designed to move projects from a verified current state to an explicit target state through evidence-backed increments.

Core Features & Use Cases

  • Project Orchestration: Defines a methodology for managing project state, backlog, and sprint boundaries.
  • Scenario Resolution: Includes logic to route project execution based on specific harness/model pairs like Claude Code or Codex.
  • Historical Reference: Serves as a design record for adversarial architecture reviews and project-control methodologies.

Quick Start

Please refer to the repository documentation to use the maintained agent-project-scaffold instead of this archived package.

Frequently Asked Questions about agent-project-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does agent-based project orchestration manage project state transitions?

Agent-based project orchestration manages project state transitions by defining project contracts and reconstructing state to move projects toward an explicit target state through evidence-backed increments.

What is scenario-based orchestration for Claude and Codex execution environments?

Scenario-based orchestration routes project execution logic based on specific harness and model pairs, such as Claude Code or Codex, applying deterministic resolution for execution policies and quality boundaries.

How do I design a control-plane architecture for managing agent project lifecycles?

Designing a project control-plane architecture involves defining methodologies for project state, backlog, and sprint boundaries, supported by deterministic execution policies for agent-based environments.

When do I need deterministic resolution logic for harness-specific execution policies?

Deterministic resolution logic is needed when routing project execution across different harness and model pairs to enforce strict quality control boundaries and execution policy compliance.

Does the archived agent-project-orchestrator package support current project scaffolding?

The archived package does not support current scaffolding; it serves as a historical reference for adversarial architecture reviews, directing users to the maintained agent-project-scaffold instead.

Can I use project control-plane design for adversarial architecture reviews?

Project control-plane design serves as a historical design record specifically for conducting adversarial architecture reviews and validating project-control methodologies.