Check the spec-based development rules and your active work item

spec.statusReadsOnly looks things up; never changes your workspace.

What it does

Call this before changing any code. Returns the workspace policy (policy.enabled, policy.mode block|warn, policy.rules, policy.exemptPaths) and the user story or test case you declared for this branch (activeWork, null when none). When policy.enabled is true and activeWork is null, do not edit files: find or create the user story (feature.list, userstory.create) and its test cases, then call spec.start_work. Every commit must then carry the trailer line in activeWork.trailerLine (e.g. "Testmaze-Ref: AAts-…"). Pass includeMap: true once at the start of a session to also get workspaceMap, a short outline of the features and stories that already exist, so you reuse them instead of creating duplicates. Read-only.

Ask your agent

You don’t call spec.status yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:

  • “Does this project require a user story before I change code?”
  • “Which story am I working on in Test Maze right now?”

Inputs

NameTypeDescription
branch
optional
stringCurrent git branch, from git rev-parse --abbrev-ref HEAD in the repository root.
includeMap
optional
booleanAlso return workspaceMap (existing features and stories).

The MCP call

What the agent’s MCP client sends (placeholders in angle brackets):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "spec.status",
    "arguments": {
      "branch": "<branch>"
    }
  }
}

Connect your agent

npx -y @testmaze/mcp init tmt_xxx
claude mcp add tm --scope project -- npx -y @testmaze/mcp

Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.