355 个 · 按相关度排序
Create or update a sprint plan, a short development work plan, using existing work items, completed work, and available capacity. Organize priorities, carryover, dependencies, and risks, and produce a progress report.
中文简介正在准备中。当前显示英语简介。
Run the measurement and ceremony layer of a delivery team: the metric set, estimation and capacity, the five sprint ceremonies, and the sprint report and quarterly rollup. Use this skill whenever the user is acting as PMO or scrum lead, planning a sprint, running standup, refinement, review, or retro, measuring velocity, cycle time, or throughput, checking capacity, or reporting on how a team is doing. Triggers on PMO, sprint planning, plan the sprint, standup, refinement, backlog grooming, sprint review, retro, velocity, capacity, cycle time, lead time, throughput, WIP, burndown, carryover, sprint report, story points to hours, how is the team doing, delivery metrics, agent lanes. Also triggers when the user asks how much work fits in a sprint or whether a team is on track, even if they never say sprint or PMO.
中文简介正在准备中。当前显示原文说明。
🇺🇸 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" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"
中文简介正在准备中。当前显示原文说明。
Summarises one sprint from the board export, sprint report and review or stand-up notes the user provides into a one-page DRAFT sprint review summary: the sprint goal as written, items delivered, items not delivered with the reasons the sources state, carry-over, impediments, metrics exactly as given, and numbered questions for the retrospective, every row referenced to a work item or note fragment and every missing fact marked UNKNOWN. Use when the user asks to "summarise the sprint", "write the sprint review", "what did we deliver this sprint", "list the carry-over and blockers" or "draft the sprint recap". Do not use for the retrospective write-up or themed lessons across several sprints, use lessons-learned-synthesis instead; for a weekly project status report, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Read sprint plans and work records to summarize completion, remaining time, blocked tasks, and emerging risks. Compare progress with elapsed time, flag stale work, and provide a concise status report with at most one recommended action.
中文简介正在准备中。当前显示英语简介。
Build a sprint plan around team availability, including time off and meetings. Define goals, prioritize backlog items, handle unfinished work, and document capacity, dependencies, risks, completion criteria, and key dates.
中文简介正在准备中。当前显示英语简介。
Plan a sprint by refining backlog items, defining a sprint goal, calculating team capacity, selecting items, and decomposing them into tasks. Produces a SPRINT-PLAN.md with goal, selected items, task breakdown, and capacity allocation. Use when starting a new sprint in a Scrum or agile project, re-planning after significant scope change, transitioning from ad-hoc work to structured sprint cadence, or after backlog grooming when items are ready for inclusion.
中文简介正在准备中。当前显示原文说明。
Analyze sprint history to forecast delivery ranges, score team health, and track retrospective actions. Python tools turn structured sprint data into reports that support planning, highlight recurring problems, and show whether improvement efforts are progressing.
中文简介正在准备中。当前显示英语简介。
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.
中文简介正在准备中。当前显示原文说明。
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.
中文简介正在准备中。当前显示原文说明。
Use when negotiating a file-based sprint contract between the generator (developer) and evaluator before code is written. Translates a product-level spec into testable acceptance criteria with rubric tie-ins. Triggers on /mk:sprint-contract, "draft a sprint contract", "negotiate scope for sprint", or before any harness-driven sprint kicks off.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Planifie le prochain sprint : calcule la capacité (vélocité glissante 3 sprints), reporte les tickets non livrés du sprint courant, puis complète depuis le backlog par priorité jusqu'à la capacité. Présente le plan, attend validation, puis assigne les tickets au sprint. Usage: /plan-sprint [<titre-sprint-cible>]
中文简介正在准备中。当前显示原文说明。
Turn large product requirements into user stories with acceptance criteria, effort estimates, and priorities. The toolkit supports backlog management, sprint planning based on team capacity, and tracking how much work the team completes over time.
中文简介正在准备中。当前显示英语简介。
Build a sprint plan for a short development cycle using team availability and recent delivery history. Select work that fits capacity, sequence dependent tasks, identify owners and risks, and reserve room for unexpected work.
中文简介正在准备中。当前显示英语简介。
Act as the team's Scrum Master of record, or copilot to a human one: plan sprints, run daily pulses, close sprints, prepare and follow up retrospectives, track and escalate impediments, and detect process anti-patterns across sprint history. Use whenever the user asks for Scrum or agile process help, in any language — "plan the sprint", "chuẩn bị retro", "how is the sprint going", "our velocity dropped", "track this blocker", "the same problem keeps coming back" — even without the word "Scrum", and whenever `_project/scrum-master/` exists and the question touches sprints, ceremonies, impediments, or team process health. Not for delivery dates and budget (project-manager) or deciding what to build (product-manager).
中文简介正在准备中。当前显示原文说明。
Review a sprint or milestone by comparing planned work with actual results. Summarize completion, estimation gaps, and blockers, then produce a retrospective with specific improvement actions, owners, and deadlines for the next iteration.
中文简介正在准备中。当前显示英语简介。
Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro. Args: [sprint number | dates]. No args = infer the current sprint.
中文简介正在准备中。当前显示原文说明。
The sprint completeness oracle — a mechanical, exit-code-driven check that every feature in a sprint manifest is provably complete across three dimensions (a done-record reference, resolvable edge tests, and a resolvable wiring test). Fails loud with a per-feature gap list naming the missing dimension. Read-only. Use to gate a sprint before it is called done (Slice A of the sprint-mode epic), or any time you want a completeness reading.
中文简介正在准备中。当前显示原文说明。
Calcule la vélocité des sprints terminés (Σ points des tickets feuilles livrés) et recommande la capacité du prochain sprint. À lancer en fin de sprint. Thin wrapper bash sur sprint_velocity.sh, zéro LLM lourd. Usage: /velocity [<titre-sprint>]
中文简介正在准备中。当前显示原文说明。
在仓库文件中管理开发计划，将大目标拆成小任务并分配到迭代，记录实现、审查和合并确认的进展，无需外部项目管理工具，还可检查任务文件与汇总表的不一致。
用HTML制作单屏看板原型，将任务卡片分为待办、进行中、审核中和已完成四列，展示负责人、预估点数、筛选搜索、迭代进度及受阻任务。
通过多个AI代理协作，分类和拆分GitHub议题、分配任务并同步项目看板，同时协助制定短期开发计划，编写进度与阻碍事项报告。
Manage Jira issues through natural language using jira CLI or Atlassian MCP, a tool connection. Search and view tickets, draft new issues, update assignments or status, and check sprints, with review and approval before changes.
中文简介正在准备中。当前显示英语简介。