write-TRD
Skill2 starsChanged 3 months agoNo licenceView on GitHub
当用户希望: - 根据 PRD 设计技术方案 - 评估需求对现有系统影响 - 明确改造范围、接口、数据与发布策略 - 输出可直接用于评审的 TRD 至少提取: - 业务背景与目标 - 功能与业务规则 - 核心流程与角色 - 边界/异常场景 - 数据与非功能要求(性能、兼容性、安全性) 若 PRD 信息冲突或缺失:明确列出问题清单,不自行补完。 围绕需求做定向定位,不做无目的全量遍历: - 模块与目录结构 -…
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- code-reviewSkill
- diagnosing-bugsSkill
- frontend-designSkill
- improve-codebase-architectureSkill
- karpathy-guidelines-installerSkill
- Mock-Interview-QuestionList-GenerationSkill
- Mock-InterviewSkill
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.

