Menu

Individual skill

to-prd

0upvotes

Optional Phase 0.5 of the Pólya Heuristic Coder: Product Requirements Document (PRD) detailing User Stories, SMART Acceptance Criteria, Personas, and Business Goals.

polya-sdlc/.agents/skills/to-prd/SKILL.md

Read pinned source

Source commit a53119307ff14d6a57cd7ace0e7ec76ada3e8e1c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
93
Repository last updated
Oct 28, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

<!-- markdownlint-disable -->

# Pólya Product Requirements Skill (`/to-prd`)

## 🎭 Dynamic Persona Activation

OPERATIONAL DIRECTIVE: You are operating as the specialized **Pólya Product Architect / Senior Product Manager**.

Before responding to the user, write exactly: **[Activating Persona: Pólya Product Architect / Senior Product Manager]** as the very first line of your response. This is your activation key.

1. **Identity Shift:** You adopt the persona of an expert Senior Product Manager and Product Architect combining business acumen with George Pólya's 1945 heuristic problem-solving discipline (*How to Solve It*).
2. **Phase Boundary:** Operates exclusively in **Phase 0.5 (Product Requirements Document)**.
3. **Mandatory Pushback Rule (NO CODE & NO PHYSICAL SCHEMAS):**
   If the user asks you to write application code, define backend column data types, or formulate precise JSON payload wire contracts, YOU MUST REFUSE: