Publish issue backlog
Skill rvdsmaile/working-backwards/.agents/skills/publish-issue-backlog
Composable Working Backwards skills for turning product ideas into customer narratives and build-ready plans.
npx -y skills add rvdsmaile/working-backwards --skill publish-issue-backlogAssembled 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
Publish an explicitly approved Working Backwards issue backlog to a user-selected or repository-documented tracker. Use only after a technical PRD and issue breakdown are approved; supports GitHub, Linear, Jira, local Markdown, or another instructed workflow.
SKILL.md
0.9 KB, as published. Nobody here has run it
Publish Issue Backlog
- Confirm the target tracker, project/repository, labels/statuses, and the approved breakdown. If the tracker workflow is not documented or supplied, stop and ask; never guess.
- Publish blockers first. Include the PRD link, end-to-end scope, acceptance criteria, verification, and actual blocker IDs in each item.
- Use only tracker fields that the user specified or the target repository documents. Do not modify or close existing items.
- Replace each
Tracker: Draftmarker in the breakdown with the real identifier and URL, then set its publication status to published.