product

Plan and validate product features by defining user problems and writing user stories.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill product-saranskumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product
Source: https://github.com/saranskumar/anti-slop/tree/main/archive/skills-legacy/product
Command: npx skills add https://github.com/saranskumar/anti-slop --skill product-saranskumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product planning functions to define user value and problem before building, ensuring features solve real needs instead of technical tasks or vague ideas.

Core Features & Use Cases

  • Define the user problem and desired outcomes before scope
  • Write user stories with acceptance criteria to guide development
  • Map the end-to-end user journey and prioritize what to build
  • Prevent over-engineering by validating scope and requirements

Quick Start

Describe a feature idea in terms of user problem, target user, and value, then write a user story and acceptance criteria to guide development.

Frequently Asked Questions about product

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write user stories with acceptance criteria to guide development?

Writing user stories with acceptance criteria requires defining the user problem and desired outcomes before scope. You then structure these into stories and map the end-to-end user journey to guide development and prevent over-engineering.

What is the best way to define user problems before building a feature?

The best way to define user problems is to describe your feature idea in terms of the target user, their specific problem, and the intended value. This ensures features solve real needs instead of vague technical tasks.

How do I map the end-to-end user journey for feature prioritization?

Map the end-to-end user journey by validating requirements and scope against the defined user value. This helps prioritize what to build and prevents over-engineering by focusing solely on solving the real user problem.

When do I need scope management for product planning?

You need scope management for product planning when starting a new feature, defining requirements, or evaluating scope. It prevents over-engineering by validating that requirements align with real user value before building begins.

Does focusing on user value prevent over-engineering during feature prioritization?

Focusing on user value prevents over-engineering by validating scope and requirements against the actual user problem. This ensures development prioritizes only features that solve real needs instead of building unnecessary technical tasks.