wf5-implement_skill

This skill implements a single step from the Plan for wf5-implement, executing defined tasks in the repository and validating outcomes.
  • Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill shotaiuchi/dotclaude --skill wf5-implement

  • SKILL.md2.0 KB

Overview

This skill implements a single step from a Plan document. It automates loading the Plan, locating the target step, applying only the planned changes to project files, running related tests, recording an implementation log, updating state, and committing the result.

How this skill works

The skill checks for active work and the presence of the Plan file, determines the target step (argument or next incomplete step), extracts the step metadata (title, tasks, targets, dependencies, completion criteria), and applies the changes to the specified files without making off-plan edits. It runs tests affected by the change, writes an implementation entry to the implementation log template, updates state.json to mark the step completed, and creates a validated commit with an auto-detected type.

When to use it

  • You have an existing Plan document and want to implement exactly one defined step.
  • You need automated, auditable single-step changes with enforced dependency checks.
  • You want tests run only for changes directly related to this step.
  • You need consistent commit messages and progress tracking between steps.

Best practices

  • Always ensure 03_PLAN.md is up to date and step dependencies are correct before running.
  • Do not use this skill to bundle multiple steps — one execution equals one step.
  • Limit off-plan edits to trivial fixes (typos/imports); record them as Notes when they occur.
  • If a change requires design or scope change, interrupt and update the Plan first.
  • Review the implementation log entry and test results before pushing the commit.

Example use cases

  • Implementing a bugfix step that lists affected files and a fix task, then running unit tests for those modules.
  • Adding a small feature described in the Plan with clear completion criteria and committing with an auto-generated feat scope.
  • Applying a refactor step that targets specific files, verifying refactor test coverage, and recording the log.
  • Completing a documented task that requires updating configuration and ensuring dependent steps are already completed.

FAQ

The skill auto-selects the next incomplete step based on state.json and validates dependencies before proceeding.

Are off-plan changes allowed?

Only trivial fixes (typos, imports) are allowed and must be noted; any significant design change must stop and prompt a Plan update.

How is the commit type chosen?

The step content drives type detection (fix/refactor/test/docs/feat) and can be overridden by commit settings in config.json.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
wf5-implement skill by shotaiuchi/dotclaude | VeilStrat