flow

Plugin flow from marketplace claude-assets in tushar2708/claude-assets. Commands read from the repo's manifest — 2 days ago.

Skills (29)

• add-to-roadmap

  Add one roadmap.md item under an epic and create its matching tracker item. Use only when explicitly invoked.

• answer-properly

  Explain code, system behavior, or technical concepts through real-world purpose, state, triggers, consequences, and architectural context. Use only when the user explicitly invokes this explanatory style.

• commit-no-verify

  Commit already staged changes with a Conventional Commit message while explicitly skipping commit hooks. Use only when explicitly invoked.

• commit

  Commit already staged changes with a concise Conventional Commit message and explanatory body. Use only when explicitly invoked.

• create-detailed-days

  Turn a range of an existing N-day plan into a self-contained day-by-day implementation guide with verified learning resources. Use only when explicitly invoked.

• create-n-day-plan

  Create a chronological, sprint-based N-day development plan from a project specification. Use only when the user explicitly asks for this planning artifact.

• create-priming

  Analyze a repository and create or refresh portable agent-context documents for its major areas. Use only when explicitly invoked.

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• docs

  Deterministic documentation governance for any project. Use when writing or updating technical documentation of any kind, processing "[docsmith] update ..." documentation tasks from the task queue, checking documentation freshness or staleness, writing ADRs / decision records, plans, runbooks, tutor

• execute

  Execute approved Flow work items in wave, stage, and task order, using the native tracker or Flow's file tracker.

• explain-feature

  Explain a repository feature in concise runtime order, covering contracts, state, control flow, and failures. Use only when explicitly invoked.

• explaining-code

  Produce accurate, consistent, easy-to-read HTML documentation that explains a codebase — one feature, one subsystem, or a whole repository — by reading the real source and tracing every claim to a file:line. Use this whenever the user asks to "explain how X works", "document this repo/feature", "wal

• fix-findings

  Run docsmith validation and mechanically resolve every known finding. Use only when explicitly invoked.

• grill

  A research-backed, relentless interview to sharpen a feature. Map its concepts, research best practices and pitfalls, then reach a shared understanding with the developer.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• init

  Initialize Flow onboarding: scaffold or refresh docsmith, create the portable roadmap registry, configure task tracking, and write idempotent agent guidance. Use only when explicitly invoked.

• link

  Find a requested file location and return one clickable absolute path with its line number. Use only when explicitly invoked.

• make-tasks

  Convert an approved Flow wave plan into ordered, dependency-aware work items. Use only after the user approves the plan.

• plan-it

  Write an approved plan split into sub-feature waves, stages, and tasks, from session context, a spec file, or both.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• review

  Critically review a scoped implementation without modifying files, tests, staging, or repository state. Use only when explicitly invoked.

• spec

  Turn the current conversation into a governed spec saved in its own numbered docs/specs/spec-NN-<use-case> folder (docsmith plan frontmatter + validation) — no interview, just synthesis of what you've already discussed.

• sync-issues

  Reconcile roadmap.md epic sections with the declared tracker. Backfill items, repair links, sync status. Never duplicates an item or guesses ownership.

• update-docs

  Process pending docsmith update tasks, verify code claims, rewrite invalidated documentation, and validate it to green. Use only when explicitly invoked.

• update-pr

  Review the current pull request and update its title and description with a synthesized Conventional Commit-style summary. Use only when explicitly invoked.

• write-adr

  Write and validate a docsmith Architecture Decision Record. Use only when explicitly invoked.

• write-doc

  Write and validate a docsmith evergreen documentation file. Use only when explicitly invoked.

• write-prd

  Write and validate a docsmith Product Requirements Document. Use only when explicitly invoked.

Subagents (1)

• docsmith-doc-author

  Use to WRITE or REWRITE a single documentation file strictly per its docsmith category and template — tutorial, how-to, reference, explanation, runbook, decision (ADR), plan, prd, or research. Invoked by the /flow:write-doc, :write-adr, :write-prd, and :spec commands with a category + topic, or dire

Hooks (3)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/exit_plan_skill_review.py"

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/skills/docs/scripts/hook/docsmith_hook.py"

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/exit_plan_make_tasks.py"

Similar plugins