'compose' 검색 결과

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Refine a draft prompt before sending to a coding agent: decomposes goal/context/constraints, flags ambiguity, emits a model-agnostic rewrite. NOT for prompts from scratch (mk:brainstorming).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Loads, lists, composes, or validates graded evaluation rubrics: PASS/WARN/FAIL grading with weighted criteria and balanced anchor examples for evaluator-style review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when refining a draft user prompt before sending it to a coding agent. Decomposes goal/context/constraints/acceptance/output-format, detects ambiguity and model-coupled framing, then emits a model-agnostic rewrite. Supports --analyze, --score, and --deep. NOT for prompts from scratch (mk:brainstorming), plans/reviews (mk:elicit), implementation plans (mk:plan-creator), or general codebase scouting (mk:scout).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when loading, listing, composing, or validating graded evaluation rubrics — PASS/WARN/FAIL grading with weighted criteria and balanced PASS/FAIL anchor examples. Triggers on /mk:rubric, "load rubric", "compose rubric preset", "validate rubric", or evaluator-style code review that needs anchor-grounded judgments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Auto-decompose large tasks into DAG-compatible parallel subtasks

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ubuntu1 배포/재배포/롤아웃, second-brain 이미지 빌드·compose up·마이그레이션 배포를 할 때 사용. rsync 경로·이미지 태그·실행 이미지 ID 대조·백업까지 체크리스트로 강제한다.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decompose an approved spec into a dependency-ordered swarm plan — one task per component, each with an explicit write_set. Produces `.claude/state/swarm/<slug>.json` with tasks + waves. The wave scheduler guarantees pairwise-disjoint write_sets within each wave so parallel dispatch is provably conflict-free.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate or repair a project's .gitignore. Composes the baseline must-ignore set (the single source of truth in baseline-ignores.json) with optional gitignore.io enrichment, and merges add-only so existing entries are never lost. Use when a repo has no .gitignore, when the commit-leak guard reports a gap, or when onboarding a new stack. Trigger: "set up gitignore", "fix my gitignore", "ignore node_modules/secrets", "gitignore for <stack>".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decompose an MVP vision into a sprint manifest — a prioritized feature list where every feature carries explicit done-criteria (a done-record reference, named edge tests, and a wiring test). Produces the sprint manifest that `sprint-oracle` checks for completeness. Use when planning a sprint of parallel work (Slice A of the sprint-mode epic). Not a workflow phase; the manifest it writes is the completeness contract a sprint is held to.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

비대한 커스텀 훅을 스코프별 서브 훅으로 분리, composer 패턴 적용, 전용 서브디렉토리 구조화

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pursue an agreed goal to a working outcome without waiting: decompose it, re-prioritise as evidence arrives, branch, gate, get an independent review (a different model or a fresh reviewer subagent — the writer never approves), merge, prune, and bank the operator's decisions in STATUS.md instead of blocking on them. Trigger on "get it done", "don't wait for me", "proceed autonomously", or when an epic or roadmap objective is handed over. Not a close-out: this work set is expected to grow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decompose an epic into atomic parallelizable tasks, route each to the right skill, and keep the four delivery records straight — issues, STATUS, ROADMAP, CHANGELOG. Use as a meta-router when several skills could apply, and as the baseline for how delivery state is recorded. Trigger at the start of any multi-track epic, when the skill count exceeds ~12, or when the records have drifted from reality.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare and risk-check the next rolling-wave slice for implementation. Use when the user wants to continue a rolling-wave project, draft one bounded slice in the main context by default, use a fresh planning author only when context or discovery cost warrants it, use a fresh preparation reviewer when semantic risk or uncertainty warrants independent pressure-testing, decompose parallel implementation chunks where appropriate, identify agent, human, either, or hybrid execution fit, write or update docs/rolling-wave/{project}/slices/NNN-slug.md, and mark that slice ready even when other slices are active.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrator - spawns an autonomous orchestrator agent that decomposes a task into subtasks and drives multiple Claude agents to completion. Use when: overmind, orchestrate, multi-agent, delegate, spawn agents, break down task, run agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Docker — Dockerfile edits, docker-compose services, containers, or the dual-container (fast + Xdebug) setup — even when the user just says 'my container won't start'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin; add lifecycle hooks; transform agent configuration, environment, MCP servers, or workspace creation; automate permissions or turn follow-ups; add a screen, sidebar header or footer item, or workspace panel; add Command Center items or slash commands; add composer pills or attachment sources; transform, render, or append agent timeline items; contribute a theme; use Paseo from plugin code; or add plugin RPCs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use Kanpeki component library in React projects. Activate when user wants to add, use, customize, or compose accessible UI components from Kanpeki (@kanpeki/*). Covers installation, component patterns, forms, theming, and dark mode with React Aria Components + Tailwind CSS 4.1 + CVA.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decompose systems into microservices and apply canonical distributed-systems patterns. Use this skill whenever the user wants to split a monolith into services, design service boundaries, choose between microservices and a modular monolith, implement sagas or the outbox pattern, set up CQRS or event sourcing, configure an API gateway or BFF, add resilience (circuit breakers, retries, timeouts), or implement distributed tracing with OpenTelemetry. Also trigger for distributed transactions, service discovery, event-driven architecture, contract testing with Pact, canary releases, and idempotent consumers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Split user stories into smaller, independently deliverable slices using the SPIDR method (Spike, Path, Interface, Data, Rules). Use this skill whenever the user asks to split a story, break down work, slice a story, asks "can this be split", mentions "SPIDR", says "story splitting", or wants to decompose a large ticket into smaller pieces. Also trigger when a user presents a story that seems too large for a single sprint and asks for help sizing or scoping it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, inherit, compose, localize, and validate YAML prototypes in the correct resource root.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.