Turn incoming reports, external PRs and alerts into evidence-based decisions and agent-ready briefs. Use when: intake arrives. For accepted work, use Plan.
The English summary is being prepared. Showing the original description.
Audit CLI, API, MCP or SDK discovery, first use and error recovery. Use when: designing an agent-facing tool or investigating misuse, including one command.
The English summary is being prepared. Showing the original description.
Compare interface designs and find structural friction. Use when: a change spreads across modules or a boundary is unclear. For code changes, use Refactor.
The English summary is being prepared. Showing the original description.
Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: selected by name; one change goes to Plan.
The English summary is being prepared. Showing the original description.
Drive one accepted change through implementation and checks to done, with one fresh review only where a mistake is costly. Use when: selected by name.
The English summary is being prepared. Showing the original description.
Review code for security problems; scan for vulnerabilities, secrets, dependency and prompt risks. Use when: asked whether code is safe to ship, even one small handler.
The English summary is being prepared. Showing the original description.
Run a supplied task in headless AGY (Antigravity, Gemini) and collect its result. Use when: AGY, Antigravity or Gemini is requested by name; never a fallback.
The English summary is being prepared. Showing the original description.
Explain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: a postmortem or retro is selected by name.
The English summary is being prepared. Showing the original description.
Dispatch independent tasks to parallel workers or subagents without write collisions. Use when: running or planning agents in parallel, even two; check scopes before any launch.
The English summary is being prepared. Showing the original description.
Write source-checked docs, READMEs, change descriptions and handoff notes. Use when: documenting a change or leaving or resuming a session handoff.
The English summary is being prepared. Showing the original description.
Settle what domain terms mean per context, and which repository conventions or language standards (Go, Python) apply. Use when: names disagree or a rename is proposed.
The English summary is being prepared. Showing the original description.
Change or repair code, config or services without weakening tests; report what ran and what did not. Use when: implementing a change or fixing a defect.
The English summary is being prepared. Showing the original description.
Interview you one question at a time, each with a recommendation, to settle a big outcome before agents work alone. Use when: selected by name.
The English summary is being prepared. Showing the original description.
Find or curate supported lessons and agent rules. Use when: asked to remember, trace a corrected claim, audit instructions or write an agent rule.
The English summary is being prepared. Showing the original description.
Pick the next work in an epic or bead graph; closed is not proven. Use when: asked what is next or whether an epic is done.
The English summary is being prepared. Showing the original description.
Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Use when: managing multiple agents.
The English summary is being prepared. Showing the original description.
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.
The English summary is being prepared. Showing the original description.
Audit claims that work is done or shipped against the diff or repo. Use when: asked whether something really got done, even if it looks obvious.
The English summary is being prepared. Showing the original description.
Restructure or clean up code with no behavior change, proved by before-and-after checks. Use when: asked to clean up, extract, dedupe or simplify, even one function.
The English summary is being prepared. Showing the original description.
Answer one cited question about code, history, claims or patterns. Use when: asked how it works, why it changed, whether a claim holds or a pattern warrants a rule.
The English summary is being prepared. Showing the original description.
Tear down a competitor's repo or product into a feature inventory and adoption choices. Use when: comparing us to another tool or asking what to steal.
The English summary is being prepared. Showing the original description.
Create, repair, audit or consolidate agent skills (SKILL.md packages). Use when: writing or fixing a skill, its description or structure. Not for one-off lessons; use Memory.
The English summary is being prepared. Showing the original description.
Measure whether a skill helps by comparing runs with and without it. Use when: reading skill A/B results or deciding to keep, revise or remove one.
The English summary is being prepared. Showing the original description.
Write or assess tests that prove behavior and would fail without the fix. Use when: writing tests, TDD, or asked whether a green test is enough.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)