Spec Kit, OpenSpec, BMAD or Kiro for a team, and where CRUX fits

Updated

In spec-driven development the team agrees on a written specification first, and the plan, the tasks and the code are produced from it. This page is for a developer or lead who uses such a framework, or is choosing one, and wants to know how it works once a PM and QA join.

The situation

Take a made-up team. Ryan, a developer, runs the specify step in his agent. The agent asks whether archived orders count toward the export limit. Only Emily, the PM, knows, and she does not open the repository. Ryan asks her in chat and pastes the answer into the spec. A month later QA cannot tell which lines came from Emily and which the agent guessed.

What spec-driven frameworks do well

These frameworks and CRUX share one idea: an agent needs a written understanding and a plan before it writes code.

  • GitHub Spec Kit. An MIT-licensed toolkit whose commands, run in the agent's chat, write spec.md, plan.md and tasks.md into a folder under specs/ for each feature. Its integrations page lists 41 coding agents.
  • OpenSpec. MIT-licensed, and built for existing codebases as well as new ones. Each change is a folder under openspec/changes/ with a proposal, specs, a design and tasks. Its docs list 39 tools.
  • BMAD-METHOD. Free and open source under MIT. It brings in product, architecture, UX, development and testing expertise, and needs a coding tool that supports skills. Documents go to _bmad-output/.
  • Kiro. An IDE, a CLI and a web app with its own agent. A spec is three markdown files under .kiro/specs/ in the repository. Plans run from $0 to $200 per user a month.
  • Superpowers. MIT-licensed skills that make the agent brainstorm a design, write a plan and build it test-first. The design and the plan are committed under docs/superpowers/.
  • GSD Core. An MIT-licensed framework, the successor of Get Shit Done, that runs a discuss, plan, execute and verify loop. Its state lives in a .planning/ folder.

Checked on 13 November 2026.

Spec-driven frameworks and CRUX side by side

FrameworkWhere the spec livesTeam setupLink to a trackerCost
Spec Kitspecs/<feature>/ in the repositoryA section for mixed-agent teamsCommunity extensions for Jira, Linear and Azure DevOpsMIT, free
OpenSpecopenspec/changes/ in the repositoryStores, shared planning repositories, in betaNone in its docsMIT, free
BMAD-METHOD_bmad-output/ in the repositoryA guide for adopting it across a teamThe v7 preview publishes tickets to Linear, Jira and othersMIT, free
Kiro.kiro/specs/ in the repositorySpecs are version-controlled and shareableImports Jira or Confluence requirements through MCP$0 to $200 per user a month
Superpowersdocs/superpowers/ in the repositoryNot documentedNoneMIT, free
GSD Core.planning/ in the repositoryState committed to git for team visibilityA guide for working from an issue, without a tracker integrationMIT, free
CRUXArtifacts on the task in your trackerEach status in your workflow has an owner roleJira Cloud, Linear, Plane and GitHub IssuesFree for one person; $49 or $120 per active project a month for a team

Checked on 13 November 2026.

Where they stop for a team

All six share work through git, and four of them document a team setup.

The commands run in a coding agent's chat, so the agent's questions reach the person at that agent. A PM who works in the tracker sees the result later, as a file or as issues the developer's agent created from it. Some Spec Kit extensions move a card across board columns as the developer's agent works, but we found no framework that gives each status an owner role.

Spec-driven development with Jira or Linear

Spec Kit has community extensions for both trackers. The Jira Integration extension turns spec.md into a Jira epic and the phases and tasks in tasks.md into stories and tasks, through a Jira MCP server, and moves finished tasks to Done. The community catalog lists Linear extensions too. GitHub does not maintain these extensions.

Atlassian's guide Spec-driven development in Jira puts the spec in the Jira work item itself, with its outcome, scope, constraints and acceptance criteria. BMAD's v7 preview can publish its tickets to Linear or Jira, and its docs say these options still need testing. OpenSpec documents no Linear integration, and Kiro imports Jira requirements through MCP.

CRUX takes the tracker side. The understanding, the plan and the answers are artifacts on the task, and each status in your workflow has its own instructions. Checked on 13 November 2026.

What a tracker-based workflow does differently

CRUX keeps the same discipline in Jira Cloud, Linear, Plane or GitHub Issues. It starts from what the tracker already holds: the agent reads the task, its parent and the decisions already on it.

  • Each status in your workflow has an owner role, and a person in that role starts the step.
  • The agent asks the person whose role should know, and the answers stay on the task. Nobody acts under a bot account, and text an agent wrote starts with a robot emoji, so QA can tell Emily's answers from the agent's guesses.
  • Each step leaves an artifact on the task: its result, which the next step starts from. People approve at checkpoints, and a person moves the task to the next status. CRUX does not change the tracker's settings.
  • A PM or QA engineer can run an agent on CRUX in the browser, on the project's model key, with the repository read-only.

When a spec-driven framework is the better choice

  • You work alone and want no account and no hosted service. CRUX has no self-hosted version.
  • You have no tracker, or you use Jira Server or Data Center, which CRUX does not support.
  • The project is new and has no tasks or history for an agent to read.
  • Everyone who decides requirements already reviews files in the repository.

Using both

A CRUX step that runs on your machine uses your own coding agent and checkout, where a framework's skills are installed too. We build CRUX this way: our developer step runs Superpowers' design and planning skills, and the tracker shows who owns each status and what the PM answered. That agent reads the project wiki from the checkout, because the wiki is not available over MCP. We have not tried the other frameworks with CRUX.

Next step

Start free. Then read How CRUX works. The price for a team is on the pricing page; during the beta nothing is charged. Other comparisons: task-to-PR agents and Jira MCP and your own skills.

FAQ

Does spec-driven development work for a team?

Yes, when everyone who decides requirements reads the spec files. Spec Kit, OpenSpec, BMAD and Kiro each document a team setup. It gets harder when the PM and QA work in the tracker and not in the repository.

Is CRUX a spec-driven framework?

No. It is a hosted workflow layer between a tracker and coding agents.

Does CRUX work with Kiro?

Kiro's MCP configuration takes a remote URL with an authorization header (docs), which is how CRUX connects. You connect an agent in the dashboard dialog "Connect your coding agent". We have not tested or documented Kiro yet.