flow

Plugin flow from marketplace myworkflow in KhaiStimpson/myworkflow. Commands read from the repo's manifest — 1 month ago.

Skills (9)

• design

  Answer an under-determined visual question with three variants in one self-contained HTML artifact, at desktop and mobile, then record the decision so implementation reuses the real design system. Use before writing UI code whenever more than one defensible visual answer exists.

• explore

  Brainstorm an open-ended idea without touching a single file, and land it as an artifact of concrete options with a recommendation. Use when the request is "brainstorm", "come up with N suggestions", "be creative", "what could we do here" — anything where the answer is ideas, not code.

• eyes

  Run the app, look at it at desktop and mobile widths, and capture durable screenshots — the review pass that green tests do not perform. Use before committing any UI-touching change, and before asking for approval on visual work.

• flow

  Front door for any new piece of work — routes it, then runs the route end to end. Use when you want the whole working loop rather than one stage of it.

• loop

  Start the loop that executes the live plan — read the plan, fill in the loop prompt from the template, and hand it to /loop. Use to run a planned effort to completion or to resume one, instead of pasting the loop prompt by hand.

• plan

  Turn agreed work into a phased markdown plan with checkboxes in docs/, plus the exact loop prompt that executes it — and implement none of it. Use when work exceeds one reviewable change, or when asked for "a plan with phases", "a loop command", or "a goal prompt".

• start

  The front door for any new piece of work. Investigate the task, announce a route in three lines with a one-token veto, then run it. Use when work arrives and it is not obvious whether it needs a plan, a design pass, a single slice, or just doing.

• work

  Implement exactly one slice — one task or one ticket — on its own branch, verify it, capture screenshots if it touches UI, and land it on the integration branch. Use as the body of a loop iteration, or for a single self-contained change.

• wrap

  Close out a session or an effort — write the handoff file, open the integration PR, comment the tracker, and make the repo present itself. Use when stopping mid-effort, when a loop finishes, or when the work is done.

Subagents (2)

• fresh-eyes

  Review one landed slice against the standards it claims to follow and the task it claims to complete, with no memory of writing it. Use after a slice is verified and before it is merged, or on any diff that wants a second read.

• researcher

  Background research on any load-bearing external fact — vendor terms, API limits, platform behaviour, pricing, licensing, framework guidance. Writes a cited report to docs/research/ and returns a summary. Use whenever a decision rests on something outside the repo, instead of asserting it from memor

Hooks (6)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}"/scripts/session-state.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/scripts/guard-image-read.sh

• Stop

  "${CLAUDE_PLUGIN_ROOT}"/scripts/phase-boundary.sh

• Stop

  "${CLAUDE_PLUGIN_ROOT}"/scripts/context-budget.sh

• PreCompact

  "${CLAUDE_PLUGIN_ROOT}"/scripts/write-handoff-spine.sh

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}"/scripts/write-handoff-spine.sh

Similar plugins