Productivity

Use when the user invokes $amap-maps-mcp, mentions Amap Maps, or asks for supported Amap Maps workflows.

Record DION meetings on Windows, transcribe recordings locally, and create Russian Markdown minutes. Use for meeting recording, stopping recording and processing existing recordings.

Examines raw stakeholder input (transcripts, briefs, emails, feature ideas) into epics and candidate user stories published to the tracker; when scope exceeds a single session, opens a decision map and resolves one decision per session.

Configures a workspace for refinement workflows: operating mode (with or without code), local markdown tracker, publishing conventions, and agent instructions block in AGENTS.md or CLAUDE.md. Run once per workspace.

Use when a Claude2GrokBot wake request starts you (webhook body type "claude2grokbot.wake") or the user says "check Claude2GrokBot": claim the tasks Claude queued, do them, and upload the results.

Have Grok Bot do work on its cloud computer (it operates the desktop like a person, by screen, mouse and keyboard) while Claude decides each next step, starting Grok Bot if it isn't running. Use when the user wants Grok Bot to do something, asks about a task sent to Grok Bot, or asks to set up, check or repair Claude2GrokBot.

Run the full pre-PR checklist (make check, secret scan, docs, diff review) before opening or updating a pull request. Use before creating a PR or when asked if work is ready.

Use when an open-ended task should be raised from task-level to outcome-level, when results must be verified by something other than the model that produced them, or when a crew of tool-bearing subagents is needed. Compiles the request into <invariant + falsifiable verifier + environment manifest>, runs an outside-judge ladder with per-claim verdicts, and makes subagents do the work rather than role-play it. Skip for tight specs with fixed acceptance criteria, trivial tasks, or crunch situations - adding harder goals there only adds risk.

把杂乱的会议记录、语音转录文字整理成结构化会议纪要。当用户发来会议记录、聊天记录或转录文本并说"整理成纪要"时使用。

Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.

>- Use this when choosing a tool, library, framework, CLI, MCP server, or agent skill for a task: first look in the user's own GitHub stars and in official vendor skill catalogs, then recommend well-known, actively maintained options with reasons.

Analyzes Android apps to identify key user workflows for AppFunctions such as creating a note, playing media, or sending an automated or AI agent triggered message, voice commands, or system shortcuts, without needing to open the app UI. Generates Kotlin code to expose these workflows to the Android system, allowing agents to discover and execute them on-device. Also refines KDoc documentation to ensure AI agents correctly understand and use the provided functionality.

End-to-end orchestrated workflow that runs a task the way Fable ran sessions - parallel evidence subagents, one committed plan, surgical execution with an intent gate, adversarial verification agents, honest outcome-first report. Use for non-trivial multi-step tasks when the user says "/fable-loop", "run the fable loop", or "do this the way Fable would". For the rules alone without orchestration, use fable-method; for large multi-phase projects, prefer the GSD workflow and use this inside phases.

Commit workflow that runs doc-gen first, stages only needed files (asking for confirmation on uncertain ones), suggests a message from the actual diff, commits, shows a summary, and asks about pushing.

Scan a Go project structure and generate/update README.md with package overviews, dependencies, and usage notes.

Update project documentation (CLAUDE.md + .llmdocs/). Use after significant work to keep docs in sync.

Builds the project and pushes a release to the staging host.

Builds the project and pushes a release to the staging host.

Create diagrams as self-contained HTML files with inline SVG that make visual arguments, then screenshot and lint them in a render-validate loop until clean. Use when the user wants to visualize a workflow, architecture, system, process, or concept as a diagram they can open in a browser, embed, or share.

Run the Gate 1 deterministic static check on task bundles before development starts and follow the Gate 2 review checklist. Use when task contracts exist under tasks/ and you need to verify blast radius, diff budget, declared-file topology, traceability anchors, spec anchor coverage, inherited ADRs, machine-checkable acceptance criteria, and DAG acyclicity. Do not use for code execution, CI pipeline construction, AST/complexity checks, or test audits (owned by quality-engineering).

Run a bounded brownfield change (bugfix, small feature, behavior tweak) against an existing spec or codebase: proposal -> one task bundle -> dev/QA -> converge -> archive. Use when an existing spec or codebase needs an incremental change (bugfix, small feature, behavior tweak) and a full PRD is overkill. Do not use for greenfield requirements (use prd-generator), architecture decisions (use spec-generator), or pure task slicing (use task-decomposition).

Implement one planned task bundle as the Dev role: read the contract, change only touch_files, run the machine-checkable DoD, fill 02-dev-workspace.md and hand off to QA. Use when a task contract exists and you are assigned implementation. Do not use for planning, task slicing, architecture, or QA verification.

Fold confirmed implementation deviations back into the technical spec after a task reaches QA_PASSED, archive the task bundle and close the change proposal. Use when a task bundle records a checked QA_PASSED verdict and its 02-dev-workspace.md deviation log is ready to be written back. Do not use while implementation or QA is still running, and do not use to invent spec content.

Implement, fix, or refactor project code with a cooperative token-budgeted workflow that stops before optional builds, tests, runs, linting, formatting, generation, dependency work, or documentation. Use for ordinary software changes in any language or framework. Do not use when the user's primary request is to perform one of those validation or maintenance actions.