Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
The English summary is being prepared. Showing the original description.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
The English summary is being prepared. Showing the original description.
Compact the current conversation into a handoff document for another agent to pick up.
The English summary is being prepared. Showing the original description.
Teach the user a new skill or concept, within this workspace.
The English summary is being prepared. Showing the original description.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
The English summary is being prepared. Showing the original description.
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
The English summary is being prepared. Showing the original description.
Integrate Egma into a repository containing voice agent code. Use when the developer asks to integrate voice agent testing, monitoring or both
The English summary is being prepared. Showing the original description.
Write or edit tests for a voice agent that can run on the Egma platform.
The English summary is being prepared. Showing the original description.
Ask which skill or flow fits your situation. A router over the skills in this repo.
The English summary is being prepared. Showing the original description.
Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'. Use /bro to get a plain-language version of the last answer.
The English summary is being prepared. Showing the original description.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
The English summary is being prepared. Showing the original description.
Drive one ticketed effort through parallel implementation, independent review, serial integration, and one open pull request.
The English summary is being prepared. Showing the original description.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
The English summary is being prepared. Showing the original description.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
The English summary is being prepared. Showing the original description.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
The English summary is being prepared. Showing the original description.
Implement a piece of work based on a spec or set of tickets.
The English summary is being prepared. Showing the original description.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
The English summary is being prepared. Showing the original description.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
The English summary is being prepared. Showing the original description.
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
The English summary is being prepared. Showing the original description.
Use when you need to resolve an in-progress git merge/rebase conflict.
The English summary is being prepared. Showing the original description.
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
The English summary is being prepared. Showing the original description.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
The English summary is being prepared. Showing the original description.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
The English summary is being prepared. Showing the original description.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)