AI client guides
How to check a story in the assistant you draft in, how to let a coding agent check a story before it builds, and how to read what Vindex sends back.
Writing better stories
How do I check a story before it goes into Jira, Azure DevOps, or Asana?
Draft the story in your assistant, run the score-story command, and fix what the result names before the story exists in the tracker. Nothing downstream, no refinement slot, no plugin comment, ever sees the version that was not ready.
How do I write testable acceptance criteria with my AI assistant?
Assistants draft acceptance criteria quickly and tend toward wishful ones. How to steer the draft to one observable outcome per criterion, and how the Testable reasoning from Vindex names exactly which criterion nobody could verify.
Agentic development
How do I let my coding agent check a story is ready before it builds?
Give Claude Code, Codex, Cursor, or Copilot the Vindex MCP server and one rule: score the story before writing code, proceed on Healthy, report and ask otherwise. What the agent sends, what comes back, and a real story it would have stopped on.
How do I put a Vindex ready check into my agent's standing instructions?
The three-line rule that makes the ready check permanent, and the file each agent reads it from: CLAUDE.md, AGENTS.md, Cursor rules, or copilot-instructions.md. How to make the threshold your team's and how to confirm the rule fires.
Not connected yet?
Every guide assumes your assistant can call Vindex. The connect pages take about two minutes per client, and the connection reference has the endpoint, sign-in, and tool schemas.