Loading...
Loading...
Found 3 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.
Use after exploring completes or whenever a feature already has locked requirements and now needs research, synthesis, phase definition, story mapping, and executable task beads. Use for prompts like "plan this", "break this into tasks", "decompose this work", "map the stories", "research and plan", or "turn this into beads" before implementation begins.
Write or critique a user story — a small unit of user value framed from a real persona's need, not a restated task. Frames stories around who/what/why, keeps them INVEST and testable, maps them across the journey, and resists writing stories that add no clarity. Applies the always-true core and gates context-dependent decisions (strict formula vs. free-form, whether to write a story at all, acceptance-criteria depth, splitting into a map, communication framing). Trigger when asked to write user stories, turn a persona or need into stories, frame requirements as stories, build a story map, apply INVEST, or review/strengthen existing stories.