agentsclimarketplace

Chunk implement

Skill netguy204/vibe-engineer/skills/chunk-implement

Implement the active chunk by following its PLAN.md, addressing any reviewer feedback in REVIEW_FEEDBACK.md first. Use when the operator asks to implement the current chunk, or as the IMPLEMENT phase of the chunk lifecycle.From its SKILL.md

Install
npx -y skills add netguy204/vibe-engineer --skill chunk-implement

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.5 KB, as published. Nobody here has run it

<!-- GENERATED from src/templates/plugin/skills/chunk-implement.md.jinja2 — edit that template and run `ve plugin render`; direct edits here will be overwritten. --> <!-- Chunk: docs/chunks/plugin_core_commands - Static plugin port of chunk-implement -->

Context

  • ve CLI: !ve --help >/dev/null 2>&1 && echo "installed" || echo "(ve CLI not found)"
  • Task workspace: !cat .ve-task.yaml 2>/dev/null || cat ../.ve-task.yaml 2>/dev/null || echo "(not a task workspace)"
  • Project config: !cat .ve-config.yaml 2>/dev/null || echo "(no .ve-config.yaml — defaults apply)"
  • Project hook: !ve hooks show chunk-implement 2>/dev/null || echo "(no project hook)"

Runtime context

Interpret the context above before following the instructions:

  • ve CLI: The ve command is an installed CLI tool, not a file in the repository. Do not search for it — run it directly via Bash. If the context shows "(ve CLI not found)", tell the operator that the vibe-engineer plugin requires the separately installed ve CLI, suggest uv tool install vibe-engineer (or pip install vibe-engineer), and stop.
  • Uninitialized project: If ve is installed but commands fail because there is no docs/chunks/ structure, tell the operator to run ve init in the project root, then stop.
  • Task workspace: If the Task workspace context shows YAML (keys external_artifact_repo and projects) instead of "(not a task workspace)", you are in a multi-project task workspace. Artifacts (chunks, narratives, investigations) live in the external artifact repo named by external_artifact_repo; code changes happen in the participating projects. Command-specific task guidance appears below.
  • Project config: .ve-config.yaml holds project configuration. Known keys: cluster_subsystem_threshold (default 5 — the cluster size at which to suggest subsystem documentation). When the context shows "(no .ve-config.yaml — defaults apply)", use the defaults.
  • Project hook: docs/hooks/chunk-implement.md holds this repository's own requirements for this command. When the context shows hook content, treat it as a binding instruction from the operator: satisfy it before reporting this command complete, and say so when you do. When it shows "(no project hook)", there are none. If a hook contradicts this command's own instructions, do not silently choose — surface the conflict to the operator and ask.
  • If this is a task workspace (the Task workspace context above shows .ve-task.yaml contents): implementation may span multiple participating projects — see the projects list in .ve-task.yaml. The chunk plan is in the external repo named by external_artifact_repo. Work from the task root to access both the plan and all project directories.

Instructions

  1. Determine the currently active chunk by running ve chunk list --current. We will refer to the directory returned by this command below as <chunk directory>

  2. Check if <chunk directory>/REVIEW_FEEDBACK.md exists. If it does:

    • This is a re-implementation cycle after reviewer feedback
    • Read the file carefully — it contains specific issues from the reviewer
    • You MUST address EVERY issue listed. For each issue:
      • Fix it in the code, OR
      • Defer it with a documented reason (add to PLAN.md Deviations), OR
      • Dispute it with evidence for why the current approach is correct
    • Non-functional feedback (documentation, style, naming conventions) is equally important as functional feedback — do not skip these
    • After addressing all issues, delete the REVIEW_FEEDBACK.md file to signal completion
  3. Implement the chunk plan as described in <chunk directory>/PLAN.md

  4. When implementation is complete, STOP. Do NOT:

    • Modify the chunk GOAL.md status field
    • Run chunk-complete or any finalization steps
    • Set status to ACTIVE or any other value

    A separate COMPLETE phase handles status transitions and finalization.

  5. If you addressed review feedback in step 2, verify you deleted the REVIEW_FEEDBACK.md file. This signals to the orchestrator that all feedback has been addressed.

Keep looking

Skills are one crate of 610,045. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.