PRD to Execution Issues

A product spec can explain what to build without giving your team clear tasks to start. Turn it into scoped engineering issues with testable outcomes, dependencies, and a practical delivery order.

What it does

• Creates assignable issues: Gives each task enough context for an engineer or coding agent to begin.
• Defines completion: Adds acceptance criteria and suggested tests or checks.
• Plans delivery order: Shows which tasks depend on others and which can run in parallel.
• Flags uncertainty: Highlights missing decisions, implementation risks, and scope boundaries.

How it works

1. Share your product requirements document, feature plan, or implementation brief.
2. Include known constraints, exclusions, and relevant implementation details.
3. Receive a structured issue plan with dependencies, complexity estimates, and verification steps.
4. Resolve open questions before assigning affected work.

Works with

Produces JSON issue plans suitable for Codex, GitHub Issues, Linear, and other engineering task systems. You can also request another output format. Direct issue creation is not included.

Why use this skill

Spend less time rewriting requirements into tickets and explaining what counts as finished. Tasks focus on testable behavior rather than disconnected database, API, and interface chores. Explicit dependencies help avoid assigning work before its prerequisites are ready.

Use cases

• Prepare a feature brief for a coding agent.
• Divide a product spec into assignable engineering work.
• Identify work that can proceed in parallel.
• Expose unresolved decisions before implementation starts.

Known limitations

This skill plans work, not implementation. Missing requirements can leave blocking questions that need your team’s answers.