Every registered collaboration framework in one place. Browse dimensions, compare frameworks side-by-side, or contribute your own.
Describe your task and see what each framework's best-matching cycle looks like, side by side.
Any collaboration framework with named dimensions can be registered. Two paths: submit a PR yourself, or ask your AI agent to build and test it for you.
Fork the repo and create frameworks/your-id.yaml.
Required fields: id (kebab-case),
name, version,
contributor, description,
dimensions (array with key, label, description, canonical_order).
id: my-framework
name: My Framework
version: "1.0.0"
contributor: Your Name
description: >
One-paragraph description of the
framework and its goals.
dimensions:
- key: plan
label: Plan
description: >
What is decided before starting?
canonical_order: 1
- key: execute
label: Execute
description: >
How is the work carried out?
canonical_order: 2
- key: review
label: Review
description: >
How is the output evaluated?
canonical_order: 3
Run the validation script to catch errors before opening a PR:
npm run build --workspace=packages/scorer node scripts/validate-frameworks.js
CI reruns this automatically on every PR and rejects malformed definitions.
Submit your PR. CI validates the schema, regenerates frameworks/index.json, and the new framework appears in the knowledge base and this page after merge.
If you have the Fluently MCP server connected, you can ask your agent to generate a framework YAML, validate it, and open the PR — all in one conversation. Copy the prompt below and paste it to Claude, Copilot, Cursor, or any MCP-capable agent.
I want to contribute a new collaboration framework to the Fluently knowledge base. Framework concept: [DESCRIBE YOUR FRAMEWORK HERE — e.g. "a 3-step Research framework: Question, Investigate, Synthesise"] Please: 1. Use the `get_framework_detail` tool to inspect the existing 4D framework structure as a reference. 2. Generate a valid `frameworks/[id].yaml` file following the same schema (id must be kebab-case, each dimension needs key, label, description, canonical_order). 3. Run `node scripts/validate-frameworks.js` locally to confirm the file is valid. 4. Confirm the YAML is ready to commit and provide the exact file contents. 5. If I approve, create a branch named `feat/framework-[id]`, commit the YAML, and open a GitHub PR with a short description of the framework and its intended use cases. Do not open the PR without my explicit approval.
Requires: Fluently MCP server connected + a GitHub MCP server or a PAT in your agent's settings.