Scaffold

One-shot project setup. Analyzes the codebase, builds the .hyperflow/ cache, seeds the memory skeleton, and optionally installs detection shims for other AI tools. Does not start the plan → dispatch chain, invoke /hyperflow:plan when you're ready for that.

Step 1, Analysis Cache

Check for .hyperflow/ at project root.

If absent, dispatch parallel searchers (single message, six Agent calls):

Label	File generated	Discovers
Searcher, analyzing tech stack	profile.md	Name, language, framework, build commands
Searcher, mapping folder structure	architecture.md	Dirs, patterns, routing, data flow
Searcher, extracting conventions	conventions.md	Naming, style, linting rules
Searcher, scanning dependencies	dependencies.md	UI lib, state, data fetching, DB, auth
Searcher, auditing test setup	testing.md	Runner, E2E, patterns, commands
Searcher, reading git workflow	git-workflow.md	Branches, commits, CI/CD, PR conventions

See project-analysis.md for what each file captures.

If present, staleness check: Compute SHA256 of tracked config files, compare against .hyperflow/.checksums. Refresh only stale files. Print Refreshing, <comma-separated list of stale files>.

After analysis:

• Write .hyperflow/.checksums (SHA256 of package.json, tsconfig.json, eslint/biome config, etc.)
• Write .hyperflow/.version (the current plugin version from skills/hyperflow/VERSION) so the cache is stamped current. The session-start migrator (scripts/migrate-cache.py) reads this marker on later sessions and brings an older cache forward when the plugin version moves, a missing/older marker triggers an idempotent, additive migration (new memory files, refreshed doctrine copy).
• Append to .gitignore if .hyperflow/ is not already excluded

Step 2, Memory Skeleton

Create .hyperflow/memory/ if absent: