菜单
Ask which Mekann skill or workflow fits the current situation. Routes only to skills and runtime flows available in this package.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Create, edit, and improve articles and technical documents by planning structure, clarifying dependencies, preserving technical accuracy, and tightening prose. Use when the user wants to draft, revise, or improve an article, guide, reference, design document, proposal, or other technical writing.
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/PRD 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".
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.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
| name | ask-matt |
| description | Ask which Mekann skill or workflow fits the current situation. Routes only to skills and runtime flows available in this package. |
| disable-model-invocation | true |
Route the user's request to the smallest suitable Mekann workflow. Do not invent upstream commands that Mekann does not expose.
grill-with-docs when an idea or design needs clarification and should update CONTEXT.md or ADRs.prototype when a runnable experiment is needed to answer one design question.to-prd and then to-issues.implement for an agreed piece of work; it should use tdd where practical.code-review to compare a completed diff against repository standards and its originating specification.diagnosetriageimprove-codebase-architecturedomain-modelingcodebase-designresearchwriting-assistantresolving-merge-conflictscli-for-agentsLoad a visible skill by reading its listed SKILL.md. A hidden skill remains explicitly loadable as /skill:<name>. Use Mekann runtime flows such as /issue, /pr-check, or /review-quality when repository policy routes the task through them.
Before issue-management flows, use setup-matt-pocock-skills if the repository does not yet define its issue tracker, triage vocabulary, or domain-doc layout.