chunk-create

Create a GOAL.md chunk with name, ticket, and dependencies.

3|1|Updated Jan 8, 2026

Search Tags:#workflow #planning #documentation #goal #ticketing #chunk #ve

Ready to run

npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chunk-create
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/chunk-create
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides operators to define a new chunk of work and clearly refine its goal, enabling structured planning before implementation.

Core Features & Use Cases

Define a short, descriptive chunk name and associate an optional ticket number for traceability.
Create a dedicated GOAL.md that captures goals, dependencies, and context so the implementing agent has all required information.
Manage narrative or investigation dependencies by linking chunk goals to related prompts and artifacts.

Quick Start

Execute ve chunk create <shortname> <ticket number> to start a new chunk and generate its GOAL.md.

Frequently Asked Questions about chunk-create

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

FAQPage Schema

How do I define and refine a work chunk for project planning?▼

To define a work chunk, you spawn a new task with a short descriptive name, associate an optional ticket number for traceability, and generate a GOAL.md file documenting scope and dependencies.

What is a GOAL.md file and how does it help document task dependencies?▼

A GOAL.md file is a structured markdown document containing frontmatter with name, ticket, depends_on fields, plus embedded guidance capturing design decisions, constraints, and associated references for the implementing agent.

Can I link investigation dependencies when breaking down project tasks?▼

Yes, you can manage narrative or investigation dependencies by linking chunk goals in the GOAL.md to related prompts and artifacts, ensuring the implementing agent has all required contextual information.

What's the best way to structure discrete work chunks for an implementing agent?▼

The best way to structure work chunks is using a dedicated GOAL.md with enforced frontmatter including name, ticket, depends_on, and embedded guidance capturing design decisions and constraints for the implementing agent.

How do I start a new chunk and generate its goal documentation?▼

You start a new chunk by executing the command 've chunk create <shortname> <ticket number>' to spawn the work chunk and automatically generate its GOAL.md documentation.