Visualizeworkflow

/visualizeworkflow

Approval-first workflow for visual or experiential alignment. Plain /workflow remains autonomous; this command is the opt-in approval route.

New /visualizeworkflow runs do not mutate product code or root SPEC.md. When a saved visualization is approved and implementation continues, /opusworkflow is the default outer route and /visualizeworkflow is the inner contract. Direct continuation remains valid, but implementation must inherit the Claude/Opus planner-reviewer plus MiniMax-M2.7-highspeed executor policy.

outer_route: opusworkflow
inner_contract: visualizeworkflow

Modes

New Run

Use for:

/visualizeworkflow "build the dashboard"

Run the normal governed planning spine inline:

1. Taste gate: read taste.md and taste.vision; if missing, stop and route

to /tastebootstrap.

1. Research brief: use the repo's effectiveness-first deepresearch protocol

when current facts matter; justify local-only when they do not.

1. Code audit: inspect relevant repo anchors before planning.
2. Introspection: run pre-plan hard-gate reasoning before freezing the draft.
3. Plan and Agent-Native Estimate.
4. Draft SPEC.md into the visualization run folder as draft-SPEC.md.
5. Create the visualization package using the /visualize contract inline.
6. Stop before implementation.

Do not mutate product code or root SPEC.md during a new run. The draft spec stays under .taste/visualizations/{run}/draft-SPEC.md until approval.

Continue

Use for:

/visualizeworkflow --continue .taste/visualizations/YYYYMMDD-HHMMSS-slug

This means the user approves the saved visualization enough to implement.

1. Read visualization.md, draft-SPEC.md, and approval.json.
2. Check live git status, active SPEC.md, and obvious repo drift since the

artifact was created.

1. Archive a non-reused active SPEC.md before replacing it.
2. Promote draft-SPEC.md to root SPEC.md.
3. Execute the implementation inline using /workflow rules as the playbook,

but do not rely on nested custom-skill chaining.

1. Verify against root SPEC.md, run post-implementation introspection, archive

closeout, and summarize.

Revise

Use for:

/visualizeworkflow --revise .taste/visualizations/YYYYMMDD-HHMMSS-slug "make it denser"

Update visualization.md, draft-SPEC.md, and approval.json with the revision request. Stay stopped with WAITING_FOR_VISUAL_APPROVAL. Do not implement.

Run Folder

All new and revised artifacts live under ignored .taste/visualizations/:

.taste/visualizations/YYYYMMDD-HHMMSS-slug/
  visualization.md
  draft-SPEC.md
  approval.json
  prompt.txt              # when an image prompt is produced
  diagram.md|html|svg     # when a schematic is produced
  index.html              # optional HTML companion for human review
  image.png|webp|jpg      # only when an image is actually generated

approval.json must be valid JSON:

{
  "status": "WAITING_FOR_VISUAL_APPROVAL",
  "task": "short task",
  "surface": "frontend-web",
  "mode": "image|prompt-only|markdown|Mermaid|HTML|SVG",
  "root_spec_promoted": false,
  "implementation_started": false,
  "created_at": "ISO-8601 or unknown",
  "updated_at": "ISO-8601 or unknown"
}

On continue, update status to APPROVED_FOR_IMPLEMENTATION before implementing and to IMPLEMENTED_VERIFIED after verification.

Approval Stop Output

Every new or revised run must end with:

## Visual Approval Required

- Status: WAITING_FOR_VISUAL_APPROVAL
- Run Folder: .taste/visualizations/...
- Visualization: .taste/visualizations/.../visualization.md
- Draft SPEC: .taste/visualizations/.../draft-SPEC.md
- Implementation Started: no

Approve and continue:
/visualizeworkflow --continue .taste/visualizations/...

Revise:
/visualizeworkflow --revise .taste/visualizations/... "requested change"

Hard Rules

• /visualizeworkflow is the approval route; /workflow remains autonomous.
• Never implement before --continue.
• Never claim an image exists unless an image artifact path exists.
• Backend, API, infra, and agent-runtime tasks may use diagrams or operational

narratives instead of fake UI mockups.

• Do not read or persist secrets, private customer artifacts, or .env files.
• HTML artifacts are companion review surfaces. Keep draft-SPEC.md,

visualization.md, and approval.json as the canonical implementation and approval sources, and make the HTML point back to them.

• HTML must stay local and self-contained by default: no remote scripts, remote

stylesheets, remote fonts, analytics, absolute local paths, .. traversal, or secret-like material.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: waitdeadai
• Source: waitdeadai/minmaxing
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.