Move a feature or story to a new stage

feature.set_lifecycleChanges dataCreates, updates or deletes something in your workspace.

What it does

Records where a feature, sub-feature or user story is in its life. The stages, in usual order: authoring = being written up and planned (every new feature and story starts here); in-progress = being built; verifying = built, tests are being run against it; live = released to users; deprecated = retired or replaced. Nothing is triggered automatically, so move it when the real work moves (for example to verifying when coding is done, to live after the release ships). When the workspace enforces its Definition of Ready / Done (spec policy rules requireReady / requireDone), a user story is refused a move into in-progress, verifying or live until it is Ready, and into live until it is Done; the answer is {success: false, message: what is missing} (check userstory.gates first). The feature or story must belong to the connected workspace. Returns {success, message, data: the updated feature or story}. Get the id from feature.list.

Ask your agent

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

  • “Checkout is built, mark it as being verified”
  • “The saved-card story is live now”
  • “Retire the old search feature”

Inputs

NameTypeDescription
suiteId
required
stringId of the feature, sub-feature or user story (the id from feature.list).
stage
required
enumNew stage. authoring = being written up; in-progress = being built; verifying = tests being run; live = released to users; deprecated = retired.
Allowed: authoringin-progressverifyinglivedeprecated

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "feature.set_lifecycle",
    "arguments": {
      "suiteId": "<suiteId>",
      "stage": "authoring"
    }
  }
}

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.