claude

workflow

Three agents and a plan queue: the assistant answers and routes, the planner writes a plan, the executor builds it and pushes.

0 on GitHubby Javier NietoMITupdated today
/

Plugin workflow from marketplace workflow in JavierMNieto/workflow-plugin. Commands read from the repo's manifest — today.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (3)

  • change

    Change the workflow itself, the agents, the queue, the hooks or the plugin, from any project. The change is planned and built in the plugin's own repository, by its own queue. Use when the person wants the assistant, the planner, the executor or the plan queue to work differently.

  • design-research

    How to decide the look and behavior of a control, screen or flow that no recorded design decision covers, so nothing a person sees is made up. Use when adding anything a user sees that the project's catalogue (catalogue in .claude/workflow.md) does not cover, when the edit-time hook says no recorded

  • setup

    Sets a project up for the workflow in a short interview, what the project is for and what its owner mostly does there, then the project file, the plugins it turns on and the connectors it keeps, with the defaults for that kind of project and a line on how to reach the rest. Use when a project has no

Subagents (5)

  • assistant

    Answers the owner's questions about the project from the repository, writes what they ask for (a short plan for the executor, a brief for the planner, a message for a person the project names only when asked for one) and says which of the four each topic is. Reads everything, builds nothing. Run the

  • executor

    Builds one or more plans from plans/, from a branch to a push to the project's branch, with the project's checks, a review of the diff against the plan, Codex's and /code-review's, and the project's suites. The owner hands it the plans' paths and it works through them in order without waiting. Run t

  • maker

    Makes the project with its owner in one chat, the compact form of the workflow (form: compact in .claude/workflow.md): decides as the planner does, builds as the executor does, and records every decision in the catalogue. For a project whose changes are small and many. Run the whole session as it wi

  • planner

    Plans one change to the project with its owner, as Fable, and writes the plan into plans/ for the executor agent to build. Research what the products people know do, ground it in the project's docs and code, make the calls, put the rest to the owner with the question tool. Planning only; it never ch

  • reviewer

    Reviews an executor's diff against the plan it builds, in a fresh context: every requirement built, every line of the plan's Done when holding as far as reading shows, nothing outside the plan's scope changed, every user-facing string in the plan's Words section and shown by what it names, the scree

Hooks (18)

  • PreToolUse

    node "${CLAUDE_PLUGIN_ROOT}/scripts/catalogue-context.mjs"

  • PreToolUse

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plan-queue.mjs" tool

  • PreToolUse

    node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-denials.mjs" tool

  • PreToolUse

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plain-words.mjs" question

  • PostToolUse

    node "${CLAUDE_PLUGIN_ROOT}/scripts/turn-audit.mjs" tool

  • PostToolUse

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plan-queue.mjs" wrote

  • PostToolUse

    node "${CLAUDE_PLUGIN_ROOT}/scripts/seen.mjs"

  • UserPromptSubmit

    node "${CLAUDE_PLUGIN_ROOT}/scripts/turn-audit.mjs" prompt

  • UserPromptSubmit

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plan-queue.mjs" prompt

  • UserPromptSubmit

    node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-denials.mjs" prompt

  • UserPromptSubmit

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plain-words.mjs" prompt

  • Stop

    node "${CLAUDE_PLUGIN_ROOT}/scripts/turn-audit.mjs" stop

  • Stop

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plan-queue.mjs" stop

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/scripts/statusline.mjs" install

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plans-on-path.mjs"

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plan-queue.mjs" session

  • StopFailure

    node "${CLAUDE_PLUGIN_ROOT}/scripts/plan-queue.mjs" cutoff

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/scripts/install-check.mjs" || { r="${CLAUDE_PLUGIN_ROOT}"; p="${r%/cache/*}"; t="${r#"$p/cache/"}"; f="This copy is loaded from a folder, not the plugins cache: put them ba

View source on GitHub

More from JavierMNieto/workflow-plugin

All 2 plugins →

writing

claude

Research-writing skills: reviewing, editing, drafting and checking LaTeX papers, proofs, sources and figures, loaded when a project works on them.

6 skills

0

Maintain workflow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins