Universal workflow generator for AI-assisted development.
Markdown-native. Zero installation. Works with any project type.
ai-flow-anything generates tailored AI-assisted development workflows for your project. It interviews your codebase, asks you about your goals, and produces a complete set of flows that guide AI assistants through your development process.
No code. No DSL. No CLI. Just markdown files that Claude, Cursor, or any AI assistant reads and follows.
- AI is the engine. All instructions are prose in markdown. The AI reads, interprets, and acts.
- Documentation-first. Every task starts with design docs and diagrams before code.
- Living knowledge base. Documentation evolves with the project, capturing patterns and decisions.
- Universal by default. Works for games, web apps, APIs, mobile apps — anything.
- Customizable by editing markdown. Add phases, rules, or entirely new flow types by editing files.
cd your-project
git clone https://github.com/yusufkaraaslan/ai-flow-anything.git .ai-workflowPick the platform you use and follow the install instructions in its directory:
| Platform | Install guide |
|---|---|
| Claude Code | platforms/claude/README.md |
| Cursor | platforms/cursor/README.md |
| GitHub Copilot | platforms/github-copilot/README.md |
| OpenCode | platforms/opencode/README.md |
| Kimi Code CLI | platforms/kimi-code/README.md |
Each wrapper is a thin file that points the AI at the platform-neutral instructions.md. All workflow logic is the same; only the activation mechanism differs per tool.
Ask your AI to initialize ai-flow-anything for the project. Each platform's install guide shows the exact invocation — slash command on platforms that support them (like Claude Code), or natural language anywhere ("initialize ai-flow-anything for this project"). The AI will:
- Detect your project type (Unity, Godot, React, FastAPI, etc.)
- Ask you about project-specific decisions
- Generate flows tailored to your project
- Install them to
.ai-workflow/flows/
Ask the AI to run a flow against a task. Examples (use whatever invocation style your platform supports — slash command on Claude Code, natural language anywhere):
- "Design a task called my-task" — runs the design flow
- "Implement the next task flow for my-task" — runs the implement flow
- "Validate my-task for PR" — runs the PR flow
- "Sync the knowledge base" — runs the KB sync flow (reconciles docs with reality)
After initializing ai-flow-anything, your project has:
.ai-workflow/ ← ai-flow-anything core + your rendered flows
├── instructions.md # Orchestration contract
├── VERSION # Installed version (used by the update intent)
├── universal/ # Non-negotiable rules, workflow structure, KB spec
├── profiles/ # Generic + your detected profile
├── rules.md # Project-specific rule overrides
└── flows/
├── design-flow.md # Design tasks with diagrams
├── implement-flow.md # Implement task flows with validation
├── free-flow.md # Quick fixes, tweaks, small refactors
├── parallel-implement-flow.md # Parallel implementation of all task flows
├── pr-flow.md # PR lifecycle management
├── test-flow.md # Test planning & execution
├── deploy-flow.md # Deployment & release
├── docs-flow.md # Documentation maintenance
└── kb-sync-flow.md # Reconcile KB + task records with the codebase
flow-storage/ ← the three-tier knowledge base
├── project/ # Architecture, conventions, patterns, decisions
├── team/ # Onboarding, workflows, glossary
└── tasks/ # Per-task records (created by design-flow)
Each task gets its own record under flow-storage/tasks/ that grows as the task moves through the flows:
flow-storage/tasks/my-task/
├── design/ # design-flow output
│ ├── task-design.md # Design document (immutable after sign-off)
│ ├── task-technical-design.md # Technical design (evolves)
│ ├── task-edge-cases.md # Edge cases & decisions
│ └── diagrams/
│ ├── class-diagram.puml
│ ├── package-diagram.puml
│ └── sequence-diagram.puml
├── implement/ # implement-flow output
│ └── flow-plan/
│ ├── task-flow-01-user-session-store.md # AI proposes descriptive names
│ ├── task-flow-02-auth-service.md # Variable number (2-10+) based on complexity
│ ├── task-flow-03-login-form-component.md
│ └── task-flow-04-tests.md # Developer approves/modifies
├── test/ # test-flow output
├── pr/ # pr-flow output
│ └── feedback/ # PR feedback records
├── deploy/ # deploy-flow output
└── docs/ # docs-flow output
└── lessons-learned.md # Post-merge summary
The knowledge base is trusted context — every flow loads it before doing anything. But projects drift: a test framework gets swapped, a "hard" constraint gets relaxed, tasks ship outside the flows. A stale KB is worse than an empty one, because wrong facts poison every future flow run.
ai-flow-anything defends against this on three levels:
- Load-time spot-check (Rule 18) — every flow verifies a few load-bearing KB claims (test framework, numeric constraints, phase labels) against the codebase before trusting them. Contradictions are flagged at the next review gate.
- Status drift audit — "Show workflow status" runs read-only doctor checks: task records stuck on
pendingfor shipped features, malformed sign-off blocks, misplaced artifacts, KB files that were never synced. - KB sync flow — "Sync the knowledge base" walks every KB entry and task record, checks each claim against the live codebase, and presents claim → observed reality → proposed fix at review gates. Corrections are applied in place and each verified file gets a
Last Syncedstamp.
Installs carry a VERSION file. When a new ai-flow-anything version ships, ask your AI to "update ai-flow-anything" — it re-syncs the core (instructions, universal rules, profiles, wrappers) while preserving your rendered flows, project rules, and knowledge base, and offers per-flow re-render diffs when skeletons changed. One review gate before anything is overwritten.
| Profile | Description | Detection |
|---|---|---|
| generic | Minimal fallback — works for anything | Any project |
| unity-game | Unity/C# games | Assets/, *.cs, ProjectSettings/ |
| godot-game | Godot/GDScript games | project.godot, *.gd |
| web-frontend | React/Vue/Angular/Svelte | package.json, src/ |
| backend-api | FastAPI/Django/Express/Go | pyproject.toml, go.mod, Cargo.toml |
| mobile-app | Flutter/React Native | pubspec.yaml, ios//android/ |
Developer asks to initialize ai-flow-anything.
AI reads:
instructions.md → "I am a workflow generator"
universal/rules.md → "These rules apply to all projects"
profiles/*/README.md → "Which profile matches this project?"
AI detects project type:
→ Scans files, matches against profile detection hints
→ If ambiguous: asks developer
→ If no match: offers to create custom profile
AI loads profile:
profiles/{detected}/README.md → "This is a Unity game"
profiles/{detected}/discovery.md → "Explore the codebase like this..."
profiles/{detected}/rules.md → "Follow these Unity-specific rules"
profiles/{detected}/skeletons/ → "Fill these templates with discovered details"
AI executes discovery:
→ Follows discovery.md instructions
→ Reads files, searches patterns, asks questions
→ Fills slot catalog with project specifics
AI generates flows:
→ Loads skeletons
→ Fills project-specific slots (class names, namespaces, patterns)
→ Applies universal + profile rules
→ Writes to .ai-workflow/flows/
AI presents for review:
→ Shows generated files
→ Developer: [A]ccept / [F]eedback / [R]eject
→ Iterates until accepted
Developer uses flows by asking:
→ "Design a task called my-task"
→ "Implement the next task flow for my-task"
→ "Validate my-task for PR"
Edit .ai-workflow/rules.md in your project:
## Custom Rule: No console.log in production
Severity: error
Check: No `console.log` statements in `src/` unless inside `if (DEBUG)`.Create .ai-workflow/flows/my-flow.md:
# Flow: Security Audit
## Purpose
Run security checks on new tasks.
## Phases
1. Scan for SQL injection risks
2. Check auth middleware coverage
3. Validate input sanitization
4. Report findingsSee docs/how-to-create-profile.md.
- Quick Start — 5-minute setup
- How to Create a Profile — Add support for your tech stack
- How to Write Rules — Define project conventions
- How to Add a Flow — Extend the workflow
- How to Customize — Project-level overrides
- Architecture Explained — Why markdown-native?
Profiles are community-contributed. To add a new profile:
- Copy
profiles/generic/as a starting point - Edit
README.md,discovery.md,rules.md - Customize skeletons for your tech stack
- Submit a pull request
MIT