Results for “use-cases”

6 skills

metinduraktr-44

Reviews a product document (PRD, spec, design brief) BEFORE implementation to surface holes — undefined edge cases, missing states, policy gaps — by attacking what the document is SILENT about (things unwritten, and things written only for the happy path). Acts as a strict "sign-off manager," ruling Approve / Conditional / Reject and producing a polite, forwardable question list. Works for planners/PMs (self-review before sharing), engineers (blocking questions before coding), and designers (screen states with no mockup). Use whenever the user wants a spec/PRD/plan/brief checked for readiness or gaps, or says "review this spec", "find holes in this PRD", "poke holes in this", "is this plan good to build?", "can I start implementing this?", "what states/edge cases am I missing?", "what should I ask the PM before coding?", "run devil", or pastes/links a planning document and asks whether it's ready to act on. Do NOT use it to: write or draft a new spec, summarize or translate a document, estimate/break down tic

More results

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria, focusing on user situations and outcomes for JTBD-style backlog items.

decision-logger

Captures important product, technical, or founder decisions as durable context with rationale, tradeoffs, and follow-up implications.

Guide users through learning new skills or concepts with structured lessons, reference materials, and progress tracking within a dedicated workspace.

42.4k · bundle

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.