354건 · 관련도순
Create a game development test plan for a sprint, feature, or individual task. Classify the work and specify automated tests, manual checks, basic functionality checks, and playtest needs from documented requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review unresolved game bugs by separating impact from urgency, then recommend repair priorities and sprint assignments, meaning work planned for a development cycle. Reports also highlight recurring problems, older issues, and bugs in previously completed work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Team minutes, retros, and decision history to keep: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history. Use when the user says: operating-rhythm, operating rhythm, meeting minutes, meeting history, scrum record, sprint planning, sprint review, sprint retrospective.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scrum-inspired paper review, revision, and R&R workflow. Handles docx/tex/md/PDF in English or Chinese. Auto-detects manuscript stage, estimates sprint count, runs multi-lens review (Contribution/Rigor/Writing/Editor), generates prioritized revision backlog, exports MD/DOCX/PDF/HTML reports. Use when asked to review a paper, revise based on reviewer comments, handle R&R, respond to peer review, plan paper revision sprints, or when user types /ps or /papersprint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and execute effective sprints using Agile methodologies. Define sprint goals, estimate user stories, manage sprint backlog, and facilitate daily standups to maximize team productivity and deliver value incrementally.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CRISP Execute — Sprint execution loop with change request management, security gates, product gates, and stakeholder reporting. Use after Phase S (Spec) is complete and crisp-state.json shows ready_for_execute: true. Triggers on "start sprint", "begin build", "execute", "sprint 1", "run sprints", or when handed off from crisp-orchestrator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate sprint planning by organizing backlog items, estimating effort, balancing capacity, identifying dependencies, and producing a sprint commitment summary. Use when teams need structured sprint planning output. Do not use for strategic roadmap planning, annual budgeting, or product vision work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA agile via the jira-as wrapper: epics, sprints, backlog, ranking, story points, subtasks, velocity. Triggers: 'create sprint', 'add KEY to sprint', 'set story points on KEY', 'rank KEY before KEY', 'velocity for board', 'epic add'. Board ID ≠ project key. NOT for issue CRUD (mk:jira-issue); NOT for time tracking (mk:jira-time).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Periodically inspect a sprint manager and worker sessions against a sprint spec, classify progress, nudge only for real stalls, and always append a checkpoint log beside the sprint file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
スプリント計画を実行する。GitHub Issues からバックログ整理→タスク分解→マイルストーン設定→sprint-state.md生成を自動化する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a sprint tracking issue (label `sprint`) on peterdrier/Humans needs working — routine-fired cloud runs, or any unattended session told to execute the sprint queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agile boards, sprints, relatórios de tempo, anexos e operações em lote no YouTrack via REST API direta — o que o MCP oficial não cobre. Use quando o usuário disser "board", "quadro", "sprint", "sprint atual", "mover para o sprint", "horas registradas", "relatório de tempo", "anexar arquivo", "aplicar comando em várias issues". Requer YOUTRACK_BASE_URL e token.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize GitHub issues, synchronize project boards, and plan sprints, or short work cycles. Coordinate multiple AI agents to break issues into tasks, assign work, update progress, and track dependencies across a project.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinate project delivery by routing requests to eight specialist skills or running a verified delivery workflow. Use live Jira data for progress analysis and completion forecasts, with recorded evidence and checks before tasks are closed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Scan a codebase for technical debt—issues that make future maintenance harder—and prioritize fixes using business impact and effort. Generate a ranked backlog, sprint allocations, and trend reports to assess cleanup work over time.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Run a structured sprint retrospective, a review of a short work cycle, using team feedback and delivery results. Identify shared themes and produce two or three prioritized improvements with owners, deadlines, and measures of success.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.