decision-rules
Skill0 starsChanged 3 months agoNo licenceView on GitHub
業務理解・業務設計から要件定義に落とし込む過程の意思決定を、パレートの法則(80/20で急所を絞る)とシンプルルール(3〜5本の一行ルールで機械的に判断する)で行い、決定記録として残すスキル。「スコープが決まらない」「何を作って何を捨てるか」「優先順位をつけたい」「要件が膨らんでいる」「業務のどこから手をつけるか」「MVP・初回リリースの範囲」「機能の取捨選択」「フェーズ分け」「この案件どう進めるべき?」といった相談、および業務フロー・課題一覧・ヒアリング結果・要望リストを前にして判断が必要な場面では必ずこのスキルを使うこと。要件定義書・PRD・ステアリングの requirements.md を書き始める前段としても使う。既に決まった要件を清書するだけの作業には使わない。
In this repository14 other files it gives its agents.
- add-featureSkill
- atlas-pptx-designSkill
- atlas-registerSkill
- business-understandingSkill
- daily-reportSkill
- dev-docsSkill
- drawio-shotsSkill
- gas-cloneSkill
- gas-devSkill
- gas-pushSkill
- hearing-sheetSkill
- natural-japaneseSkill
- obsidian-logSkill
- 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.

