graders
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-10-31
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- tool
- Skill
- type
- tool_used
- input_match
- "skill"\s*:\s*"(?:[\w-]+:)?intake"
03 SKILL.md 正文
该 Skill 的授权仅允许展示来源链接,正文请前往 GitHub 查看。
查看 SKILL.md ↗04 同仓库更多 Skills
intake
Use at the very start of the workflow, when a raw idea, voice transcript (German or English), or backlog line needs capturing before superpowers:brainstorming. Use before design begins — not after an approved story or spec exists, and not to design the solution.
harden-finding
Use when a review finding (Codex Gate A/B, CodeRabbit, or manual review) has been surfaced and you want it to never silently return — turning a one-off fix into a lint rule, type constraint, test, or documented convention. Use also when a finding you've seen before recurs.
ticket
Use when a bug, regression, robustness fix or wording defect arrives that stays inside an approved commitment — it becomes a ticket file that records the evidence, the expected behaviour's source and the commitment, and serves as the brief a coding agent fixes it from. Also `list` for the open tickets and `T-<n> <state>` for a state change. A change that alters an approved commitment is handed to intake instead.
sparring
Use when you want an advisory second opinion in a chat you opened for that purpose — investigating a question read-only, checking an agent's report against the current files, weighing options before committing to one, or drafting a bounded prompt for a coding agent to run elsewhere. Invoke it by name. It advises; it does not implement, commit, or run review gates.
intake
Use at the very start of the workflow, when a raw idea, voice transcript (German or English), or backlog line needs capturing before superpowers:brainstorming — or later, when an approved story or spec must change after a decision to change it, to write a change record that accounts for every earlier condition. Not for designing the solution, nor for a bug or defect inside an approved commitment (that is `ticket`).
harden-finding
Use when a review finding (Codex Gate A/B, a PR bot, or manual review) has been surfaced and you want it to never silently return — turning a one-off fix into a lint rule, type constraint, test, or documented convention. Use also when a finding you've seen before recurs.