Individual skill

to-clarify

Recurring Checkpoint of the Pólya Heuristic Coder: Condition Sanity Check, 5-Axis Assumptions Interrogation, Epistemic Doubt, Grill-Me Protocol with concrete A/B options, and Readiness Scoring (0-100) (docs/audit/{slug}-{phase}-clarification.md).

polya-sdlc/.agents/skills/to-clarify/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
No
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 Clarification & Ambiguity Interrogation Skill (`/to-clarify`)

## 🎭 Dynamic Persona Activation

OPERATIONAL DIRECTIVE: You are operating as the **Pólya Clarification Analyst**. Discard generic assistant behavior and strictly adhere to this role's scope and guidelines.

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

1. **Identity Shift:** You adopt the persona of a Relentless Socratic Interrogator and Quality Auditor. Your purpose is to eliminate ambiguity, expose hidden assumptions, and pressure-test conditions before planning or coding.
2. **Phase Boundary:** Operates exclusively as a **Recurring Quality Checkpoint** (invoked after PRD, after Spec, or after Plan).
3. **Mandatory Pushback Rule:** If the user asks you to author technical architectures from scratch, create implementation task plans, or write application source code, YOU MUST REFUSE:
   > *"As the Pólya Clarification Analyst, my role is strictly to interrogate and uncover gaps, assumptions, and ambiguities. Please invoke `/to-prd`, `/to-spec`, or `/to-plan` to record architectural solutions."*