Skip to main content
affpapa.org
RU EN
skill CX Codex

to-spec · pandoscope — Claude Code skill: what it does, how to install

Generates a self-contained feature spec from the current conversation and codebase without running a repetitive user interview.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add pandoscope/skills --skill to-spec -a claude-code
Open on GitHub

What to-spec does

This skill synthesizes a PRD directly from active chat context and repo inspection. Instead of questioning the user, it extracts established requirements into structured sections: problem statement, solution, extensive user stories, implementation decisions, test seams, and scope limits.

Every requirement must pass a reproducibility litmus test: two independent implementers should build nearly identical outcomes. The skill references repo ADRs, pins project terminology using uvx disambiguate, and blocks progress if no grilling session exists in context unless explicitly bypassed.

Without tracker rules defined in AGENTS.md, the skill cannot publish tickets labeled ready-for-agent. Implementation notes deliberately exclude file paths and transient code snippets, keeping only state machines, schemas, or compact prototype shapes.

What it helps with

  • generate a complete PRD from chat history without prompting interviews
  • define test seams before starting feature implementation
  • enforce self-contained specifications that survive handoffs
  • pin feature decisions to project ADRs and glossary terms

Example prompts for the agent

  • Generate a spec from our chat about user authentication
  • Turn our discussion into a PRD and publish it to the tracker
  • Create a ready-for-agent spec for the background export worker

How to install to-spec

1Skills CLI (Vercel)

npx skills add pandoscope/skills --skill to-spec -a claude-code

2Manually: put the files in place

~/.claude/skills/to-spec/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/to-spec/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about to-spec

How do I install to-spec in Claude Code?

Run npx skills add pandoscope/skills --skill to-spec -a claude-code in your terminal. You can also place the skill file directly at ~/.claude/skills/to-spec/SKILL.md.

What does the to-spec skill do?

It converts an ongoing conversation into a detailed specification with user stories and architectural constraints. It strictly skips follow-up interviews, assembling details from context already provided.

What happens if there is no grilling session in the context?

The skill triggers a gate prompt asking whether to skip the missing grilling session. If confirmed, it logs the omission in the Further Notes section of the final document.

Source text

SKILL.md · MIT 
---
name: to-spec
description: Turn the current conversation into a spec published to the project tracker — no interview, just synthesis of what was already discussed.
metadata.derived-from: https://github.com/mattpocock/skills/blob/391a2701dd948f94f56a39f7533f8eea9a859c87/skills/engineering/to-spec/SKILL.md
metadata.derivation-note: Adds reproducibility invariant + self-containedness litmus test (see derived to-tickets) + grilling gate. Tracker deferred to consumer AGENTS.md; vocabulary pinned to docs/glossary (`uvx disambiguate`), decisions to writing-adrs. Upstream `/setup-matt-pocock-skills` dropped. Caveman-condensed.
disable-model-invocation: true
---

# To Spec

Produce spec (aka PRD) from current conversation + codebase understanding. Do NOT interview user — synthesize what you already know.

## Reproducibility invariant

Spec — and tickets later derived from it — must be **self-contained**: replayed by any implementer, human or agent, builds roughly same application. Every outcome-shaping decision lives in spec itself, or durable docs it references — ADRs (`writing-adrs`), glossary terms (`docs/glossary/`). Never conversation context, tribal knowledge, implementer discretion.

**Litmus test:** two independent implementers could build meaningfully different things → spec underspecified. Add decision to spec, or record as ADR/glossary term + reference.

## Grilling gate

Spec is load-bearing. No grilling session (`docs/glossary/grilling-session.md`) in context → stop, ask user: "No grilling session found — really skip?" Proceed only on explicit confirmation; note skip in Further Notes.

## Process

1. Explore repo if not already done. Use glossary vocabulary (`uvx disambiguate <term>`) throughout; respect ADRs in touched area.

2. Sketch seams for testing the feature. Prefer existing seams; new seams at highest point possible. Fewer seams better — ideal is one.

   Check seams with user.

3. Write spec per template — written and checked with the `writing-prose` skill if available, surface `ticket`; precision and understandability must not suffer. Apply litmus test to every section, publish per consumer repo's tracker conventions (AGENTS.md). Apply `ready-for-agent` label — no further triage.

Spec template:

```markdown
## Problem Statement

Problem, from user's perspective.

## Solution

Solution, from user's perspective.

## User Stories

LONG numbered list: "As an <actor>, I want <feature>, so that <benefit>".
Example: "As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending."
Extremely extensive — cover all aspects.

## Implementation Decisions

Decisions made: modules built/modified, interfaces, technical clarifications, architecture, schema changes, API contracts, specific interactions.

Hard-to-reverse or surprising decisions → also record as ADR (`writing-adrs`) + reference. Decision only in conversation, not listed here → fails litmus test — write it down.

No file paths/code snippets — stale fast. Exception: prototype snippet encoding a decision more precisely than prose (state machine, reducer, schema, type shape) → inline within relevant decision, note prototype origin, trim to decision-rich parts.

## Testing Decisions

What makes a good test (external behavior only, not implementation details), which modules tested, prior art in codebase.

## Out of Scope

What this spec excludes.

## Further Notes

Anything else.
```

© pandoscope · MIT · pandoscope/skills

Similar skills

All skills for Writing and docs →

to-spec by other authors comes first.

to-spec Matt Pocock Turns the current conversation and repository context into a spec, then publishes it to the project issue tracker. Use it when a feature discussion is ready to hand off to an agent. 715,388installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. 1,219,756installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. 414,180installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. 1,038,491installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs domain-modeling Matt Pocock This skill sharpens project terminology, maintains GLOSSARY.md, and records selected architecture decisions in ADRs. Use it while the domain model is changing. 876,391installs

From the same set8

caveman caveman switches agent chat to compact, easy-to-parse prose while keeping technical meaning. Use it when extra wording gets in the way. CX Codex +1 2,000installs tdd Enforces strict red-green-refactor cycles with an auditable commit trail. Keeps LLM agents from writing unverified production code. CX Codex +1 1,900installs documenting-decisions This skill marks important choices in agent-written code and turns them into a review log. Use it during planning, implementation, fixes, or diff review. CX Codex +1 1,900installs domain-modeling A skill that pins down your project's terminology in a glossary and records architectural decisions while you design. CX Codex +1 1,800installs grilling Stress-tests technical plans, decisions, or ideas through scored multiple-choice questions. It helps uncover blind spots before writing code. CX Codex +1 1,700installs to-tickets Turns an approved plan, spec, or conversation into vertical tickets with blocking edges, then publishes them to the project tracker. CX Codex +1 1,700installs writing-adrs Sets the format, numbering and when-to-write rules for Architecture Decision Records. Useful when architectural choices keep getting lost in chat threads. CX Codex +1 1,700installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor