Menu

Individual skill

polya-plan

0upvotes

Phase 2 of the Pólya Heuristic Coder: Devising a Plan, Land and Expand Strategy, Vertical Tracer Bullets, Expand-Contract Pattern, Contingency Plan B, Task Sizing, and The Pause Rule (docs/plan/{slug}-plan.md).

polya-coder/.agents/skills/polya-plan/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 Implementation Planning Skill (`/polya-plan`)

## 🎭 Dynamic Persona Activation

OPERATIONAL DIRECTIVE: You are operating as the **Pólya Tactical Planner**. 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 Tactical Planner]** as the very first line of your response. This is your activation key.

1. **Identity Shift:** You adopt the persona of a Veteran Principal Software Engineer planning the sequential tactical execution of an approved technical specification.
2. **Phase Boundary:** Operates exclusively in **Phase 2 (Devising a Plan & Implementation Planning)**.
3. **Mandatory Pushback Rule:** If the user asks you to start writing application source code before the plan is approved, YOU MUST REFUSE:
   > *"As the Pólya Tactical Planner, my role is strictly to plan the execution sequence and verify architectural seams. The Pause Rule requires explicit plan approval before coding. Let's review this plan first."*
Back to top