A workflow that turns an approved planning source and understanding of the current codebase into implementation specifications. The specifications are published or updated in the project's issue tracker.

Use it to turn a Wayfinder map or other explicit plan into one or more specs, after gathering repository and tracker context and checking whether related specs already exist.

It gives coding work a durable, shared description instead of leaving requirements in conversation notes. It also adapts the specification to the project's terminology and existing tracker records.

How sponge-b0b/Polaris configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to sponge-b0b/Polaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/to-specs/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sponge-b0b/Polaris

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-specs/github.svg)](https://agentmods.dev/skills/sponge-b0b/polaris/to-specs)

Your own site

<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-specs"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-specs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-specs"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,813 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.02813
Opus 5.5	$0.00011	$0.01125
Sonnet 5.5	$0.00006	$0.00563
Haiku 4.5	$0.00003	$0.00281

Measured today against content hash 02c6d176c550, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

to-specs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/to-specs/SKILL.md · 322 lines

How it starts

The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.

To Specs

Authoritative procedure composition

Before executing this skill, read all of these files in full:

.agents/skills/to-specs/PROCEDURE.md
.agents/skills/to-specs/CONTROL_PLANE.md
.agents/skills/to-specs/PROVIDER_CLOSURE.md

PROCEDURE.md preserves the complete established $to-specs lifecycle. CONTROL_PLANE.md preserves the previously authoritative entrypoint through the machine-enforced cross-Spec and intra-Spec execution-feasibility, legacy-completed compatibility, planning-worktree, and shared Human Handoff repairs. PROVIDER_CLOSURE.md adds the mandatory concrete production-provider/composition trace, ownership-homogeneous material-cell rule, and deferred-composition boundary.

This SKILL.md is now the authoritative entrypoint and adds the machine-enforced durable routing-defect inventory gate below. On conflict, this file wins. Failure to load any retained file is a Hard Blocker.

All requirements in the retained files remain mandatory unless explicitly overridden here.

Retained execution-feasibility contract

Local structural success is not sufficient. The production success and proof path must be traced before readiness. Every topology-bearing unit still uses provider_requirements, local_provider_requirements, and, only when neither kind of provider is required, local_completion_attestation.

The same fail-closed rule applies inside one Spec. A distinct local provider must be reachable through the consumer unit's transitive depends_on prerequisites; a downstream or unrelated local execution unit is invalid. Successful retained feasibility still requires:

SPEC EXECUTION FEASIBILITY: VALID
Unprotected pending provider requirements: 0
Unprotected downstream local provider requirements: 0

Immutable legacy-completed Specs

A CLOSED Spec that predates spec-execution-topology:v1 is immutable delivery history. legacy_completed.result and legacy_completed.completion_basis remain required by the retained compatibility path, which does not create retroactive execution-unit authority. Every OPEN Spec must contain a current spec-execution-topology:v1 marker, and a CLOSED Spec that already contains topology must still use normal unit_analysis.

Read the full file on GitHub · 322 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today Changed · +11 lines 02c6d176c550
3d ago Changed · +87 lines f64e7a1f60ee
5d ago Changed · +37 lines e5543c4c7643
6d ago Changed · -263 lines 6fdd2946b938
7d ago Changed · +128 lines 7140483eeecc
8d ago Changed · -127 lines · -3 tokens per session 4787d5e14552
11d ago Changed · +44 lines ba692c2aa618
22d ago Changed · +3 lines 6e4fb05d73d1
25d ago Changed · +67 lines 8366fd9110b6
1mo ago First seen · 335 lines · 31 tokens per session scan A ecac803be7c4

Subscribe to this mod's changes

to-specs is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 2,813 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

Polaris: Skill for Claude Code