orchestrator-inject

Inject a chunk into the orchestrator after verifying GOAL.md and PLAN.md commits.

3|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill orchestrator-inject
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-inject
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/orchestrator-inject
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill orchestrator-inject

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit and inject a chunk into the orchestrator for background execution, enabling asynchronous processing of chunk tasks.

Core Features & Use Cases

  • Pre-flight commit check: verifies that GOAL.md and PLAN.md for the target chunk are committed before injection.
  • Chunk resolution: determines the correct target chunk by resolving the current implementing chunk or listing FUTURE chunks.
  • Orchestrator interaction: ensures the orchestrator is running and performs the injection, then reports status to the operator.
  • Monitoring prompt: offers to initiate chunk monitoring after a successful injection.

Quick Start

Provide the chunk name to inject via the orchestrator-inject command and let the orchestrator handle background execution.

Frequently Asked Questions about orchestrator-inject

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

FAQPage Schema
How do I inject chunks into a background orchestrator for asynchronous workflow automation?

Background orchestration injects chunks for asynchronous processing by verifying GOAL.md and PLAN.md are committed before starting the orchestrator. This enables automated background execution of chunk tasks.

How do I ensure my git workflow commits are checked before starting background execution?

Pre-flight commit checks validate git availability and ensure GOAL.md and PLAN.md are committed before background execution starts. The system reports success or failure to the operator if checks fail.

Do I need git installed to automate chunk injection and background execution?

Git is required for chunk injection because the skill validates git availability and ensures GOAL.md and PLAN.md are committed before starting the orchestrator for background execution.

What is the best way to resolve which chunk to inject for background orchestration?

Chunk resolution determines the correct target by resolving the current implementing chunk or listing FUTURE chunks. This identifies the proper chunk before verifying its committed state and injecting it.

Can I monitor background execution status after successfully injecting a chunk?

After a successful injection, the system offers a monitoring prompt to initiate chunk monitoring. This allows you to track the asynchronous processing of the injected chunk tasks within the orchestrator.