vwf

Create or update docs/blueprint/registry.yaml — the machine-readable Project Registry every command parses — and docs/blueprint/architecture.md, its prose system-shape view. Derives the whole registry proposal from docs/blueprint/product.md where one exists, evidence quoted and corrected by MCQ; the interview is the fallback.

Move completed cycle plans out of the active set into docs/plans/archived/. Never deletes. May be run manually or offered at the end of execute.

Maintain the always-current, full-product blueprint under docs/blueprint/ — flow docs as the primary unit, entity data contracts, and per-service OpenAPI contracts, plus conventions.md. Stack-agnostic; resolves section→project mapping from the architecture registry. Gated by fresh subagent completeness reviewers per doc and one whole-product coherence review at the end of the sweep. A run sweeps flow by flow until whole-product coverage holds, then stamps it in .config/vwf.yaml — /vwf:plan halts without a complete stamp.

Authoring discipline for vwf blueprints — the code-independence line that keeps a blueprint a durable technical contract, plus the per-entity, cross-entity/integration, and UI/UX completeness bars. Auto-applies when editing any docs/blueprint file. Read the reference matching the surface you are pinning down.

Import the product's design system from the configured design tool into docs/blueprint/design-system.md — the product-wide UX/visual contract (semantic tokens, typography, spacing, motion, accessibility standard, component behaviors) every blueprint screen references — and pin design.design_system_id in .config/vwf.yaml. A vwf foundation, mandatory once the product has a UI surface. Design systems are authored and iterated in your design tool; this skill imports via its adapter plugin, and never authors visual language itself. A product with no screen surface at all takes the text-only path and elicits Terminal UX directly.

Authoring discipline for a product's design system — the code-independent UX/visual contract (semantic tokens, typography, spacing, motion, accessibility standard, component behaviors, anti-patterns) that every blueprint screen references. Auto-applies when editing docs/blueprint/design-system. Read the reference matching the layer you are defining.

Reconcile the repo's human-facing docs — README, CLAUDE.md, docs/ guides, per-project READMEs, the app changelog — with a change that landed, editing only what the change falsified. Runs at the end of every reality-changing vwf command, and standalone after ad-hoc work — pass a commit range, or let it scope to the current branch's delta.

Check that the repo actually matches what .config/vwf.yaml declares — per-language LSP servers and toolchains, each project's frameworks and dependencies against its manifest, the harness task names, health endpoints, the mempalace wing and room set, the graphify CLI/graph/hook/ignore file, and format-stamp drift. Reports; never writes without consent. Run it after setup, before execute, or any time the repo and the config might have drifted apart.

Opinionated standards for writing and maintaining Markdown documentation — writing style, code blocks, tables, CHANGELOGs, and diagrams. Auto-applies when editing any Markdown file.

Execute an approved cycle plan end-to-end in a dedicated worktree — dependency-ordered, code then review+security concurrently per step under TDD with finding loops, one E2E acceptance + UX-conformance pass after all steps, gaps captured in the plan doc. Autonomous between the start and one final human gate, which reviews the run and approves the merge. Requires an approved plan in docs/plans/.

The front door for production feedback — a bug, a metric reading, a UX complaint, or a feature idea. Classifies it and routes it into the doc and command that fix it (gaps → blueprint/plan, metrics → product, UX → design-system/screens). "canvas" harvests the design review conversations from each project's own design tool, via the design adapter, into the same routes. Durable even when mempalace is down.

Manage git workflows — worktree isolation, commits, merges, and pushes. Use for all substantive changes; never work directly in the main worktree.

Capture the current session as a handoff document and file it to mempalace (wing=<project>, room=handoff, drawer=<name>) so work can resume in a fresh session. With no argument — or `next` — it writes the reserved `next` handoff, to mempalace and to the main checkout's docs/memory/handoff/next.md, which /vwf:recall resumes automatically. Use when the context window grows beyond ~60%.

