w-build — Claude Code skill: what it does, how to install
w-build — a skill for Claude Code that implements an agreed task in small slices and checks the result. It starts from an existing plan or a clear implementation request.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-build -a claude-codeWhat w-build does
w-build reads repository guidance and the technical material for the affected area, then builds one complete slice using existing packages and patterns. It identifies the files owned by the task and states acceptance conditions before editing, while leaving unrelated changes intact. When the work spans packages or touches an unfamiliar area without a plan, steps 1–3 of w-council come first.
The skill runs the smallest suitable check after implementation. Reproducible logic defects call for a regression check, and failed checks are investigated rather than weakened. The full pre-push suite belongs to /w-ship, not this skill. Changes to behavior, commands, or conventions call for updates to the relevant MDX files and nearest README. It does not commit; questions about product scope, secrets, or destructive operations go to a human.
What it helps with
- split an agreed implementation task into complete slices
- preserve unrelated working-tree changes
- check a code change with the smallest suitable test
- update docs after behavior or command changes
Example prompts for the agent
- Use
w-buildto implement the task in the plan and run a suitable check. - Have
w-buildadd the agreed behavior while preserving unrelated edits. - Run
w-buildon a task spanning packages, starting with the requiredw-councilsteps.
How to install w-build
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-build -a claude-code2Manually: put the files in place
~/.claude/skills/w-build/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-build/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-build -a codex2Manually: put the files in place
.agents/skills/w-build/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-build -a cursor2Manually: put the files in place
.cursor/skills/w-build/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-build2Manually: put the files in place
.github/skills/w-build/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-build -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-buildManually: put the files in place
.devin/skills/w-build/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-build -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about w-build
How do I install w-build in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-build -a claude-code. The skill file is at ~/.claude/skills/w-build/SKILL.md.
What does w-build do?
It implements an agreed task in complete slices, runs a suitable check, and updates documentation when behavior or commands change. It does not commit changes.
When does w-build ask a human for input?
It asks about product scope, secrets, or destructive operations. For other decisions, it consults repository instructions and technical docs.
Source text
SKILL.md · MIT
--- name: w-build description: Implement an agreed task incrementally and verify the result. disable-model-invocation: true --- Use an existing plan or a sufficiently clear implementation request. Read repository instructions, affected README/scripts, matching rules and skills, and technical docs. Resolve consequential decisions from matching docs; ask a human for product scope, secrets, or destructive operations. Do not commit. 1. Inspect the working tree and identify the files owned by this task. State the acceptance conditions; preserve unrelated changes. If there is no plan and the area spans packages or is unfamiliar, follow [council](../w-council/SKILL.md) steps 1–3 first. 2. Implement one complete slice using existing packages and patterns. Change owning schemas and run documented generators instead of editing generated clients or migrations. 3. Run the smallest existing check for this change. A reproducible logic defect should have a regression check; use TDD when requested or required by the repository, not as a ritual for prose edits. Never the full pre-push suite (`/w-ship` owns that). 4. Investigate failed checks before building dependent work. Separate regressions caused here from pre-existing or environmental failures; never weaken checks to obtain a pass. 5. If behavior, commands, or conventions changed, update matching MDX and nearest README; otherwise one line why not.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills