Loading...
Loading...
Found 2 Skills
Use when working on Laminar demands via the remote Laminar MCP and you see wrong or empty client/product scope, plans from source-context lists without per-id loads, needless raw transcripts, same-step or same-release story-map peers, anchored ADR conflicts, MCP transitions/assignments, broken or silent MCP, or mentions of Laminar MCP, demands, TAL-* ids, story map, anchored or source context, or Laminar handoff.
Drafts initial ticket requirements by asking targeted clarifying questions and producing a structured ticket with Title, Body, and Acceptance Criteria. Use when a user has a request that needs to be converted into a clear tracker-ready ticket without codebase or architecture analysis.