Skip to content
Agentmart
Submit a tool

product-definition

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

Skill by zpower426

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/zpower426-product-definition

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Use cases: design

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/product-definition

What's inside

Skill name
product-definition
Description
Translate vision into rigorous, unambiguous product logic documents (PRD/User Stories), providing an accurate execution benchmark for R&D and design.
License
MIT
Instructions
22 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# 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/`.

From zpower426/pmpowers, MIT.

More from zpower426/pmpowers

Signals

Stars
0
Forks
1
Open issues
0
Last commit (this folder)
Mar 31, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/zpower426/pmpowers
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from zpower426

Cite this page

product-definition skill. Agent Mart. https://agentmart.dev/skills/zpower426-product-definition (last updated 2026-10-24)