architectureCreate or update docs/blueprint/registry.yaml — the
backlogThe product's prioritised backlog — a project on the repo's forge,
blueprint-authoringAuthoring discipline for vwf blueprints — the code-independence
blueprintMaintain the always-current, full-product blueprint under
change-planTurns an ad-hoc change request into a plan folder that /vwf:execute runs in a fresh context. Use when the user wants to plan a change with no blueprint slice behind it: tooling, docs, CI, a refactor, or a tree the blueprint does not describe. Not for a blueprint slice (use plan). archetype: workflow
design-system-authoringAuthoring discipline for a product's design system — the
design-systemImports the product's design system from the configured design tool into docs/blueprint/design-system.md, and pins design.design_system_id in .config/vwf.yaml. Use as /vwf:design-system once the product has a UI surface; a product with no screen surface takes the text-only path. Not for authoring vi
docs-syncReconcile the repo's human-facing docs — README, CLAUDE.md, docs/
doctorCheck that the repo actually matches what .config/vwf.yaml declares
documentation-standardsOpinionated standards for writing and maintaining Markdown
executeRuns an approved plan folder to completion in a dedicated worktree and a fresh context, and lands it per the plan's recorded consent. Use as /vwf:execute <plan-folder>, next or all, once /vwf:plan or /vwf:change-plan has approved a folder in docs/plans/. Not for writing a plan (use plan or change-pl
feedbackThe front door for production feedback — a bug, a metric reading,
git-workflowManage git workflows — worktree isolation, commits, merges, and
handoffCapture the current session as a handoff document, written to
import-conversationsReads the design review conversation back from a project's design tool, whichever it pins on the design axis, and returns it as a vwf conversations payload. Invoked by /vwf:feedback canvas as its design adapter. Not a general-purpose skill, and not for classifying a remark (use feedback). archetype:
import-design-systemReads the design system back from the project's design tool, whichever it pins on the design axis, and returns it as a vwf design-system payload. Invoked by /vwf:design-system as its design adapter. Not a general-purpose skill, and not for writing the blueprint doc (use design-system). archetype: wo
import-screensReads a flow's designed screens back from the project's design tool, whichever it pins on the design axis, and returns them as a vwf screens payload. Invoked by /vwf:screens import as its design adapter. Not a general-purpose skill, and not for diffing against the contract (use screens). archetype:
initHand a new or existing repo, and every member repo it has, to
karpathy-guidelinesBehavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
mockupsRender the blueprint's screens as self-contained static HTML
plan-managementThe one owner of docs/plans/ bookkeeping — the plan index
planProduce reviewable cycle plans as diffs for one slice of the
product-foundationsThirteen foundations with elicited defaults (users, observability,
productCreate or update docs/blueprint/product.md — the problem, target
readmeCreates or updates the repository's README from a scan of the codebase: the project list, an architecture diagram, infrastructure, local development, and the task-runner commands. Use as /vwf:readme [target-dir]. Not for reconciling docs after a change (use docs-sync). archetype: workflow depends-on
recallRead a handoff document from docs/memory/handoff/<name>.md at the
rest-api-designTechnology-agnostic principles for designing REST APIs. Use when
screensTwo-way screen sync with the project's design tool. "prompt <flow>" writes one
setupBring a repo into vwf's format and keep it there. Step 0 resolves
verifyVerify a deployed environment against the blueprint —