CoFix / Product / Developer Workflow
Developer Workflow

Your way of working, loaded into Claude Code.

Workflow skills for every developer's coding assistant, a playbook of rules the agent follows in each project, and MCP connectors per member. Admins choose what's on, and every session starts with it.

Get startedSee pricing
 workflow / skills
Plan before codeon
Branch namingon
Commit message styleon
Write tests firstoff
PR description templateon
Security checkliston
Update the docson
Release notesoff

Example skill names replace with real ones

Org wideeach workflow skill on or off for everyone
5 stagesrules for diagnosing, planning, building, verifying and opening pull requests
1 token eachper developer or machine, revoked one at a time
4 assistantsClaude, ChatGPT, GitHub Copilot and Gemini CLI, over MCP
How it works

From your conventions to every session.

  1. Choose the skills

    Admins switch each workflow skill on or off for the whole organisation.

  2. Write the playbook

    Per project, rules for each stage of the agent's work: diagnosing, planning, building, verifying and opening pull requests. Start from a template.

  3. Issue tokens

    One token per developer or machine, so revoking one stops that machine and no other.

  4. Start a session

    The Claude Code plugin loads the enabled skills when a session starts. MCP connectors give Claude, ChatGPT, Copilot and Gemini CLI the same access as the web app.

  5. Review

    Pull requests from people and from the agent are reviewed against the same standards in Security.

What you get

Everything in Developer Workflow.

Workflow skills

What your developers' AI assistant is told before it writes anything: write tests first, find the root cause, and so on. Each skill is on or off for the whole organisation.

Playbook per project

Rules the agent follows at each stage of its work: diagnosing, planning, building, verifying and opening pull requests. Start from a template, and a repository's AGENTS.md is read too.

Per developer tokens

One token per developer or machine. Revoking one stops that machine and no other.

Claude Code plugin

Loads the enabled skills when a session starts.

MCP connectors

One per member for Claude, ChatGPT, GitHub Copilot or Gemini CLI, with the same access checks as the web app.

Repositories per project

GitHub, Bitbucket and Azure DevOps repositories linked to each project, tagged Frontend, Backend, Mobile or Shared.

Coming soon
Meeting notes: record, extract and route to worklog, tickets or knowledge
In depth

A closer look.

Playbook

Rules for each stage of the agent's work, per project.

The playbook tells the agent how this project is worked on: how to diagnose, what a plan must contain, how to build, what verifying means here and what a pull request must say. Start from a template and edit. A repository's AGENTS.md file is read as well, so conventions already written down are not written twice.

  • Diagnosing, planning, building, verifying and opening pull requests
  • Start from a template
  • AGENTS.md is read too
  • Per project, so a mobile app and an API can differ
 project / web-app / playbook
DiagnoseReproduce the failure before naming a causerule
PlanList the files to touch and the tests to addrule
BuildThe smallest change that makes the tests passrule
VerifyRun the whole suite, not just the changed filerule
Pull requestState the risk and how to roll backrule
Also readAGENTS.md in the repositoryautomatic

Example rules, started from the default template

Skills and tokens

Every session starts with your way of working.

Workflow skills are what a developer's coding assistant is told before it writes anything. Admins switch each one on or off for the whole organisation, and the Claude Code plugin loads the enabled set when a session starts. Each developer or machine uses its own token, so revoking one stops that machine and no other.

  • Skills on or off for the whole organisation
  • Loaded by the Claude Code plugin at session start
  • One token per developer or machine
  • MCP connectors with the same access as the web app
 workflow / tokens
ActivePriya R. · laptop · Claude Codeused 2m ago
ActiveJonas L. · laptop · Claude Codeused today
RevokedBuild agent · shared runneryesterday
Session startEnabled skills loaded by the pluginorganisation wide

Example data

Connects to

The tools your developers already open.

Claude CodeThe plugin loads the enabled skills when a session starts.
ClaudeMCP connector per member, with the same access as the web app.
ChatGPTMCP connector per member, with the same access as the web app.
GitHub CopilotMCP connector per member, with the same access as the web app.
Gemini CLIMCP connector per member, with the same access as the web app.
GitHubRepositories linked per project, tagged Frontend, Backend, Mobile or Shared.
BitbucketRepositories linked per project.
Azure DevOpsRepositories linked per project.
Who uses it

Your conventions, wherever the code is written.

For engineering teams →Your team's way of working in every Claude Code session, and a playbook the agent follows.For agencies →A playbook per client project, so each codebase is worked on its own way.
Questions

Developer Workflow FAQ.

What is a workflow skill?

Instructions your developers' coding assistant receives before it writes anything: write tests first, find the root cause, follow the branch naming, and so on. Admins switch each skill on or off for the whole organisation.

How do skills reach Claude Code?

Through the Claude Code plugin, which loads the enabled skills when a session starts. Each developer or machine uses its own token.

What is the playbook?

Rules the agent follows in one project at each stage of its work: diagnosing, planning, building, verifying and opening pull requests. Start from a template and edit. A repository's AGENTS.md file is read too.

Which assistants work with the MCP connectors?

Claude, ChatGPT, GitHub Copilot and Gemini CLI. One connector per member, signed in as that member, with the same access checks as the web app, reaching knowledge bases, tickets and the work log.

What happens when someone leaves?

Revoke their token and that machine stops. No other token is affected.

Is there a seat charge?

No. Developer Workflow has no seat line. The agent's work counts toward AI usage.

Part of one workspace

Works with the rest of CoFix.

Knowledge Base →Knowledge bases with a graph, AI chat, a health score and MCP connectors for Claude, ChatGPT, Copilot and Gemini.Security →AI code review on pull requests against standards you control.Platform →Multi tenant, roles, subscriptions, notifications and audit logs.