To Spec
Turn what has already been discussed into a spec and file it as a GitHub issue on the product repo, without interviewing the user again. Use when the user says write this up as a spec, open an issue for this, or turn this into a ticket, after the decisions are made.
Install
/plugin marketplace add frankxai/claude-skills-libraryThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add frankxai/claude-skills-library --skill to-specgit clone --depth 1 https://github.com/frankxai/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/absorbed/engineering/to-spec ~/.claude/skills/to-specPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# To spec The conversation already holds the decisions. This skill writes them down once, in the product repo's issue tracker, so the next agent picks up a spec instead of a transcript. It does not ask new questions; if a decision is missing, it is listed as open. ## Before writing 1. **Pick the repo.** The product repo that will change, verified by path, `git rev-parse --show-toplevel` and origin. Never the estate root. Linear is archive unless the user asks for it. 2. **Check for an existing issue.** `gh issue list -R <owner/repo> --search "<keywords>"`. If one tracks this slice, comment the spec there instead of opening a duplicate. 3. **Read the area.** Use the repo's own vocabulary and respect any ADR that covers it. 4. **Name the test seam.** Prefer an existing seam, as high as possible, ideally one. Say it back to the user in one line and continue unless they object. ## The issue body
Details
- Skill name
to-spec- Repository
- frankxai/claude-skills-library
- Path
absorbed/engineering/to-spec/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the To Spec skill do?
Turn what has already been discussed into a spec and file it as a GitHub issue on the product repo, without interviewing the user again. Use when the user says write this up as a spec, open an issue for this, or turn this into a ticket, after the decisions are made.
How do I install the To Spec skill?
Claude Code plugin: /plugin marketplace add frankxai/claude-skills-library. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is To Spec popular?
It lives in frankxai/claude-skills-library, which has 48 GitHub stars and 6 forks.
Related skills
Acos Meta
48frankxai/claude-skills-library
ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.
Acos Visual Gen
48frankxai/claude-skills-library
Generate research-grounded visuals using the InfoGenius pipeline. Use when creating infographics, diagrams, educational visuals, or any image that benefits from factual accuracy. Supports 8 visual styles (3D, technical, minimalist, photorealistic, futuristic, vintage, cartoon, standard) and 4 audience levels.
Agent Harness Construction
48frankxai/claude-skills-library
Shape an agent's tools, observations, and recovery without adding a second coordinator. Use when defining a tool, a skill, a hook, or a worktree lane.
Verification Loop
48frankxai/claude-skills-library
After a feature or refactor on this Windows estate, run six checks in order and write a PASS or FAIL note before a draft pull request. Use when work is about to be committed, pushed, or handed to another harness.
Starlight Chronicle
48frankxai/claude-skills-library
The reflective layer of the FrankX OS. A four-cadence practice — weekly Palace Review, monthly Survey, quarterly Constellation Census, annual Legacy Audit — that witnesses what's been built, blesses what is whole, and orients the next move from a sovereign vantage. Couples to /changelog as its factual underlayer. Use when invoking /palace, /chronicle, /bless, or when a Sunday reflection is requested.
Argumentation
45pjt222/agent-almanac
Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that propose technical changes, justifying design decisions in ADRs, constructing substantive code review feedback, or building a research argument or technical proposal.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.