Menu
Create a chunk PLAN.md file containing the technical breakdown for the work in that chunk's GOAL.md file.
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 | chunk-plan |
| description | Create a chunk PLAN.md file containing the technical breakdown for the work in that chunk's GOAL.md file. |
Determine the currently active chunk by running ve chunk list --current. We
will refer to the directory returned by this command below as
Run ve chunk suggest-prefix <chunk_name> (using just the directory name,
not the full path) to check if this chunk should be renamed for better
semantic clustering. If a prefix is suggested:
{prefix}_* chunks. Consider renaming to {prefix}_{current_name}?"mv to rename the chunk directoryve chunk cluster-list to see how large the
new cluster is. If it has 5+ chunks with no subsystem documentation,
suggest the operator consider /subsystem-discover to capture invariantsStudy /GOAL.md
In light of the broader project objective in docs/trunk/GOAL.md and the guiding architecture decisions in docs/trunk/DECISIONS.md and the existing codebase: Complete the template in /PLAN.md with a detailed sequence of steps that will achieve the goal. If a chunk is part of a narrative (docs/narratives/[goal.frontmatter.narrative]/OVERVIEW.md), it may be valuable to read about the broader picture that the goal fits into.