valzav/valcraft

Create or retrofit a lean spec-driven development project frame: project instructions, README, product brief, architecture and ADR structure, and other justified scaffold artifacts. Use when starting a project or repository, asking to scaffold or set up SDD, retrofitting project structure, or committing Valcraft's base configuration with the frame. Cast commits one clean frame and hands its product brief to Foreman. Not for feature or PRD triplets, the first MVP feature, staged-feature completion, quick tasks, implementation, review, merge, or tracker closure.

Distill a prompt artifact — inline prompt text, a markdown prompt file (system prompt, agent instructions, slash command), a skill directory, or a workflow — into its minimal goal-directed essence, a short structured summary of goal, applicability, steps, and load-bearing constraints. Use when explicitly invoked, or when the user asks to distill, condense, deconstruct, or boil down a prompt or skill, asks what a skill actually does under the noise, wants a cleaned minimal copy of a skill saved as a new skill, or wants to compare two similar skills or prompts. Read-only over the source — for improving the artifact in place, use valcraft-hone.

Under a Foreman assignment, write or revise one implementation task plan for a feature FEAT-NNN/T-XXX, quick Q-NNN/QT-XXX, or existing task plan; apply MSW, commit and push the reviewable plan, and hand its exact commit to Review. Foreman dispatches it for task planning and plan-review remediation; start work with valcraft-foreman. Not for implementation, feature specification, review, PR creation, merge, or tracker closure.

Coordinate or take over the spec-driven delivery loop through fresh Spec, Draft, Review, Forge, Land, and Temper workers, from a new feature, PRD, or quick-task source to landing and retrospective. Spec, Draft, Forge, and Land run only under it. Own runtime readiness, intake, takeover inference, task selection, intermediate tracker state, worker lifecycle, backend returns, report validation, approval gates, recovery, and named-state transitions. Use for a new feature, PRD, or quick task, "run the delivery loop", "take over delivery", "start sprint", "work through the tasks", "deliver quick", or "run foreman". Do not use for a standalone review (valcraft-review), retrospective (valcraft-temper), or project framing (valcraft-cast).

Under a Foreman assignment, implement one feature task, quick task, or passed plan; write code and discriminating tests, remediate code findings, push the task PR, and hand Review an exact target. Foreman dispatches it; start work with valcraft-foreman. Not for planning, specification, review, merge, or closure.

Refine an existing prompt artifact — inline prompt text, markdown prompt files (system prompts, agent instructions, slash commands), or a complete skill directory — against the official model prompting guides (Anthropic's Claude Fable 5.1 and Fable 5 prompting guides + OpenAI GPT-5.6 best practices). Use when explicitly invoked, or when the user asks to refine, tighten, optimize, modernize, or audit a prompt, system prompt, SKILL.md, CLAUDE.md, agent instructions, or skill for Claude, Opus, Fable, GPT, or Codex — even if they just say "make this prompt better" or "apply prompting best practices". Use for guide-based audit or refinement. For a read-only essence summary or separate minimal copy, use valcraft-distill. For deletion-only reduction of a Markdown document against its contract, use valcraft-msw.

Finalize reviewed Valcraft work: verify exact final heads and applicable checks, merge an authorized task or spec PR, close the valid tracker targets, reconcile partial completion, or record and close work completed outside git. Foreman dispatches it to land, merge, finalize, close, mark not planned, resume a partial merge or closure, or assess external-completion evidence. Land never implements or reviews a change and never gives merge authority to Foreman.

Apply the MSW Kernel to a markdown document — a plan, spec, skill, prompt, or any other .md file. Derives the document's contract, judges every claim by the kernel's deletion test, deletes the claims that fail, audits every limit for authority, and reports in the kernel's format. Use when explicitly invoked with a file, or when the user asks to apply MSW, run the MSW deletion test, or strip a document down to what its contract actually requires. Edits the target in place — for prompt-guide refinement use valcraft-hone; for a read-only essence summary use valcraft-distill.

Independently review an exact plan commit, code target, or completion-evidence record and return reproduced findings without edits. Use plan mode for plans and feature artifacts, code mode for diffs and refs, and evidence mode for Land records. Use valcraft-hone for prompt audits and valcraft-msw for document reduction.

Create or refresh a business-facing project roadmap from accepted goals, priorities, feature contracts, and verified progress. Use for a stakeholder view of what is done, underway, and still needed, or a Foreman roadmap refresh. Not for choosing strategy, prioritizing work, writing feature contracts, or selecting Foreman's next task.

Under a Foreman assignment, create or resume one complete feature contract triplet, including the first MVP feature, or one quick-task file from exactly one local requirements document, selected GitHub PRD issue, or inline quick brief; push it and open its spec PR. Foreman dispatches it for intake, staged feature completion, Spec review remediation, and tracker projection. Start new work with valcraft-foreman. Not for project scaffolding, task planning, implementation, review, PR landing, or closure.

Produce an evidence-based retrospective over completed work, or synthesize prior Temper reports, and deliver one local, gitignored retrospective report with an exact Review handoff. Use for a retrospective, post-mortem, lessons learned, process-improvement analysis, completed feature or quick-task batch, PR or commit corpus, date window, or synthesis of analyze reports. Temper writes no git state: no branch, commit, push, or PR. It never reviews, closes tracker state, applies proposals, or analyzes one change before merge; in an attended synthesize run it offers corroborated proposals to the operator as a selection and records the choice.

Configure the committed .valcraft/config.yaml base and user-local .valcraft/config.local.yaml overlay. Use for initialization, invalid configuration, plugin upgrade, or requested tracker, approval, Foreman, backend, branch, merge-strategy, browser-tool, or editor-navigation changes. Tune owns only these files and the Valcraft Herdr plugin install; it does not scaffold or run delivery.