'backlog' 검색 결과

GitHub 이슈와 PR을 대조해 중복 작업, 수정 PR이 없는 보안 지적, 미해결 중대 버그를 정리하고 우선 조치와 건수를 보고서로 제공합니다.

• 스프린트 전에 이슈와 PR을 점검할 때
• 같은 수정을 진행하는 PR을 찾을 때
• 수정 PR이 없는 보안 지적을 확인할 때

GitHub의 미처리 PR을 변경 규모, CI 결과, 충돌, 정체 상태에 따라 정리하고 검토 우선순위를 제시합니다. 선택한 PR의 상세 검토와 승인 후 댓글 게시도 지원합니다.

• 미처리 PR의 검토 순서 결정
• 변경 중복과 CI 실패 확인
• 지정한 PR의 상세 검토

Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a backlog of open issues and pull requests
• Checking whether reported bugs are already fixed
• Assessing pull request readiness for merging

Plan A/B tests to compare page changes using clear hypotheses and meaningful measures. The skill helps define sample size, duration, traffic allocation, and result interpretation, and organize a continuing program of prioritized experiments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare headlines or signup buttons
• Estimate test sample size and duration
• Interpret results and possible adverse effects

Capture unexpected behavior and workarounds encountered while using Prisma 8, Prisma Compute, or Prisma Postgres. Record symptoms, causes, versions, and reproduction steps in a local log linked to a Linear ticket, checking for duplicates first.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording an unexpected Prisma error and its workaround
• Documenting undocumented behavior found in an example app
• Preserving reproduction steps from a customer report

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking the details of an issue by its key
• Listing tickets assigned to you
• Drafting and creating a new issue

Process vendor bills, assign accounting categories, check cash forecasts, and prepare a payment run for approval. Separate approvals for recording bills and paying them help owners review both the accounting entries and the proposed spending.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Process a backlog of vendor bills
• Check available cash before paying bills
• Prepare this week's payment list

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Forecasting sprint workload from past delivery data
• Assessing team health and prioritizing improvements
• Tracking retrospective actions and recurring themes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess technical debt across a codebase
• Prioritize refactoring for the next sprint
• Compare debt levels before and after cleanup

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Grouping customer requests into themes
• Selecting the top three requests for product goals
• Considering alternatives to requested features

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a sprint planning meeting
• Estimating capacity around leave and other duties
• Selecting backlog work that fits team capacity

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing open bugs at the start of a sprint
• Organizing new bugs after a team QA review
• Reviewing a backlog with more than ten open bugs

Prepare a daily NemoClaw maintenance plan by ranking pending pull requests and issues, checking work carried over from earlier versions, and selecting release targets. Produce a queue with owners, next actions, and merge readiness.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan the day's maintenance work
• Find work carried over from earlier releases
• Rank pull requests for review

Connect AI agents to Jira and Confluence through MCP, a protocol for accessing external tools. This skill guides issue searches and updates, page management, sprint workflows, authentication setup, and troubleshooting of Atlassian integrations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find Jira issues by assignee or status
• Search and update Confluence pages
• Turn meeting notes into Jira ticket updates

Review open issues and discussions to create a clear work queue. Record the five highest-priority items, suggested labels, possible duplicates, and cases needing human judgment in a state file for future reviews.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing a backlog of open issues
• Finding possible duplicate reports
• Preparing label suggestions

Translate user needs into concise stories that explain who benefits, what they want, and why. Add Gherkin acceptance criteria—preconditions, an action, and an expected result—to support development discussions and testable definitions of success.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning requirements into user stories
• Defining testable acceptance criteria before development
• Preparing stories for backlog refinement and sprint planning

Guide a team through questions about users, workflows, and priorities to create a user story map. Organize activities and tasks, then define a minimum viable product and later releases that each cover the full workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Facilitating a team story mapping workshop
• Reorganizing a flat backlog around user workflows
• Defining the scope of a minimum viable product

Guide a team from product positioning and customer problem research to prioritized initiatives and a roadmap. Coordinate validation, stakeholder feedback, and execution planning so the team can connect its strategic direction to concrete work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Establishing direction for a backlog without a clear strategy
• Planning a new product or major initiative
• Revisiting target customers and product differentiation

Break a large feature into smaller user stories, each describing a useful change for users. Apply nine splitting patterns, define acceptance criteria, and assess which work to deliver first, defer, or remove.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Splitting an onboarding epic into smaller user stories
• Breaking down a reporting feature before sprint planning
• Choosing a split pattern for an admin workflow

Collect posts from X profiles by username, choosing regular posts, posts with replies, or media posts. Receive structured text, author details, engagement counts, and media information for account research and content tracking.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Research posts from competitor accounts
• Collect a creator’s posting history
• Gather posts that include photos or videos

Sort open GitHub issues by category, risk, inactivity, and possible duplication. Examine selected reports in detail, identify missing information, and prepare comments, labels, or closures for user approval before taking action.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sort accumulated bug reports and feature requests
• Check possible duplicates against open and closed issues
• Review inactive issues for follow-up or closure

Turn an accepted feature proposal into an implementation specification grounded in existing code. Define scope, explain design decisions, track unresolved questions, and document migration steps and tests, with implementation tasks added when the work is approved for building.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn an accepted proposal into an implementation specification
• Record design choices and unresolved questions
• Plan migration stages and test coverage

Turn a design problem into an RFC, a proposal for review and discussion. Define who benefits and what changes, compare real alternatives, document drawbacks and open questions, and save a linked, validated draft.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting an RFC for a design change
• Clarifying beneficiaries and observable outcomes
• Comparing alternatives and design drawbacks

Sort incoming issues and pull requests, verify their claims, and assign clear triage states. Record missing information, decisions needed, and actionable handoff notes so maintainers can see which items are ready for work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sorting a backlog of issues and pull requests
• Reproducing a newly reported bug
• Identifying missing details in an unclear report