「complex」の検索結果

Set up a parallel agent team for COMPLEX tasks: creates worktree structure, an ownership map, and an initialized task queue. Use when a task is decomposed into parallel subtasks.

日本語の概要は準備中です。原文の説明を表示しています。

Structured step-by-step reasoning before acting, to avoid guessing. For complex debugging, multi-step analysis, hypothesis checks. NOT for being stuck on approach (mk:problem-solving).

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

Read-only full Jira ticket analysis incl. media + linked issues via jira-analyst agent; produces comment-ready findings. NOT complexity scoring (mk:jira-evaluator) or estimation (mk:jira-estimator).

日本語の概要は準備中です。原文の説明を表示しています。

Workflow navigator: scans project state (plans, reviews, tests, git) and recommends the next pipeline step. Use for 'what next?' or 'where am I?'. NOT for complexity routing (mk:scale-routing).

日本語の概要は準備中です。原文の説明を表示しています。

Heuristic read-only story-point estimation for one Jira ticket via jira-estimator agent. NOT complexity analysis (mk:jira-evaluator) or full RCA (mk:jira-analyst).

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate Jira ticket complexity and inconsistencies via jira-evaluator agent, read-only. NOT estimation (mk:jira-estimator) or full RCA (mk:jira-analyst).

日本語の概要は準備中です。原文の説明を表示しています。

Set up parallel agent team for COMPLEX tasks. Creates worktree structure, generates ownership map, and initializes task queue. Use when orchestrator decomposes a task into parallel subtasks, or when asked to "set up team", "parallel setup", or "configure worktrees".

日本語の概要は準備中です。原文の説明を表示しています。

Detects the right agent and complexity tier at Phase 0 orient; runs first in every workflow. NOT for runtime agent routing inside a single skill.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a problem requires structured step-by-step reasoning before acting. Prevents jumping to conclusions or guessing root causes without evidence. Triggers on complex debugging, multi-step analysis, hypothesis verification, or when mk:fix invokes diagnosis phase. NOT for being stuck on approach (too many implementations, forced assumptions, innovation block) — use mk:problem-solving instead.

日本語の概要は準備中です。原文の説明を表示しています。

Use when stuck on approach (not debugging). Strategic unsticking via 7 non-default techniques: simplification cascades, collision-zone thinking, meta-pattern recognition, inversion, scale game, first principles, via negativa. Triggers on complexity spiraling, innovation block, recurring patterns across domains, forced-assumption solutions, scale uncertainty, told-it's-impossible, or bloated systems needing subtraction. For evidence-based root-cause debugging, use mk:sequential-thinking instead.

日本語の概要は準備中です。原文の説明を表示しています。

Fast parallel codebase scouting. Spawns multiple Explore subagents to search directories simultaneously, returning a consolidated file map with architecture fingerprint, complexity estimates, and routing suggestions. Use before planning, debugging, or any task spanning multiple directories. NOT for reading a single known file in depth (use Read directly); NOT for semantic find-usages or go-to-definition.

日本語の概要は準備中です。原文の説明を表示しています。

Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: 'analyze KEY', 'rca for KEY', 'describe KEY with media'. NOT for complexity scoring (mk:jira-evaluator); NOT for story-point estimation (mk:jira-estimator).

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).

日本語の概要は準備中です。原文の説明を表示しています。

Process multimedia files with FFmpeg (video/audio encoding, conversion, streaming, filtering, hardware acceleration) and ImageMagick (image manipulation, format conversion, batch processing, effects, composition). Use when converting media formats, encoding videos with specific codecs (H.264, H.265, VP9), resizing/cropping images, extracting audio from video, applying filters and effects, optimizing file sizes, creating streaming manifests (HLS/DASH), generating thumbnails, batch processing images, creating composite images, or implementing media processing pipelines. Supports 100+ formats, hardware acceleration (NVENC, QSV), and complex filtergraphs.

日本語の概要は準備中です。原文の説明を表示しています。

Self-learning pre/post-task hooks and model/task routing from the Ruflo CLI, on a ruOS desktop. Use to add coordination, formatting, and learning around Claude Code operations, or to route work by complexity/cost.

日本語の概要は準備中です。原文の説明を表示しています。

Spin up a coordinated multi-agent swarm (hierarchical or mesh topology) to work a complex, multi-file task on a ruOS desktop. Use when a task needs 3+ agents working in parallel with anti-drift coordination; skip for single-file edits.

日本語の概要は準備中です。原文の説明を表示しています。

Use when user says "simmer this", "refine this", "hone this", "iterate on this", or asks to improve a specific artifact over multiple rounds. Runs an iterative refinement loop with investigation-first judges that read the code, understand the problem, and propose evidence-based improvements. Auto-selects single judge or multi-judge board based on complexity. Works on any artifact type: documents, prompts, specs, emails, creative writing, API designs, pipelines, codebases. Supports multi-file workspace targets, runnable evaluators, and open-ended optimization (model selection, pipeline topology, prompt tuning).

日本語の概要は準備中です。原文の説明を表示しています。

Rework a change as if the intended UX and architecture had existed from day one — deleting compatibility cruft, dead branches, and accidental complexity instead of patching around them. Use when refactoring, cleaning up after a feature lands, removing flags, collapsing legacy paths, or when the user says the code "should look like X from scratch".

日本語の概要は準備中です。原文の説明を表示しています。

Call this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.

日本語の概要は準備中です。原文の説明を表示しています。

Hypertree decomposition approach to planning problems for reduced computational complexity

日本語の概要は準備中です。原文の説明を表示しています。

Heuristic search-based temporal planning and scheduling for complex multi-constraint environments

日本語の概要は準備中です。原文の説明を表示しています。

End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards. Use for complex forms, validation architecture, autosave, field dependencies. Activate on "form validation", "react-hook-form", "Zod", "form error", "multi-step form", "wizard". NOT for simple HTML forms, backend validation only, or non-React frameworks.

日本語の概要は準備中です。原文の説明を表示しています。