Individual skill
phase-build
Build one release phase against the specs — plan it on an interactive board (endpoints, components, resources, with what already exists read from the codebase), let the user adjust, then build node by node while the board shows live progress. Use when the user wants to build a phase, implement the phase-1 slice, execute the plan from a story map or spec, or watch a build happen visually.
plugins/vstack/experimental/phase-build/SKILL.md
Source commit 0f2e1a8c0f95aa486aa88f0abae347ea16e4b809
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 11
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- claude-skills Repository topic
- ai-agents Repository topic
- claude-plugin Repository topic
- codex Repository topic
- codex-plugin Repository topic
- codex-skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesSKILL.mdcore · 6,809 bytesassets/build-board.htmlasset · 62,884 bytes
Read excerpt
One release phase, built in three passes — API, then UI, then infrastructure — against a plan the
user saw and adjusted first. The board shows three trees (Endpoints · Components · Resources), each
node coloured by what it is: **new** this phase, **changed** (exists, this phase extends it), or
**already built**. Press Start, and the same board becomes the progress view — nodes pulse while
being built and fill in as they land.
```
story map slice + specs + phase screens ──► plan JSON ──► board ──► user adjusts ──► Start
│
done ◄── infra ◄── ui ◄── api — one node at a time, each reported to the board ◄┘
```
**`have` is read from the codebase, never from a previous plan.** A plan that colours from last
phase's intentions lies the first time a phase ships partial. Read the actual routes, components,