tushar2708/flow

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

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 already staged changes with a concise Conventional Commit message and explanatory body. Use only when explicitly invoked.

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

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 a chronological, sprint-based N-day development plan from a project specification. Use only when the user explicitly asks for this planning artifact.

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

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

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, tutorials, how-tos, reference or explanation docs, governing README content, building or publishing the doc site, maintaining docmap.json or anything under .docsmith/, or whenever the user or a hook mentions "docsmith".

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

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

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", "walk me through the codebase", "create a diagram of this flow", "how does this module/pipeline/endpoint work", or wants a visual, structured explanation of code they can keep and share. Prefer this skill over an off-the-cuff prose answer whenever the explanation would benefit from structure, diagrams, or a document the user keeps — even if they do not say the word "documentation".

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

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.

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.

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

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.

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

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

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

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.

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

Turn the current conversation into a governed spec saved as a numbered docs/plans/NN doc (docsmith plan frontmatter + validation) — no interview, just synthesis of what you've already discussed.

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

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

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

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

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

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