chunk-complete

Finalize a chunk by updating code references and setting GOAL.md and PLAN.md to ACTIVE.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the finalization of a chunk by updating code references and ensuring GOAL.md and PLAN.md are set to ACTIVE.

Core Features & Use Cases

  • Identify the currently active chunk using ve chunk list --current.
  • Locate the chunk's GOAL.md and PLAN.md and capture code_references with symbolic paths.
  • Validate and apply the finalization workflow, pushing status updates and generating traceable metadata.

Quick Start

Run ve chunk complete <chunk_id> to finalize the current chunk and move its GOAL.md and PLAN.md to ACTIVE.

Frequently Asked Questions about chunk-complete

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

FAQPage Schema
How do I finalize a workflow chunk and move GOAL.md and PLAN.md to ACTIVE?

To finalize a chunk, run ve chunk complete <chunk_id>, which updates code references and moves GOAL.md and PLAN.md to ACTIVE. This validates the workflow and generates traceable metadata for lifecycle management.

What does updating code references in a chunk workflow achieve?

Updating code references during chunk finalization records symbolic paths to ensure traceability across the project. It links the finalized chunk's GOAL.md and PLAN.md directly to the relevant code for accurate lifecycle management.

Do I need the ve CLI to validate and apply chunk status updates?

Yes, the ve CLI is required to validate and apply the chunk finalization workflow. It identifies the active chunk and pushes the status updates needed to move GOAL.md and PLAN.md to ACTIVE.

How do I find the active chunk before running the finalization process?

You can find the active chunk by running the command ve chunk list --current. This identifies the specific chunk before you locate its GOAL.md and PLAN.md files to capture code references and finalize.

What is the best way to ensure traceability when completing a chunk?

The best way to ensure traceability is using chunk-complete to capture symbolic code references for the active chunk. This records the paths within GOAL.md and PLAN.md, producing structured metadata for lifecycle management.