Agent skill · product strategy · borghei
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.
Why this skill is useful
Adds 3 executable scripts for ticket decomposition, branch validation, and naming conventions that streamline the development process.
What it needs
Requires python3 installed locally. About 5k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
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 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, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] The PRD or spec — the user-facing capabilities to decompose (drives the epic→ticket tree) [ ] Target ship window — one sprint, month, or quarter (drives ticket sizing and PR sequencing) [ ] Team composition — FE, BE, ML, mobile (decides parallel paths and vertical-slice tickets) [ ] Feature-flag and rollout posture — flagged/dark-launch vs direct ship (drives PR sequencing and definition-of-done) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Workflows Workflow 1 — Decompose a PRD into tickets 1. Pull the PRD; identify the user-facing capabilities. 2. Run prdtoticketsdecomposer.py with the user stories + technical notes to surface a candidate ticket tree (epic → tickets → subtasks) with size estimates and dependencies. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/spec-to-repo