dev-reading
Skill1 starsChanged 19 days agoNo licenceView on GitHub
This skill should be used when a non-developer planner/PM receives developer materials — API specs, DB schema/ERD, technical docs — and wants them explained in plain language with a planner's lens. 개발자에게 받은 API 명세·DB 스키마/ERD·기술문서를 비개발 기획자가 이해하도록 평이하게 풀어주고, 확인·질문 포인트와 기획·일정 영향까지 짚어준다. 트리거 예시 "이 API 명세 풀어줘", "ERD 해석해줘", "이 DB 구조 뭔 뜻이야", "개발자한테 받은 문서인데 이해가 안 가", "기획자 입장에서 이 자료 어떻게 봐야 해", "이 기술문서 정리해줘", "explain this API spec", "decode this schema". 소스코드 해석은 범위 밖. Use this whenever the user shares API/DB/technical material and wants to understand it — even if they don't explicitly say "해설".
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- flowchart-defenseSkill
- ia-builderSkill
- meeting-agendaSkill
- meeting-minutesSkill
- qa-masterSkill
- requirements-generatorSkill
- wbs-generatorSkill
- weekly-reportSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

