flowstate

Use before any creative work — features, components, changes, or modifications. Guides structured design through collaborative dialogue before implementation. Triggers: "brainstorm", "design", "think through", "explore approaches", ambiguous requests, or requests with multiple valid interpretations.

Use after a problem has been solved and the solution verified working — captures the lesson as categorized documentation in docs/solutions/ with YAML frontmatter so future sessions can find it. Triggers: "compound", "capture learning", "document solution", "that worked", "it's fixed", "working now", "problem solved", "that did it", "doc-fix".

Use for extended multi-agent review with 14+ agents including conditional and language-specific reviewers. Appropriate for large changes, architectural shifts, migrations, or when standard review is not thorough enough. Triggers: "deep review", "thorough review", "full review", "extended review", "review everything", "maximum coverage".

Use to review brainstorm or plan documents before proceeding to the next workflow step. Applies structured self-review for completeness, clarity, consistency, feasibility, and YAGNI.

Use when implementation is complete and all tests pass — guides branch completion by presenting structured options for merge, PR, or cleanup.

Use when performing multi-agent code review after implementing features, before merging, or when reviewing PRs. Runs 5 core review agents in parallel plus a learnings researcher. Produces prioritized findings (P1/P2/P3) with todo files for tracking and resolution. Triggers: "review", "code review", "check before merge", "review PR", "run reviewers", "catch issues".

Enhance an existing plan with parallel research agents per section. Adds best practices, edge cases, code examples, and learnings references. Does not rewrite -- only enriches. Triggers: "deepen", "enhance plan", "add research to plan", or after initial planning when more depth is needed.

Transform brainstorm outputs, feature descriptions, or improvement ideas into well-structured implementation plans with TDD-structured tasks. Orchestrates parallel research (local + conditional external), spec-flow analysis, and plan writing. Triggers: "plan", "implement", "build this", or after a brainstorm session when ready to move to implementation.

Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification -- not performative agreement or blind implementation.

Use when requesting code review after implementing features, before merging, when stuck, or after fixing complex bugs. Structures what to provide reviewers and what output to expect.

Use when executing implementation plans with independent tasks — dispatches a fresh subagent per task with two-stage review (spec compliance then code quality) after each.

Use when encountering any bug, test failure, or unexpected behavior. Enforces a disciplined reproduce-isolate-diagnose-fix-verify cycle. No guessing allowed.

Use when implementing any feature or bugfix, before writing implementation code. Enforces strict test-first development — no production code without a failing test.

Use when subagent-driven-development detects parallelizable task waves in an approved plan. Spawns up to 3 implementer teammates per wave, each in its own worktree, then merges worktrees between waves. Triggered internally by the flowstate:subagent-driven-development skill — not user-invoked. Triggers: "parallel waves", "team execution", or invocation from subagent-driven-development.

Use at the start of the work phase, after plan approval and before implementation begins, to create an isolated git worktree for the feature branch. Triggers: "create worktree", "isolate work", "set up branch", "start implementing", or invocation from flowstate:subagent-driven-development.

Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.

Structure implementation plans with TDD-structured tasks, bite-sized granularity, and learnings integration. Use when converting research/specs into an actionable plan document.