24건 · 관련도순
Manage GitHub issues, synchronize project boards, and plan sprints, short development cycles. Coordinate multiple AI agents to break work into tasks, assign responsibilities, update progress, and produce reports on completion and blockers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a realistic Linear cycle plan from current priorities, dependencies, estimates, carryover, and team capacity without silently rescheduling work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agile product ownership for backlog management and sprint execution. Use for writing user stories and acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing a backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan sprints with story point estimation, capacity planning, sprint goals, and retrospective frameworks. Organize teams for effective iteration with clear goals, realistic commitments, and continuous improvement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
🇺🇸 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" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when prioritizing a Salesforce backlog with the MoSCoW method (Must / Should / Could / Won't) plus an effort + value lens, deciding what fits in the next sprint or release, and using WSJF as a tie-break when MoSCoW alone produces ties. Trigger keywords: MoSCoW prioritization, must should could won't, WSJF salesforce, prioritize salesforce stories, sprint commit, backlog grooming. NOT for story writing or splitting (use admin/user-story-writing-for-salesforce). NOT for release train planning (use agents/release-train-planner). NOT for sizing/estimation method debates — this skill assumes a sizing convention is already in place.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Estimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.