Handoff working backwards
Skill rvdsmaile/working-backwards/.agents/skills/handoff-working-backwards
Turn an approved Working Backwards initiative into a product brief and build plan. Use after announcement, FAQ, decisions, and critical critique findings are complete; do not use to write implementation code or estimates.From its SKILL.md
npx -y skills add rvdsmaile/working-backwards --skill handoff-working-backwardsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 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.
SKILL.md
1.0 KB, 169 tokens by cl100k_base, as published. Nobody here has run it
Handoff Working Backwards
Read ../../working-backwards/WORKFLOW.md and run the initiative validator first.
- Refuse to hand off if required artifacts are absent or critical findings remain unresolved; return to synthesis with the errors.
- Write
product-brief.mdwith the decision, customer/outcome, scope/non-goals, key decisions, and risks. - Write
build-plan.mdwith desired outcomes, milestones, risks/mitigations, and testable acceptance criteria. - Set
initiative.mdtohandoff. Do not add code, estimates, or granular engineering tickets unless separately requested. - When the user wants technical delivery, offer
start-technical-deliverywith the completed initiative and target implementation repository. Do not make technical delivery a handoff requirement.
What ships with it: 1 file
190 B alongside SKILL.md
agents/
- openai.yaml190 B