Custom fork of mattpocock/skills — same skills, but to-prd and to-issues write directly to local markdown docs under ~/semianalysis/context-files/ instead of opening GitHub issues.
npx skills@latest add rromero09/Skills -g -a claude-code -yRepo is private — requires
gh auth login(or SSH key) on the target machine.
To install only the modified skills:
npx skills@latest add rromero09/Skills --skill to-prd --skill to-issues -g -a claude-code -y| Skill | Upstream behavior | This fork |
|---|---|---|
to-prd |
Submit PRD as GitHub issue | Write to ~/semianalysis/context-files/to-prd/<MMDD>/<slug>.md |
to-issues |
Create one GitHub issue per vertical slice | Write to ~/semianalysis/context-files/to-issues/<MMDD>/<NN>-<slug>.md |
grill-with-docs |
Write CONTEXT.md + ADRs into the repo | Glossary → ~/semianalysis/context-files/grill-with-docs/CONTEXT.md (persistent); ADRs → ~/semianalysis/context-files/grill-with-docs/<MMDD>/adr/<NN>-<slug>.md |
All other skills inherit upstream behavior unchanged.
git remote add upstream https://github.com/mattpocock/skills.git
git fetch upstream
git merge upstream/main
# resolve conflicts in skills/engineering/to-prd + skills/engineering/to-issues
git push origin mainOriginal README from upstream preserved below for reference.
My agent skills that I use every day to do real engineering - not vibe coding.
Developing real applications is hard. Approaches like GSD, BMAD, and Spec-Kit try to help by owning the process. But while doing so, they take away your control and make bugs in the process hard to resolve.
These skills are designed to be small, easy to adapt, and composable. They work with any model. They're based on decades of engineering experience. Hack around with them. Make them your own. Enjoy.
See upstream repo for full docs, philosophy, and full skill catalog.