1,024 件 ・ 関連度順
概要と使いどころ
Workflow navigation assistant. Scans project state (plans, reviews, tests, git) and recommends the next step in the 7-phase pipeline. Use when asked "what should I do next?", "where am I?", "help", or at session start. NOT for domain complexity routing (see mk:scale-routing); NOT for skill discovery (descriptions handle that automatically).
日本語の概要は準備中です。原文の説明を表示しています。
Use when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).
日本語の概要は準備中です。原文の説明を表示しています。
Generate release-unit development plans from professor-triage completed (verify-done) issues, grouping by priority and size
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined goal-to-execution workflow for any user task. Parses objective, asks only for materially missing requirements via ambiguity-gate, inspects repo via idea, plans via sdd-dev or deep-plan, executes safely under project conventions, verifies completion per R020, and reports changed files with evidence. Use when user invokes /goal <task>.
日本語の概要は準備中です。原文の説明を表示しています。
Research-validated planning — research → plan → verify cycle for high-confidence implementation plans
日本語の概要は準備中です。原文の説明を表示しています。
Prepare, execute and verify authorized Fusion CAD changes using resolved entities, explicit units and state-bound plans. Use for reviewed parameter, sketch, feature, assembly or configuration operations.
日本語の概要は準備中です。原文の説明を表示しています。
Handle ethical requirements, IRB approval, trial registration, and pre-analysis plans for RCTs. Use when user mentions: research ethics, IRB, informed consent, trial registration, pre-analysis plan, PAP, data security, vulnerable populations, research transparency.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial dialectic tool inspired by GAN. Alternates between Generator (creative advocate) and Discriminator (adversarial critic). Supports forced role selection (g/d), intensity modes (hard/soft), and multi-language output. Use for stress-testing ideas, business plans, code, and spec designs.
日本語の概要は準備中です。原文の説明を表示しています。
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
日本語の概要は準備中です。原文の説明を表示しています。
Safe database migration manager for zero-downtime DDL changes and rollback plans. Activate on: database migration, schema change, DDL, rollback plan, zero-downtime migration, Prisma migrate, Drizzle kit, Flyway, column rename, table alter. NOT for: query optimization (use database-optimizer), ORM modeling (use data-pipeline-engineer), backup/restore (use devops-automator).
日本語の概要は準備中です。原文の説明を表示しています。
Plan database migrations before executing them: risk assessment, dependency mapping, multi-service sequencing, rollback budgets, and stakeholder communication plans. Use when deciding HOW to migrate, not when writing the actual DDL. NOT for: writing migration SQL (use database-migration-manager), data ETL pipelines (use data-migration-specialist), query optimization, or ORM configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Parses complex problems into DAG (Directed Acyclic Graph) execution structures. Decomposes tasks into nodes with dependencies, identifies parallelization opportunities, and creates optimal execution plans. Activate on 'build dag', 'create workflow graph', 'decompose task', 'execution graph', 'task graph'. NOT for simple linear tasks or when an existing DAG structure is provided.
日本語の概要は準備中です。原文の説明を表示しています。
Use for bounded reasoning, partial planning, commitment policy, deliberation cost, and reconsideration-threshold design instead of assuming free deliberation. NOT for exhaustive planning, static optimization, or domains where reconsideration cost is irrelevant.
日本語の概要は準備中です。原文の説明を表示しています。
Design AgentSpeak(L)-style BDI agents with context-guarded plans, selection functions, and intention stacks. Use for interruptible autonomy, agent policy, and multi-agent orchestration in dynamic environments. NOT for simple rule engines, static planners, or centralized workflows.
日本語の概要は準備中です。原文の説明を表示しています。
A workflow skill that lets Codex keep coding for 60 hours on medium and large projects: Claude Code CLI plans through an interactive requirements questionnaire, PRD, specs, and roadmap; Codex implements verified vertical slices, with resumable Long-Run Execution for lengthy work; Trellis maintains project memory. Use when the user mentions 大项目工作流, Codex 连续开发 60 小时, Codex 长任务, long-running or resumable Codex implementation, large/medium project, new SaaS, multi-module system, requirements questionnaire, Claude Code CLI planning, Codex implementation handoff, Trellis bootstrap, non-system-drive project, or vertical slice. Skip for: single-file edits, casual Q&A, copy polish, throwaway prototypes, or tasks the user explicitly wants done fast without process.
日本語の概要は準備中です。原文の説明を表示しています。
Act as a senior Amazon account growth operator that combines Amazon performance-drop analytics, Amazon growth-opportunity analytics, Amazon Ads data, retail readiness, BSR/rank signals, margin, inventory, and campaign/search-term evidence into a prioritized profitable growth action plan. Use when Codex needs to decide what to protect, fix, scale, reduce, pause, harvest, launch, or monitor for an Amazon brand, agency, marketplace, ASIN set, or account; when building daily, weekly, or monthly Amazon account operating plans; when reallocating ad budget; when deciding which ASINs are safe or risky to push; or when turning performance-drop and growth-opportunity findings into approval-gated actions with success/failure criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Use when executing implementation plans with independent tasks in the current session
日本語の概要は準備中です。原文の説明を表示しています。
Plan mode: write markdown plan to .hermes/plans/, no exec.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a written implementation plan to execute in a separate session with review checkpoints
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
日本語の概要は準備中です。原文の説明を表示しています。
Execute plans via delegate_task subagents (2-stage review).
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a spec or requirements for a multi-step task, before touching code
日本語の概要は準備中です。原文の説明を表示しています。
Validates a plan before committing to it - checks whether the ranking survives the assumptions, finds the most likely way it fails, and makes the trade-offs explicit via a Pareto frontier instead of an invented single score. Use before a launch, price change, migration, infrastructure change or major commitment, when running a premortem, when two objectives conflict, or when a decision depends on an assumption nobody has tested.
日本語の概要は準備中です。原文の説明を表示しています。
Decides how far ahead to plan, what to discount future payoffs by, and which backlog items can be dropped without analysis - using receding-horizon planning, an explicit discount factor, and branch-and-bound pruning against the incumbent. Use when building a roadmap, prioritising a backlog, arguing about short-term versus long-term, setting quarterly or annual plans, or when planning has become an end in itself.
日本語の概要は準備中です。原文の説明を表示しています。