multica
Managed-agent teamwork, issue assignment, progress tracking, reusable-skill compounding, and handoff workflow adapted from multica-ai/multica for OMK. Use when coordinating multiple agents, converting work into agent-ready tasks, tracking blockers, or turning repeated solutions into skills.
git clone --depth 1 https://github.com/dmae97/open-multi-agent-kit /tmp/multica && cp -r /tmp/multica/templates/skills/kimi/multica ~/.claude/skills/multicaSKILL.md
# multica Source basis: multica-ai/multica at commit 24a59098d65e52797df6a4f4e4de2a6299f10afc. This OMK skill is a compact adaptation, not a vendored copy of upstream prompts or code. ## Use when - Work needs multiple lanes, agent handoffs, reviewer/QA passes, or issue-board style tracking. - A user asks to coordinate OMX/Kimi/Codex agents or compound reusable skills. - You need to turn a broad request into assignable, verifiable tasks. ## OMK workflow 1. Define the board: goal, stop condition, lanes, owners, write scopes, verification gates, and worker limit. 2. Split only independent work. Keep blocking critical-path tasks local unless delegation was explicitly requested. 3. For each lane, provide goal, scope, files, constraints, expected output, and proof required. 4. Track lifecycle: queued, in progress, blocked, review, verified, done. Include blocker reason and next action. 5. Merge results through a reviewer/integrator pass. Do not accept agent output without diff review and gates. 6. When a repeated pattern proves useful, convert it into a compact OMK skill with source, trigger, workflow, output contract, and guardrails. ## Output contract Return: - lane/task board - agent or local owner per lane - status and blockers - integration decisions - reusable skill candidates - verification evidence ## Guardrails - Respect configured worker limits and user permission for parallel agents. - Do not run install scripts, Docker, cloud setup, or daemon startup unless the user explicitly requests that operational change. - Do not let agent parallelism create overlapping write scopes.
Persistent memory, recall, session replay, and memory-governance workflow adapted from rohitg00/agentmemory for OMK. Use when setting up agent memory, deciding what to remember, importing/replaying sessions, reducing repeated context, or auditing memory safety.
Minimal, goal-driven, surgical coding workflow adapted from forrestchang/andrej-karpathy-skills for OMK. Use for coding, refactoring, debugging, and review tasks where assumptions, overengineering, or broad edits could cause regressions.
Legal workflow drafting, triage, review, research planning, legal operations, law-student or clinic support, and legal AI governance adapted from Anthropic claude-for-legal. Use for commercial, privacy, product, corporate, employment, regulatory, AI governance, IP, litigation, legal-clinic, and law-student tasks. Draft-only; attorney review and current source verification required.
Real-engineering alignment, shared-language, TDD, diagnosis, and architecture-review workflow adapted from mattpocock/skills for OMK. Use before non-trivial implementation, ambiguous product work, debugging loops, test-first changes, or codebase architecture cleanup.
Review AdaptOrch, OMK, and similar DAG multi-agent orchestration frameworks. Use when assessing DAG node responsibility, dependency edges, worker write authority, fallback/retry/timeout/evidence gates, review/merge boundaries, or reproducible decision traces.
Optional read-only OMK web/social/video research workflow inspired by Panniantong/Agent-Reach. Use for web search, current social evidence, YouTube/Bilibili/Reddit/Twitter/X/RSS/GitHub public research, and Agent Reach availability checks without auto-installing or collecting credentials.
Backend API review for NestJS, Express, FastAPI, database access, validation, auth, error handling, and API contracts.
Adversarial code review for diffs, logic correctness, type safety, test coverage, and security risk.