From aed600abd2a4809e126ff23315081bc0356cd6bc Mon Sep 17 00:00:00 2001 From: VinPropane Date: Fri, 17 Apr 2026 21:19:40 -0400 Subject: [PATCH] =?UTF-8?q?chore:=20story=20kickoff=20=E2=80=94=20ask=20us?= =?UTF-8?q?er=20when=20unclear=20or=20decision=20needed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .cursor/rules/story-kickoff.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.cursor/rules/story-kickoff.md b/.cursor/rules/story-kickoff.md index 5017427..d7bc635 100644 --- a/.cursor/rules/story-kickoff.md +++ b/.cursor/rules/story-kickoff.md @@ -7,6 +7,11 @@ alwaysApply: true When the user starts work on a **Linear issue** (e.g. issue key `NEO-5`, phrases like “begin work on story”, “implement NEO-…”), run this sequence **before** writing or changing application code. +## Clarifications (ask the user) + +- During kickoff and while drafting the plan, **ask the user** about anything **unclear**, **underspecified**, or that **needs a decision** (scope, behavior, acceptance criteria, priorities, trade-offs, or what is out of scope). Do not guess or pick silent defaults when the issue, Linear notes, or repo context do not settle it. +- Use **concrete questions**, often with short options when helpful; group related questions so the user can answer in one pass. + ## 1. Load Linear context - Fetch the issue when possible (Linear MCP `get_issue` / `list_issues`, server **`plugin-linear-linear`**), or use a URL / pasted description the user provides.