flowchad-setup
Flowchad Setup
Initialize Flowchad in a project by discovering what already exists, asking what's missing, and scaffolding flow definitions.
Phase 1: Auto-Discovery (no user input)
Scan the project silently. Gather everything before asking a single question.
1a. Detect Test Framework & Existing Flows
Search for e2e/integration tests — these are flows already defined in code.
# Find test files
find . -type f \( \
-name "*.spec.ts" -o -name "*.spec.js" \
-o -name "*.test.ts" -o -name "*.test.js" \
-o -name "*.e2e.ts" -o -name "*.e2e.js" \
-o -name "*_spec.rb" -o -name "*_test.rb" \
More from fellowship-dev/flowchad
flow-add
Create a new flow definition from a natural language description — scans codebase for routes, components, and existing flows to generate accurate YAML. Usage /flow-add <description>
6flow-suggest
AI-powered improvement prioritization — analyze walk results, friction reports, and trends to produce a ranked action plan. Usage /flow-suggest <flow-name>
6flow-diff
Compare walk snapshots to detect regressions and improvements — visual diff, timing changes, broken/fixed steps. Usage /flow-diff <flow-name>
6evidence-upload
Upload walk screenshots and GIFs to GitHub for embedding in issues and PRs. Supports orphan branch (default), S3, or Navvi backends.
6flow-walk
Walk a user flow using Playwright CDP — execute steps, capture screenshots, measure timing, store results. Usage /flow-walk <flow-name>
6flow-update
Update an existing flow definition to reflect product changes — reads codebase diffs, updates steps/expectations/context. Usage /flow-update <flow-name> <what changed>
6