Spec to Repo
Translate product specs (PRDs, user stories) into a ship-ready repo plan: ticket decomposition, branch strategy, and PR sequencing. Use when breaking a PRD into tickets or designing the branch/PR sequence.
Install
/plugin marketplace add borghei/Claude-SkillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borghei/Claude-Skills --skill spec-to-repogit clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skills/product-team/spec-to-repo ~/.claude/skills/spec-to-repoPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Spec to Repo A delivery-focused skill that bridges product spec to repository work. Where PRD-writing skills focus on what to build, this skill focuses on **how to break it down for execution** — the ticket decomposition, branch strategy, PR sequencing, and acceptance criteria that make a spec actually ship. ## When to use this skill - Translating a **PRD or feature brief** into a sequence of tickets - Designing the **branch + PR sequence** for a multi-week feature - Auditing an existing **ticket decomposition** for risk (big tickets, hidden dependencies) - Defining **definition-of-done** that covers code, tests, docs, telemetry - Planning **incremental shipping** (feature flags, canaries, dark-launch) - Reviewing a **decomposition before sprint planning** to avoid mid-sprint surprises - Slicing a spec into **tracer-bullet tickets** with blocking links that people or coding agents can pick up in dependency order ## Inputs the advisor expects - The PRD or spec document - Target ship window (1 sprint? 1 month? 1 quarter?) - Engineering team size + composition (FE, BE, ML, mobile) - Risk profile (greenfield vs production-impacting) - Feature-flag and rollout posture ## Clarify First Before generating the repo plan, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Details
- Skill name
spec-to-repo- Repository
- borghei/Claude-Skills
- Path
product-team/spec-to-repo/SKILL.md- Repo updated
- 8 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Spec to Repo skill do?
Translate product specs (PRDs, user stories) into a ship-ready repo plan: ticket decomposition, branch strategy, and PR sequencing. Use when breaking a PRD into tickets or designing the branch/PR sequence.
How do I install the Spec to Repo skill?
Claude Code plugin: /plugin marketplace add borghei/Claude-Skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Spec to Repo popular?
It lives in borghei/Claude-Skills, which has 1,157 GitHub stars and 217 forks, and is included in 1 curated skill list.
Related skills
Cto Advisor
1.2kborghei/Claude-Skills
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, or making architecture decisions.
Customer Success Manager
1.2kborghei/Claude-Skills
Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
Financial Analyst
1.2kborghei/Claude-Skills
Performs financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction for strategic decision-making
Sprint Retrospective
1.2kborghei/Claude-Skills
Data-driven sprint retrospectives from git history — velocity, cycle/lead time, contributor insights, and churn hotspots. Use to run a retrospective, analyze team velocity or throughput, or generate a retro report from commit history.
Release Orchestrator
1.2kborghei/Claude-Skills
Gates a release from a live git checkout: preflight checks, secret scan, tag-based SemVer bump, changelog and GO/NO-GO score. Use when cutting a release from a repo (offline notes and plans from text: release-manager).
Git Branch Cleanup
422gotalab/skillport
Analyzes and safely cleans up local Git branches. Categorizes branches by merge status, staleness, and remote tracking. Provides interactive selection with safety guards. Use when the user wants to clean up branches, delete old branches, organize Git branches, or asks about which branches can be safely deleted.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.