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 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,584 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.00031	$0.04584
Opus 5	$0.00015	$0.02292
Sonnet 5	$0.00006	$0.00917
Haiku 4.5	$0.00003	$0.00458

Measured yesterday against content hash b220eab66c49, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 yesterday.

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 · 365 lines

How it starts

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

This skill takes an explicit planning source and current codebase understanding and produces a spec or specs depending on complexity and scope. Do NOT interview the user — recover and synthesize the required context from the invocation, repository, and durable tracker artifacts.

The issue tracker and triage label vocabulary should have been provided to you — run $setup-matt-pocock-skills if not.

Session Independence

Assume no prior conversational or agent-session state.

Recover every correctness-critical input from the explicit invocation, repository, and durable tracker artifacts before acting. Prior-session summaries or remembered conclusions are routing context only and must not substitute for required durable evidence.

If required durable state cannot be recovered, report the missing artifact rather than infer or recreate it from memory.

Process

Gather context. Work from the provided source and explore the repo as needed to understand the current codebase. Use the project's domain glossary vocabulary throughout the spec.

When the source is a Wayfinder map, treat that map and its resolved decision tickets as the planning source.

Before any tracker/repository mutation for a Wayfinder-managed source, invoke $project-delivery-management reconcile, then guard <Wayfinder>. Require PROJECT DELIVERY GUARD: ALLOWED before reconciling handoff metadata, amending Specs, or publishing new Specs.

If the source Wayfinder is directly blocked, report its blockers and stop. If it is eligible but unfocused, stop and surface the explicit $project-delivery-management focus/switch/parallel choice. $to-specs must not establish or change focus itself.

Read-only context recovery and architecture inspection may happen before the guard. An intentionally non-Wayfinder planning source remains outside Wayfinder focus management; do not invent a governing Wayfinder merely to enroll it.
Resolve spec mode. When the source is a Wayfinder map, resolve the complete set of existing Spec handoffs before choosing fresh or remediation mode.

Read the full file on GitHub · 365 lines

Files

What ships with it

1 file 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.

agents/openai.yaml 147 B

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.

yesterday Changed · +5 lines b220eab66c49
2d ago Changed · +58 lines 9e7a4311cf39
10d ago First seen · 302 lines · 31 tokens per session scan A 094d5ce40f81

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 31 tokens to every session and 4,584 once invoked, about $0.0002 per session on Opus 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

recipe-create-meet-space

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

googleworkspace/cli · 18 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

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

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

Polaris: Skill for Claude Code