{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "llopresto87-cypress--route-risky-change-spec-first",
 "repo": "llopresto87/Cypress",
 "repo_url": "https://github.com/llopresto87/Cypress",
 "repo_slug": "llopresto87-cypress",
 "title": "Route a risky change through spec and failing test first",
 "page_title": "How to route a risky change through spec and failing test first with Cypress",
 "summary": "Sorts a change into a risk tier, then requires a specification and failing test before code for high-risk work.",
 "who": "A developer about to change architecture or a contract in a shared repository who wants the AI session to slow down and write a spec first.",
 "problem": "An AI session can start editing code for a risky change before anyone has written down what the change should do.",
 "outcome": "For a T3 change, the session writes a specification and a failing test before the code, and separate reviewer workers check the result.",
 "steps": [
  "Install the workflow with `./Cypress/install.sh claude-code --project-dir /path/to/your/project`.",
  "Open a Claude Code session rooted at your project.",
  "Describe the change and ask the session to classify it into a risk tier first.",
  "For a T3 change, confirm the session wrote a specification and a failing test before any code edit.",
  "Ask the reviewer worker to check the change against the written specification."
 ],
 "agent_prompt": "In the Cypress-installed repo at <project-path>, ask a Claude Code session to classify and then implement the change described in <change-description> following the T3 process. Expected output: a specification file and a failing test committed or saved before the implementation. Verify that the failing test exists and fails before the code change is made.",
 "agents": [
  "claude-code"
 ],
 "difficulty": "Advanced",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README says the tier choice and the order of spec and test are requested of the model, and no tool checks them, so you must verify the order yourself.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "python",
 "requirements": [
  "bash",
  "Python 3.14 or newer on PATH",
  "git, to clone the repository",
  "Claude Code or another supported coding tool, with a session rooted at your project"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/llopresto87-cypress/route-risky-change-spec-first/",
 "md": "https://dedupedai.com/use-cases/llopresto87-cypress/route-risky-change-spec-first/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/llopresto87-cypress--route-risky-change-spec-first.json",
 "api_version": "v1"
}