To prd
Use when: turn current conversation and repo context into a PRD for an issue tracker.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill to-prdAssembled 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.
- 2 stars2 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.2 KB, 217 tokens by cl100k_base, as published. Nobody here has run it
Goal: produce a practical PRD from what is already known.
Use for:
- converting a feature discussion into a product requirements document
- capturing user stories, implementation decisions, and testable scope
- preparing work for issue tracking or agent handoff
Workflow:
- Read existing conversation, repo shape, glossary, ADRs, and relevant code.
- Do not interview from scratch; ask only for missing blockers.
- Identify modules to build or modify, preferring deep testable interfaces.
- Write user stories, implementation decisions, acceptance criteria, and risks.
- Include test expectations and open questions.
- Publish or prepare for the issue tracker only when target labels are known.
PRD sections:
- problem statement
- solution
- user stories
- implementation decisions
- acceptance criteria
- test plan
- risks and open questions
Rules:
- use the project vocabulary, not generic product prose
- keep scope traceable to user-visible outcomes
- separate known decisions from assumptions
- prefer small modules that can be tested in isolation
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.