wangjq4214 · Agent Skills
出典を確認した実質的な文書を持つ Skill が 7 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
grimoire-check
Use when asked whether an implementation satisfies user intent, the original request, a spec, ticket, or acceptance criteria, including missing requirements despite passing tests or work beyond the requested scope. For code defects, security, compatibility, or performance risks, use grimoire-review.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 11月12日
grimoire-debug
Use when a program crashes, produces incorrect results, fails unexpectedly or intermittently, or becomes unexpectedly slow, or when a failing test has an unexplained cause. For an already-understood fix with no diagnosis needed, use grimoire-implement.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 11月12日
grimoire-plan
Use when asked to plan how to implement a change or revise an existing implementation approach, including steps, affected code, dependencies, and verification. For required behavior and acceptance criteria, use grimoire-spec.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 11月12日
grimoire-refine
Use when explicitly invoked to work through requirements and choose a handoff, spec, or ticket set. Not for implementation planning or code execution.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 11月12日
grimoire-retro
Use when explicitly invoked to investigate a specific or recurring agent mistake or repeated user corrections, retrospect on task execution, analyze historical sessions for recurring problems, or compare agent behavior before and after workflow changes. Not for ordinary product debugging or code review.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 11月12日
grimoire-simplify
Use when asked to simplify code, remove redundant state or branches, eliminate duplication or dead paths, or reduce valueless indirection without changing behavior. For responsibility or dependency redesign, use grimoire-improve.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 11月12日
grimoire-spec
Use when asked to write or revise a requirements spec defining outcomes, constraints, integration contracts, and observable acceptance criteria from a conversation or repository context. Not for implementation steps or ticket decomposition.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 11月12日