skills.rest
AI-Driven-Highspeed-Development
AI-Driven-Highspeed-DevelopmentOFFICIAL
Explore all skills by this author →
GitHub

orch-expedition

Coordinate the 8-phase expedition pipeline to export ADHD agents with user confirmations and git checkpoints.

Updated Feb 1, 2026
Search Tags:#workflow#verification#agents#registry#export#orchestrate#expedition
One-click install
npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill orch-expedition
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orch-expedition
Source: https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3/tree/main/modules/dev/instruction_core/data/skills/orch-expedition
Command: npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill orch-expedition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the 8-phase expedition pipeline to export ADHD agents to external projects, ensuring target environments stay pristine and sidecars manage infrastructure.

Core Features & Use Cases

  • Orchestrates all 8 expedition phases with defined stop points and explicit user confirmations.
  • Enforces a Layered architecture (L1 Bundle) separating sidecar and target responsibilities, preventing target pollution.
  • Creates and configures per-target registry managers and MCP modules, coordinating artifact creation and verification for external projects.

Quick Start

Trigger an expedition export by specifying the target path and let the system walk through all eight phases with user confirmations.

Frequently Asked Questions about orch-expedition

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

FAQPage Schema
How do I orchestrate agent exports to external projects without polluting the target environment?▼

Expedition exports use a layered architecture separating sidecar and target responsibilities, ensuring target environments stay pristine while sidecars manage infrastructure during agent delegation.

What are verification gates in an expedition pipeline and when are they required?▼

Verification gates are mandatory stop points within the 8-phase expedition pipeline that require explicit user confirmations and git checkpoints before proceeding to subsequent export phases.

How do I generate registry managers and MCP modules for specific target paths?▼

Trigger an expedition export by specifying the target path, and the system automatically creates and configures per-target registry managers and MCP modules while coordinating artifact creation and verification.

Does the expedition pipeline support sidecar environments for infrastructure management?▼

Yes, the expedition pipeline explicitly supports sidecar environments to manage infrastructure, enforcing a layered L1 Bundle architecture that prevents target pollution during end-to-end agent exports.

Can I enforce user confirmations and git checkpoints during an end-to-end agent export?▼

Yes, the expedition pipeline orchestrates all eight phases with defined stop points, enforcing mandatory user confirmations and git checkpoints at verification gates throughout the export process.

Related Skills

Explore More Software Engineering Skills→
LerianStudioLerianStudio
205

pre-dev-prd-creation

Generate a complete PRD with problem discovery, user stories, and success metrics.

Official
Basic
AI-Driven-Highspeed-DevelopmentAI-Driven-Highspeed-Development

expedition

Export ADHD Framework agents and instructions to external projects.

Official
Advanced
charl-krugercharl-kruger
5

building-mcp-server-on-cloudflare

Build MCP servers on Cloudflare Workers with OAuth authentication.

Community
Advanced
gtpgg1013gtpgg1013

ultrawork

Parallelize independent tasks across multiple agents with automatic model routing.

Community
Advanced