69건 · 관련도순
Independently reviews deliverables handed over through Kanban, checks them against acceptance criteria and test evidence, and records an approval, actionable change request, or escalation when a human decision or external prerequisite is needed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage tasks on an OpenViking kanban board, where each Markdown file contains the task and its handoff notes. Record decisions, verified progress, and next steps so another agent or person can resume the work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Comprehensive kanban board and task management via ktui CLI. Use for project tracking, todo lists, task dependencies, workflow automation, and board management. Activates when user mentions boards, tasks, kanban, or project management. If the `ktui` command is not available, but `uv` is available utilize `uvx kanban-tui` instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan, set up, and monitor a multi-agent video production pipeline backed by Hermes Kanban. Use when the user wants to make ANY video — narrative film, product/marketing, music video, explainer, ASCII/terminal art, abstract/generative loop, comic, 3D, real-time/installation — and the work warrants decomposition into specialized profiles (writer, designer, animator, renderer, voice, editor, etc.) coordinated through a kanban board. Performs adaptive discovery to scope the brief, designs an appropriate team for the requested style, generates the setup script that creates Hermes profiles + initial kanban task, then helps monitor execution and intervene when tasks stall or fail. Routes scenes to whichever Hermes rendering / audio / design skill fits each beat (`ascii-video`, `manim-video`, `p5js`, `comfyui`, `touchdesigner-mcp`, `blender-mcp`, `pixel-art`, `baoyu-comic`, `claude-design`, `excalidraw`, `songsee`, `heartmula`, …) plus external APIs for TTS, image-gen, and image-to-video as needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prototype a single-screen kanban task board in HTML, with columns for work stages, task cards, assignee avatars, estimates, and filters. A sprint summary highlights progress, leading assignees, and blocked tasks for a team overview.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate valid fancy-kanban boards — markdown-embedded kanban boards with typed fields, swimlanes, workflow rules, and card face configuration for Obsidian and compatible tools
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The 'don't do the work yourself' rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
여러 AI 에이전트에 담당 범위와 완료 조건을 배정하고 병렬 작업을 관리합니다. 칸반으로 진행 상황과 장애 요인을 공유하며 테스트와 검토를 거쳐 결과를 통합합니다.
영상 요청을 제작 계획으로 정리하고 스타일에 맞는 전문 에이전트 팀과 작업 환경을 구성합니다. Hermes 칸반으로 작업을 배분하고 진행 상황과 중단·실패한 작업의 대응을 돕습니다.
Check kanban boards, which organize tasks into columns, and retrieve task lists filtered by status, assistant, or board. Use the returned data to see task counts and review work in progress.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian file-based, or manual mode). Async-first output. Six modes — setup (scaffold a new board for a business), triage (Eisenhower-sort the backlog), next (pick the next thing to work on, single board or across all), status (paste-ready async snapshot), unblock (diagnose Review/Blocked column), weekly (Friday pulse + week planning). Triggers on "/pm," "/pm setup," "/pm triage," "/pm next," "/pm status," "/pm unblock," "/pm weekly," "what should I work on next," "kanban status," "Eisenhower this," "triage my backlog," "what's blocked."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decomposition playbook + specialist-roster conventions + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pitfalls, examples, and edge cases for FETIH Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate multiple Claude Code workers through an existing Kanban board. This guide describes task dispatch, automated checks before AI review, per-task cost tracking, human intervention, and recovery after restarts; the runtime and integrations require separate installation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build the user interface for a holaOS app whose data resources are already connected through the SDK. Choose a feed, table, kanban board, form, or calendar layout using shared components and workspace styling.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design a Trello-style task board with four progress columns, filter controls, and cards showing labels, due dates, assignees, and comment counts. Optional grouped rows organize work by larger initiatives or assignees, with cards styled to look draggable.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
AgentFlow workflow skill. Use this skill when the user needs Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage the kanban board. List, read, and close GitHub issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Kanban flow metrics to identify bottlenecks and improve team throughput. Covers Cycle Time, Throughput, WIP, and Flow Efficiency using Little's Law and Theory of Constraints. Use when a team wants to optimize delivery flow or improve predictability. Do not use for sprint-based Scrum planning — use sprint-planning-assistant instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.