skills.rest
netguy204
netguy204COMMUNITY
Explore all skills by this author →
Website𝕏@netguy204GitHub

chunk-implement

Implement the active chunk's code changes according to PLAN.md and feedback.

3|1|Updated Jan 8, 2026
Search Tags:#workflow#implementation#coding#plan#review-feedback#chunk
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-implement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chunk-implement
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/chunk-implement
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates the currently active chunk from planning into concrete code, ensuring alignment with the PLAN.md and reviewer feedback.

Core Features & Use Cases

  • Implement per PLAN.md: Translate the active chunk's goals into code changes following the documented plan.
  • Feedback integration: If REVIEW_FEEDBACK.md exists, address every issue, defer as Deviations, or dispute with evidence, and delete the file upon completion.
  • Workflow isolation: Keep changes contained to the chunk directory and avoid modifying GOAL.md or triggering finalization steps.

Quick Start

Identify the active chunk with ve chunk list --current and implement it according to the PLAN.md.

Frequently Asked Questions about chunk-implement

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

FAQPage Schema
How do I implement code changes from a planning document while addressing reviewer feedback?▼

Implementation follows the PLAN.md to translate active chunk goals into code, addressing every issue in REVIEW_FEEDBACK.md if present, then deleting the feedback file upon completion.

What is the best way to keep code changes isolated when implementing a specific workflow chunk?▼

To isolate changes during chunk implementation, keep all modifications confined to the chunk directory and avoid modifying GOAL.md or triggering any chunk finalization steps.

How do I integrate reviewer feedback into my code implementation workflow?▼

Integrate reviewer feedback by addressing every issue in REVIEW_FEEDBACK.md, deferring issues as Deviations, or disputing with evidence, and delete the file once integration is complete.

How do I identify which workflow chunk to implement before starting the coding process?▼

Identify the active workflow chunk before coding by running the command 've chunk list --current' to see which chunk requires implementation according to its plan.

Can I modify the project goals when implementing an active chunk?▼

No, you cannot modify project goals during chunk implementation; the workflow isolates changes to the chunk directory and explicitly avoids modifying GOAL.md to maintain project scope.

What happens to REVIEW_FEEDBACK.md after I finish implementing the chunk?▼

After finishing chunk implementation, the workflow requires you to delete REVIEW_FEEDBACK.md to clear the feedback queue and prevent reprocessing of resolved issues.

Related Skills

Explore More Software Engineering Skills→
netguy204netguy204
3

chunk-complete

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

Community
Intermediate
netguy204netguy204
3

chunk-commit

Automate conventional Git commits for chunk workflows with required artifacts.

Community
Intermediate
netguy204netguy204
3

chunks-resolve-references

Update cross-chunk references in active GOAL files, flagging ambiguities for operator review.

Community
Intermediate
SireJeffSireJeff
8

RPI Implement Phase - Execute chunk-based todolists with atomic changes and continuous testing

Execute chunk-based todolists with atomic code changes and continuous testing.

Community
Advanced