Menu
Batch-submit all FUTURE chunks to the orchestrator.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-submit-future |
| description | Batch-submit all FUTURE chunks to the orchestrator. |
This command batch-submits all FUTURE chunks to the orchestrator, with guards for uncommitted changes and already-running chunks.
Follow these steps in order:
Check the orchestrator status:
ve orch status
If the orchestrator is not running, start it:
ve orch start
List all chunks and filter for FUTURE status:
ve chunk list | grep "\[FUTURE\]"
From the output, identify chunks marked with [FUTURE]. If there are no FUTURE
chunks, inform the user and stop.
Query the orchestrator for already-running work:
ve orch ps --json
Parse the JSON output to get the list of chunk names currently in the orchestrator. Note their status (RUNNING, DONE, etc.).
For each FUTURE chunk identified in Step 2, check eligibility:
4a. Check for uncommitted changes:
git status --porcelain docs/chunks/<chunk_name>/
If this command produces any output, the chunk has uncommitted changes and cannot be submitted. Add it to the "skipped (uncommitted)" list and continue to the next chunk.
4b. Check orchestrator presence:
Compare the chunk name against the work units from Step 3. If the chunk is already in the orchestrator (regardless of status), add it to the "skipped (already in orchestrator)" list with its current status and continue to the next chunk.
4c. Submit eligible chunks:
If the chunk passes both checks (committed AND not in orchestrator), submit it:
ve orch inject <chunk_name>
Add it to the "submitted" list.
Present a summary to the user organized by outcome:
Submitted: (chunks successfully injected)
Skipped (uncommitted changes): (cannot submit until committed)
Skipped (already in orchestrator): (no action needed)
If all FUTURE chunks were skipped, explain why no chunks were submitted.