القائمة
Commit and inject a chunk into the orchestrator for background execution.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Collaboratively refine a high-level ambition into a set of chunk prompts.
Migrate the project's ACTIVE chunks to the present-tense, intent-owning standard. Audits each chunk's goal against the code it claims to govern; rewrites retrospective framing inline; logs over-claims that need operator triage; historicalizes chunks with no enduring intent. Designed for full-corpus migrations — fans out across many parallel sub-agents at 5 chunks per agent.
Create a new chunk of work and refine its goal. Use when the operator wants to start new intent-bearing work, chunk something, define a piece of work, or break work into a chunk.
Update code references in the current chunk and move both the PLAN.md and the GOAL.md to the ACTIVE state.
Wake an entity by loading its identity, memories, and operational context
Set up a project steward via interactive interview
| name | orchestrator-inject |
| description | Commit and inject a chunk into the orchestrator for background execution. |
Inject a chunk into the orchestrator for background execution, with a pre-flight commit check to ensure the chunk files are available in the worktree.
Input: $ARGUMENTS
Parse the arguments for an optional chunk name (positional).
Example invocations:
/orchestrator-inject my_chunk
/orchestrator-inject
If no chunk name is provided, run ve chunk list --current to resolve the
current IMPLEMENTING chunk. If that returns nothing, run ve chunk list and
look for FUTURE chunks. If still ambiguous, ask the operator which chunk to
inject.
Store the resolved chunk name as <chunk> for subsequent steps.
Run git status --porcelain docs/chunks/<chunk>/ to check if GOAL.md or
PLAN.md have uncommitted changes (modified, untracked, etc.).
If changes exist:
Stage the chunk files:
git add docs/chunks/<chunk>/GOAL.md docs/chunks/<chunk>/PLAN.md
Commit with a conventional message:
git commit -m "docs: commit <chunk> for orchestrator injection"
Report to the operator that files were auto-committed.
If the chunk files are already committed and clean:
Report that the chunk files are already committed and skip to Step 3.
If git is not available (the git status command fails):
Skip the commit step and proceed to Step 3. The orchestrator requires git for worktrees, so this scenario is unlikely but should be handled gracefully.
Run ve orch status. If the orchestrator is not running, start it with
ve orch start.
Run ve orch inject <chunk> and capture the output. Report success or
failure to the operator.
After successful injection, suggest:
Would you like me to monitor this chunk? I can run
/orchestrator-monitor <chunk>.
Do not auto-start monitoring unless the operator confirms.