2,358 件 ・ 関連度順
概要と使いどころ
Summarizes cybersecurity breach incidents into structured legal and compliance records. Trigger when synthesizing incident reports, forensics, logs, or notifications into a defensible chronology, scope-impact analysis, response ledger, or regulatory-risk assessment. Keywords: data breach, incident response, unauthorized access, ransomware, exfiltration, GDPR, CCPA, HIPAA.
日本語の概要は準備中です。原文の説明を表示しています。
Validates and summarizes the four required authorization forms in a personal injury matter (retainer, HIPAA release, insurance authorization, employment record release). Confirms signatures, dates, scope, and completeness to determine readiness for the investigation phase. Use when reviewing client onboarding packets, verifying authorization forms before discovery, or checking HIPAA and record-release compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts U.S. litigation attorney representation agreements for client onboarding, covering scope, fees, retainers, confidentiality, conflicts, duties, withdrawal, and dispute resolution. Use when converting consultations into enforceable engagement terms for civil litigation matters including personal injury. Trigger: engagement letter, litigation retainer, representation agreement, fee contract, conflict disclosure, attorney withdrawal, client acknowledgment.
日本語の概要は準備中です。原文の説明を表示しています。
Extracts technical API constraints from OpenAPI/Swagger specs and developer docs into a contract-ready API Access & Constraints Schedule with source traceability, risk flags, and change-control language. Use when drafting legal exhibits or schedules covering API access scope, rate limits, authentication, data fields, or deprecation terms for MSAs, SOWs, or order forms.
日本語の概要は準備中です。原文の説明を表示しています。
Manages Rule 30(b)(6) corporate representative deposition workflows — drafting notice topics with reasonable particularity, building examination outlines, defending designees, handling objections, and preserving binding admissions for summary judgment or trial. Use when drafting or responding to 30(b)(6) notices, selecting and preparing designees, building topic-by-topic outlines, or triaging scope and privilege disputes. Trigger keywords: 30(b)(6), corporate representative deposition, topic list, designee, notice analysis, deposition objections, corporate admissions.
日本語の概要は準備中です。原文の説明を表示しています。
Structured multi-file implementation plans before build; scope-aware, enforces Gate 1. NOT for ticket sizing (mk:planning-engine) or plan CEO-review (mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ticket complexity and dependencies against the codebase before sprint planning. NOT for writing plans (mk:plan-creator); NOT for scope review (mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Single-task pipeline: plan → test → build → review (ship separately). Use for a feature or scoped fix. NOT for green-field builds (mk:autobuild) or auto-orchestration (mk:workflow-orchestrator).
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously improve one measurable metric via bounded, git-tracked iterations: one scoped change, verify, keep or revert. NOT for cleanup (mk:cook), known-cause bugs (mk:fix), or shipping (mk:ship).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a plan directory (plan.md + phase-*.md) needs a visual review. By DEFAULT this drives the STRUCTURED visual-plan artifact (visual-plan/plan.json) via the mewkit visual-plan CLI — generate if absent, validate, open the local studio (view/edit), and export plan.html from the approved artifact. Pass --static for the legacy prompt-only single-file plan.html template render. Triggers on "render this plan", "visualize the plan", "open the plan studio", "make a shareable plan page", "plan.html". This is the canonical owner of plan-as-visual-review. NOT for plan critique or scope review (see mk:plan-ceo-review / mk:validate-plan), NOT for generic code/diagram/diff visuals (see mk:preview), NOT for live media generation (see mk:multimodal).
日本語の概要は準備中です。原文の説明を表示しています。
Session-scoped guardrails warning before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, etc; user can override. NOT for scoping edits to a directory (mk:freeze).
日本語の概要は準備中です。原文の説明を表示しています。
Runs autonomous multi-hour green-field builds: planner, contract, generator/evaluator loop, scaffolding density per model tier. NOT for scoped tasks (mk:cook); NOT for scaffolding only (mk:bootstrap).
日本語の概要は準備中です。原文の説明を表示しています。
Ship workflow with explicit scopes: prepare stages and commits locally; release pushes and creates a PR; publish manages issues and versioning. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying. Supports official (→ main) and beta (→ dev/develop) ship modes with auto-detection.
日本語の概要は準備中です。原文の説明を表示しています。
Use when autonomously improving a measurable scalar metric through bounded, git-tracked iterations: modify one scoped change, verify, keep or revert. Triggers on /mk:loop, 'optimize coverage/bundle size/lint count', 'iterate until the metric improves'. NOT for subjective cleanup (see mk:cook), known-root-cause bugs (see mk:fix), behavioral grading (see mk:evaluate), or shipping (see mk:ship).
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Multi-pass structural code review with adversarial analysis, scope-aware dispatch, adversarial persona passes, and forced-finding protocol. Supports input modes: branch diff (default), PR number (#123), commit hash, pending changes (--pending). Use when asked to "review this PR", "code review", "pre-landing review", "check my diff", or "review #123". Proactively suggest when the user is about to merge or land code changes. NOT for behavioral verification against a running build (see mk:evaluate); NOT for post-implementation simplification (see mk:simplify).
日本語の概要は準備中です。原文の説明を表示しています。
Session-scoped safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Active for the current session only. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode". NOT for scoping edits to a specific directory (see mk:freeze).
日本語の概要は準備中です。原文の説明を表示しています。
Use when running an autonomous multi-hour build of a green-field product — orchestrates planner → contract → generator ⇄ evaluator loop with adaptive scaffolding density per model tier. Triggers on /mk:autobuild, "build me a kanban app", "build a retro game maker", "autonomous build", or any green-field product spec. NOT for scoped single-task work (see mk:cook); NOT for initial project scaffolding only (see mk:bootstrap).
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates single-task implementation pipeline: plan → test → build → review. Shipping is an explicit follow-up. Use for feature work, plan execution, or fixes scoped to a single task. NOT for green-field product builds (see mk:autobuild); NOT for auto-invoked workflow orchestration (see mk:workflow-orchestrator).
日本語の概要は準備中です。原文の説明を表示しています。
YC-style product strategy assessment with forced questions and CEO scope modes — adapted from gstack /office-hours pattern
日本語の概要は準備中です。原文の説明を表示しています。
Inspect scoped Autodesk data, compare versioned BOMs, and prepare ownership-aware drafts or approved custom-property changes. Not for implicit PLM release, membership changes or CAD geometry editing.
日本語の概要は準備中です。原文の説明を表示しています。
Configure and diagnose Fusion interoperability, transport selection, scoped profiles and qualification. Use for setup or connection problems, not design edits.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare, submit and reconcile reviewed Fusion Automation jobs with exact sources, scoped authorization and explicit budgets. Not for arbitrary model-generated cloud scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify the brief BEFORE any design work to avoid building the wrong thing. Interrogates goal, user, constraints, success criteria, and scope, then writes a short context doc the other design skills consume. Use when the user says "let's design X", "build a UI for Y", "get context", "clarify the brief", or kicks off any product-design task without a clear spec. First stage of the Product Design set — highest leverage for reducing rework.
日本語の概要は準備中です。原文の説明を表示しています。