Generate a Claude Code–ready SPEC file from the current conversation.
npx skills add https://github.com/prestarius/jet-skills-stack --skill to-cc-spec
Please help me install this Agent Skill. Skill: to-cc-spec Source: https://github.com/prestarius/jet-skills-stack/tree/main/skills/to-cc-spec Command: npx skills add https://github.com/prestarius/jet-skills-stack --skill to-cc-spec
This Skill converts an ongoing design discussion (a design, idea, or half-finished plan) into a self-contained Claude Code–ready implementation spec / handoff document that a fresh agent can execute without the chat. Use whenever the user says "write a spec", "make this Claude Code–ready", "hand this off", "turn this into an implementation plan", or is about to delegate a build to another agent.
Turn the current chat into a Claude Code–ready SPEC file named <THING>_SPEC.md.
High-intent search queries and answers about installing and using this skill.
To turn a design chat into a Claude Code spec, generate a self-contained <THING>_SPEC.md document. This file enforces a strict 7-section layout including goals, architecture decisions, and implementation plans for fresh agent execution.
A Claude Code-ready specification document is a single <THING>_SPEC.md file that captures design context, architecture decisions, and a phased execution plan. It allows a fresh AI assistant to execute an implementation end-to-end without the original chat history.
An AI assistant handoff spec requires seven specific sections: Goal & non-goals, Context & assumptions, Architecture decisions, Repo / file layout, Phased implementation plan, Exact commands, and Open questions. This structure ensures reproducible agent execution.
You should generate an implementation plan from a conversation when you are about to delegate a build to another agent. Use it for design chats, ideas, or half-finished plans to produce a reproducible handoff document for fresh execution.
Yes, you can use this for AI assistant handoff in any design chat, idea discussion, or half-finished plan context. It processes the current conversation to output a single SPEC file formatted in SCREAMING_SNAKE case for easy agent delegation.
No, generating a Claude Code spec requires no external dependencies. The process extracts context directly from the current conversation to produce a self-contained specification document with exact commands and open questions.
wsbaserInterview users to extract feature requirements and generate a self-contained specification document.
afel6Generate task-level implementation plans with file paths, tests, and verification steps.
filipealvaUnify Claude Code and Codex agents, commands, skills, and hooks across sibling git repositories.
whtooGenerate standardized markdown templates for specification, design, and TDD plans.
