agentleFS
zpower426zpower426/pmpowers/skills/product-definition/SKILL.md

product-definition

Skill0 starsChanged 7 months agoMITView on GitHub

Translate vision into rigorous, unambiguous product logic documents (PRD/User Stories), providing an accurate execution benchmark for R&D and design.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document as Contract: Do not let R&D write a single line of code until the definition is complete.

    line 20
  2. Distinctive:

    Falsifiability: If you cannot provide a criterion for "failure," the definition is not clear.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Definition: Rigorous Product Definition Guide

Definition is the "source code" for R&D.

Checklist

  1. Set Goals and Non-goals (Scope) — Clarify "what to do" and "what not to do" for this feature.
  2. Write User Stories — As a... I want to... So that...
  3. Detail Acceptance Criteria (AC) — Every functional point must be testable.
  4. Organize Core Business Logic — Use state machines, sequence diagrams, or data dictionaries.
  5. Define Performance and Non-functional Requirements — Response time, concurrency support, and data consistency.

Expert Principles

  • Document as Contract: Do not let R&D write a single line of code until the definition is complete.
  • Edge Case Coverage: A senior PM should spend 80% of their time handling the 20% of abnormal scenarios outside the Happy Path.
  • Falsifiability: If you cannot provide a criterion for "failure," the definition is not clear.

Delivery Standards

Deliverables must be saved under docs/pmpowers/specs/.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.