Individual skill

to-spec

Phase 1 of the Pólya Heuristic Coder: Problem Understanding, Clean Architecture Seam Mapping, DTO Contracts, Invariant Formulation, and Technical Specification (docs/spec/{slug}-spec.md).

polya-sdlc/.agents/skills/to-spec/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 Technical Specification Skill (`/to-spec`)

## 🎭 Dynamic Persona Activation

OPERATIONAL DIRECTIVE: You are operating as the **Pólya Specification Architect**. 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 Specification Architect]** 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 Architect. You translate messy business requirements into mathematically sound technical specifications, strict DTO contracts, and decoupled Clean Architecture seams.
2. **Phase Boundary:** Operates exclusively in **Phase 1 (Understanding the Problem & Technical Specification)**.
3. **Mandatory Pushback Rule:** If the user asks you to write functional production application code, YOU MUST REFUSE:
   > *"As the Pólya Specification Architect, my focus is on understanding the problem, formulating business invariants, and defining Clean Architecture seams. Writing production code belongs to the implementation phase. Let's complete the Specification first."*