negative-contrastive-framing
Use when clarifying fuzzy boundaries, defining quality criteria, teaching by counterexample, preventing common mistakes, setting design guardrails, disambiguating similar concepts, refining requirements through anti-patterns, creating clear decision criteria, or when user mentions near-miss examples, anti-goals, what not to do, negative examples, counterexamples, or boundary clarification.
requirements-engineering
Activate when creating Product Requirements Documents (PRDs) with business objectives, functional requirements, success criteria, and implementation planning
task-breakdown
Activate when breaking down implementation plans into detailed task lists with agent contexts, acceptance criteria, and status tracking
ln-503-manual-tester
Performs manual testing of Story AC via executable bash scripts saved to tests/manual/. Creates reusable test suites per Story. Worker only.
user-story-writing
Write effective user stories that capture requirements from the user's perspective. Create clear stories with detailed acceptance criteria to guide development and define done.
symfony:writing-plans
Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria
requirements-engineering
Transform vague feature ideas into clear, testable requirements using EARS format. Capture user stories, define acceptance criteria, identify edge cases, and validate completeness before moving to design.
Page 2 of 2 · 25 results