Read the design review conversation back from a project's design tool (whichever it pins on the design axis) and return it as a vwf conversations payload. Invoked by /vwf:feedback canvas as its design adapter — not a general-purpose skill.

Read the design system back from the project's design tool (whichever it pins on the design axis) and return it as a vwf design-system payload. Invoked by /vwf:design-system as its design adapter — not a general-purpose skill.

Read a flow's designed screens back from the project's design tool (whichever it pins on the design axis) and return them as a vwf screens payload. Invoked by /vwf:screens import as its design adapter — not a general-purpose skill.

Behavioral 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.

MemPalace — mine projects and conversations into a searchable memory palace. Use when the user asks about MemPalace, memory palace, mining memories, searching memories, palace setup, wings, rooms, or drawers; or when they want to recall past work that may already be filed in their palace.

Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall is invoked. Complements the mempalace setup skill and requires the mempalace-mcp server.

Render the blueprint's screens as self-contained static HTML mockups — one page per screen plus the state variants the Screens contract pins, styled from design-system tokens — into the repo's gitignored docs/scratchpad/ tree for local browser review. Mockups are realizations, never contract; never pushed to the design tool, never committed.

Produce reviewable cycle plans as diffs for one slice of the blueprint (a flow or an entity). Reads desired (blueprint) vs actual (code), writes only the delta to docs/plans/<date>-<time>-<slice>.md. Resolves the slice's transitive dependency chain and plans each unimplemented dependency as its own plan doc first, in order; routes any blueprint gap it uncovers back through /vwf:blueprint before writing — so no cycle builds on a gap. Requires the blueprint coverage stamp to read complete, and halts on any /vwf:doctor blocking finding across the chain's projects.

Create or update docs/blueprint/product.md — the problem, target users, success metrics, and slice priority the whole blueprint serves. The Phase −1 foundation; blueprint halts without it.

The foundational concerns every product must decide — users & operators, observability, audit logs, change logs, background processes, data retention & PII, notifications, runtime settings, rate limiting, reliability targets, disaster recovery & backup, cost guardrails. Elicited defaults distilled from the 95octane reference implementation. Used by /vwf:architecture (the foundations checklist) and /vwf:blueprint (expanding accepted foundations into contracts); read the reference matching the foundation being decided or expanded.

Create or update the repository's README — scan the codebase and document it with a title, short description, a project list, an architecture mermaid diagram with notes, an infrastructure (cloud tools) section, a local development setup guide, per-project sections (monorepo or multi-repo), and the important task-runner commands. Follows the documentation-standards skill.

Retrieve a handoff document from mempalace (wing=<project>, room=handoff, drawer=<name>) to resume work in a fresh session, and optionally run its next prompt. With no argument — or `next` — it resumes the reserved `next` handoff and runs its continuation without asking. Use to continue after a session that exceeded ~60% context.

Comprehensive, technology-agnostic principles and best practices for designing REST APIs. Use this skill whenever designing new REST endpoints, reviewing API contracts, planning versioning strategy, defining error formats, or establishing API standards for a project. Also trigger when discussing backward compatibility, API security, pagination, rate limiting, authentication schemes, or OpenAPI spec authoring — even if the user doesn't say "REST API" explicitly. This skill is the authoritative guide for all API design decisions.

Bring a repo into vwf's format and keep it there. Step 0 resolves one of three entry paths — onboard (a blank repo bootstraps, a repo with code is detected and confirmed), migrate (reconcile a tree written against an older format), or current (say so and exit) — then runs the shared spine that validates, stamps .config/vwf.yaml, checks the repo, commits, and prints the chain forward.

Verify a deployed environment against the blueprint — health-check each deployed project and re-run the flows' acceptance criteria in staging mode. Run after you (or CI) deploy; vwf never deploys. A clean pass against the production environment offers to record a release, freezing each deployed service's API contract into docs/blueprint/apis/released/. Failures route through the feedback machinery.