agentsclimarketplace

Break prd into issues

Skill rvdsmaile/working-backwards/.agents/skills/break-prd-into-issues

Composable Working Backwards skills for turning product ideas into customer narratives and build-ready plans.

Install
npx -y skills add rvdsmaile/working-backwards --skill break-prd-into-issues

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create a reviewable, dependency-ordered issue backlog from an approved technical PRD. Use when a team needs independently grabbable vertical slices before publishing to any issue tracker.

SKILL.md

0.9 KB, as published. Nobody here has run it

Break PRD into Issues

Use ../../working-backwards/templates/issue-breakdown.md.

  1. Write the breakdown beside the PRD using the same slug plus -issue-breakdown.md.
  2. Make every issue a thin, complete vertical slice with a verifiable behavior. Do not create horizontal tickets for all schemas, APIs, or UI.
  3. Give each issue an AFK or HITL type, dependency, tracker-draft status, end-to-end scope, acceptance criteria, and verification evidence.
  4. Order issues so blockers appear first. Present the complete backlog for user approval; do not publish it.
  5. Run ../../working-backwards/scripts/validate_technical_artifacts.py issues <breakdown-path> and hand off to publish-issue-backlog only after explicit approval.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.