prioritise-todos
Use this to rate and prioritise todos
- License 许可
- MIT
- 最近更新
- 2026-03-19
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- prioritise-todos
- description
- Use this to rate and prioritise todos
02 资源文件 13
- 参考文档checklist.md9.9 KB
- 其他customize.toml1.6 KB
- 资产文件documentation-requirements.csv7.9 KB
- 参考文档instructions.md8.0 KB
- 参考文档templates/deep-dive-template.md5.7 KB
- 参考文档templates/index-template.md4.4 KB
- 参考文档templates/project-overview-template.md1.9 KB
- 参考文档templates/project-scan-report-schema.json4.7 KB
- 参考文档templates/source-tree-template.md2.1 KB
- 参考文档workflows/deep-dive-instructions.md11.7 KB
- 参考文档workflows/deep-dive-workflow.md1.0 KB
- 参考文档workflows/full-scan-instructions.md42.2 KB
- 参考文档workflows/full-scan-workflow.md1.0 KB
03 SKILL.md 正文
Group similar todos. Similar todos means they are either of the same kind, or are related to another (ie you would ideally do them together) The goal is to create batches of work meant for a sub-agent.
So the more complex a group/todo is, the less priority it has. Simple and easy fixes that require as little structural changes as possible should be at the top.
Create a grouped and ranked list. keep descriptions brief. bullet points.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing good code
use this skill whenever you write code. it provides a process for creating good, composable apis.
write-review-elixir
Review Elixir code. ALWAYS use this skill before or after you added code written in elixir to ensure high code quality. Also use use this when asked to review existing elixir code.
whats-next
Answers what to do next, what to work on next, where we're at
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always