bdd-core
01Cursor rule Cursor
USE WHEN starting feature work, running /bdd, resuming a BDD ticket, or user says 'add', 'implement', 'build', 'feature', 'resume', 'continue'. Orchestrates BDD phases.
Cursor rule Cursor
USE WHEN starting feature work, running /bdd, resuming a BDD ticket, or user says 'add', 'implement', 'build', 'feature', 'resume', 'continue'. Orchestrates BDD phases.
Cursor rule Cursor
USE WHEN in BDD intake phase OR ticket has phase:intake. Guides discovery and context gathering for features.
Cursor rule Cursor
USE WHEN in BDD done phase (verify.md exists). Close the ticket — verification already happened in verify.
Cursor rule Cursor
USE WHEN in BDD plan-implementation phase. Author impl-plan.md, run figure-it-out on load-bearing choices, ADR lifecycle, review before implement.
Cursor rule Cursor
USE WHEN in BDD define-behavior or scenario-gate phase. Guides Given/When/Then scenario creation and validation.
Cursor rule Cursor
USE WHEN BDD thresholds exceeded (2+ stories, >15 scenarios, >20 tasks). Split protocol and examples.
Cursor rule Cursor
USE WHEN in BDD implement phase. RED/GREEN TDD cycle; run /refactor after GREEN.
Cursor rule Cursor
USE WHEN in BDD verify phase OR all scenarios marked [x]. Evidence gate — cross-scenario refactor, then /verify and /audit.
Cursor rule Cursor
Collaborative brainstorming and rubber-ducking — divergence-first thinking partner. Use when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction ('brainstorm', 'rubber duck', 'help me think', 'explore options', 'what are the tradeoffs').
Cursor rule Cursor
@.safeword/SAFEWORD.md.
Cursor rule Cursor
Finds the real cause of a bug, in four steps, before you touch a fix. Use when encountering bugs, test failures, unexpected behavior, or when previous fix attempts failed. Enforces investigate-first discipline ('debug this', 'fix this error', 'test is failing', 'not working').
Cursor rule Cursor
Extract tacit knowledge through non-obvious microquestions — things only the user knows that can't be found in code, docs, or research. Use when about to guess at intent, context, or constraints, or when user says 'ask me', 'what do you need to know', 'what's missing'. Skips questions answerable by reading the…
Cursor rule Cursor
Explore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection. Looks up current docs and recent research, weighs options on correctness and…
Cursor rule Cursor
Internal fallback used only right after the shared review coordinator reports it's run out of reviewer routes. Not something a user invokes directly.
Cursor rule Cursor
Deep quality review of any work-product — code, docs, specs, plans, decisions — with web research. Use when explicitly verifying against latest docs ('double check against latest', 'verify versions', 'check security'), pressure-testing correctness and elegance, or needing deeper analysis beyond the automatic hook.…