agentsclimarketplace
Sign in

Write technical prd

Skill rvdsmaile/working-backwards/.agents/skills/write-technical-prd

Write a repository-aware technical PRD from an approved Working Backwards handoff and technical grill. Use after target-repository discovery and technical design approval, before implementation planning or issue slicing.From its SKILL.md

Install
npx -y skills add rvdsmaile/working-backwards --skill write-technical-prd

Assembled 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

0.9 KB, 155 tokens by cl100k_base, as published. Nobody here has run it

Write Technical PRD

Use ../../working-backwards/templates/technical-prd.md.

  1. Save the PRD in the target repository's existing spec location; otherwise use docs/specs/YYYY-MM-DD-<slug>.md.
  2. Link to source handoff artifacts and canonical target-repository documents. Do not duplicate commands, conventions, or architecture inventories.
  3. Commit to architecture, interfaces/data flow, test seams, risks/rollout, non-goals, and independently testable vertical slices. Do not include exact files, code snippets, estimates, or implementation tasks.
  4. Run ../../working-backwards/scripts/validate_technical_artifacts.py prd <prd-path> and hand off to review-technical-prd.

What ships with it: 1 file

157 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. 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.