flow

Plugin flow from marketplace flow in flowst8-dev/flowst8. Commands read from the repo's manifest — 5 days ago.

Skills (13)

• brief

  Flow subcommand. Ticket-readiness interview for one Jira card — asks your role (pre-dev, dev, QA), interviews you on the requirements for that role, gives a verdict, saves a brief manifest beside the spec, and offers to post a summary comment. Run as /flow:brief {ticket}.

• code

  Flow subcommand. Implements the latest pass's spec.md in the consuming codebase with the flow:implementer agent (full mode), or fixes a named list of ACs (targeted mode), and writes manifest.json and manifest.md. No review, verification or commit. Run as /flow:code {ticket} [--target-acs N,N].

• datapoints

  Flow subcommand. Catalogs every code path in the consuming codebase that writes (INSERT/UPDATE/DELETE/MERGE/UPSERT) to one or more named database tables — raw SQL in any language, query builders, ORM model writes and stored-procedure calls — and follows import/include chains up to the entry point (r

• decisions

  Flow subcommand. Appends decisions from pasted meeting notes, a chat thread, an email, a file or a Jira comment URL to a ticket's card-level decision log, via the flow:decision-logger agent. Works before the Jira card exists. Run as /flow:decisions {ticket} [--decisions content].

• drift

  Flow subcommand. Compares a ticket's decision log with its latest spec pass (spec, manifest, diff) and its spec passes with each other for drift, using the flow:drift-checker agent, and writes drift.md. Compares the passes you list, or the latest against the one before it. Run as /flow:drift {ticket

• fetch

  Flow subcommand. Fetches one Jira card with the flow:jira-fetch agent and shows the structured JSON payload. Run as /flow:fetch {ticket}.

• log

  Flow subcommand. Shows the flow-log.md run log for a ticket (latest pass, or a named pass), or lists every run log with its status. Run as /flow:log [ticket] [p0N].

• playwright

  Flow subcommand. Authors or refreshes a ticket's Playwright specs in the consuming codebase's e2e suite, asks you for any missing test data, runs them, and writes test-plan-results.md beside the spec. The only place Flow runs browser tests. Run as /flow:playwright {ticket} [TS-###].

• report

  Flow subcommand. Summarizes local Flow telemetry — run counts and outcomes, durations, tokens and tool calls, per-command, per-ticket and per-agent cost tables, code-review and AC-verification quality signals, retry-budget use and recent runs — and can write a self-contained HTML dashboard. Use when

• review

  Flow subcommand. Runs one flow:code-reviewer pass (no escalation) over the files changed on the current branch, or the latest pass manifest for a ticket, and shows severity-ranked findings. Run as /flow:review [ticket].

• run

  Flow is a multi-agent, spec-driven development pipeline. Takes a Jira ticket from card to verified, reviewed, tested implementation in one command, and keeps a card-level append-only decision log alongside the spec. Run as /flow:run {ticket} (e.g. /flow:run PROJ-123). Also triggers on /flow followed

• spec

  Flow subcommand. Regenerates spec.md for the latest pass of a ticket with the flow:spec-author agent, from a fresh card fetch. Run as /flow:spec {ticket}.

• verify

  Flow subcommand. Scores every acceptance criterion in the latest pass spec against the branch diff with one flow:ac-verifier (no escalation) and writes acceptance-criteria.md. Run as /flow:verify {ticket}.

Subagents (11)

• ac-verifier

  Flow pipeline sub-agent. Read-only scoring of every acceptance criterion in a spec against a git diff, with path:line evidence (pass / partial / fail / manual). Never fixes or retries. Dispatched by the flow orchestrator in Wave D (r1, then r2 and r3 on escalation) and by /flow:verify.

• branch-manager

  Flow pipeline sub-agent and the only Flow agent that runs git. Resolves and checks out the feature branch from a card, makes local commits (code, and spec artifacts under the spec root), and, opt-in only, pushes the code feature branch and opens a PR. Never pushes spec artifacts or telemetry. Dispat

• code-reviewer

  Flow pipeline sub-agent. Read-only review of a list of changed files against the board standards file and universal quality rules; returns severity-ranked findings as JSON. One pass, no fixes. Dispatched by the flow orchestrator in Wave E (r1, then r2 and r3 on escalation) and by /flow:review.

• decision-logger

  Flow pipeline sub-agent. Extracts decisions from supplied meeting notes, threads, emails or Jira comments and appends them, deduped, to a card-level decision-log.md. Append-only. Dispatched by the flow orchestrator in Wave A and by /flow:decisions.

• drift-checker

  Flow pipeline sub-agent. Compares a card's decision log with its latest spec pass (spec, manifest and diff) and each earlier pass with the next, and reports where a document or decision has stopped agreeing with the others as severity-ranked findings. Advisory by default; with --block it marks the r

• implementer

  Flow pipeline sub-agent and the one that writes application code. Implements a spec's acceptance criteria in the consuming codebase (full mode) or fixes a named list of ACs (targeted mode), and returns a manifest. Never commits. Dispatched by the flow orchestrator in Wave C and the Wave E/D retries,

• jira-commenter

  Flow sub-agent. Posts one comment to a Jira ticket only when the ticket is assigned to the authenticated user; refuses otherwise, with no override. Dispatched by /flow:brief after the developer confirms a comment.

• jira-fetch

  Flow pipeline sub-agent. Fetches one Jira card through the Atlassian MCP and returns a fixed JSON payload (title, description, ACs, status, labels, parent story, recent comments). Dispatched by the flow orchestrator in Wave A and by /flow:fetch and /flow:brief; not for general Jira questions.

• playwright-testing

  Flow pipeline sub-agent. Turns spec-testing.md scenarios, the front-end guide and the diff into Playwright specs inside the consuming codebase's existing e2e suite (author mode), and optionally executes them and writes test-plan-results.md (run mode). Never prompts. Dispatched by the flow orchestrat

• spec-author

  Flow pipeline sub-agent. Populates the Flow spec template from a jira-fetch card payload, board standards file, author identity and branch name, and writes one spec.md. Dispatched by the flow orchestrator in Wave B and by /flow:spec.

• test-planner

  Flow pipeline sub-agent. From a spec and a git diff, writes validation.md, front-end-testing.md and spec-testing.md (one TS-### row per AC). Deliberately blind to review and verification results. Dispatched by the flow orchestrator in Wave G and by /flow:test.

Hooks (2)

• PreToolUse

  python

• Stop

  python

Similar plugins