'backlog' 검색 결과

Review open issues and discussions to organize a project's backlog. Identify possible duplicates, suggest priorities and labels, and record the top five actionable items and cases needing human attention in a state file.

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

• Organizing a growing issue backlog
• Selecting the top five actionable issues
• Suggesting labels and possible duplicates

Route project management requests to the appropriate GSD skill. Use it to start projects, onboard existing code, manage milestones, import plans, or review backlog items without choosing the individual skill yourself.

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

• Start a project or onboard an existing codebase
• Create or complete a development milestone
• Audit a milestone or summarize its status

Capture tasks and ideas in GSD as structured todos, notes, backlog entries, or future ideas with trigger conditions. You can also browse pending todos, choose work to start, and review previously captured future ideas.

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

• Saving tasks as structured todos
• Capturing quick notes and promoting them later
• Parking ideas in the backlog

Route requests for idea exploration, rough planning, time-boxed technical investigation, phase specifications, or thought capture to the appropriate GSD skill. It selects and invokes a skill based on the intended task.

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

• Explore an idea or opportunity
• Sketch a rough design or plan
• Run a time-boxed technical investigation

Identify maintenance problems across code, architecture, tests, dependencies, documentation, and infrastructure. Rank them by impact, risk, and effort, then produce a prioritized backlog with business reasons and a phased improvement plan alongside feature development.

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

• Deciding which parts of the codebase to refactor first
• Organizing maintenance issues across technical areas
• Explaining the business reasons for technical improvements

Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.

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

• Grouping accumulated bug reports by root cause
• Planning one fix for several related issues
• Checking test evidence before closing issues

Audit groups of bug reports to find shared root causes, checking claims against current code and tests. Produce a cause map, prioritize fixes that remove faulty mechanisms, and document which issues have enough evidence to close.

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

• Grouping backlog issues by shared root cause
• Checking whether old bug reports still apply
• Comparing fixes that remove faulty mechanisms

Turn raw security findings into a ranked list for engineering review. Check claims against source code, merge duplicates, assess how feasible exploitation is, and assign component owners, with results in JSON and Markdown.

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

• Validating security scanner findings
• Merging duplicate findings across scans
• Prioritizing a vulnerability backlog

Split large feature requests or user stories, descriptions of what users need, into smaller deliverable pieces. Eight patterns guide the breakdown, with acceptance criteria and checks that each piece provides value and can be developed and tested independently.

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

• Breaking down work that will not fit in one sprint
• Clarifying backlog items that are too large to estimate
• Separating stories with multiple acceptance scenarios

Find a valuable gap in test coverage by checking code, existing tests, and QA priorities. The skill creates at most one locked GitHub issue with concrete test cases, ready for later implementation.

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

• Finding past bugs that lack regression tests
• Reviewing recent changes for untested behavior
• Preparing a QA backlog without implementing tests

Add an idea to the backlog parking lot (999.x numbering)

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

Shared work-item templates and conventions for ADO and GitHub backlog handoff across the RAI, Security, SSSC, Accessibility, and Privacy planners

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

Mutating backlog execution for Azure DevOps, GitHub, and Jira. Use to create one item or apply a reviewed handoff to a confirmed tracker.

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

Read-only backlog planning for Azure DevOps, GitHub, and Jira. Use to discover, triage, sprint-plan, or resume without mutating a tracker.

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

Shared backlog conventions for Azure DevOps, GitHub, and Jira. Use for platform resolution, autonomy tiers, sanitization guards, and story quality, and for Azure DevOps pull request creation and build status or log retrieval.

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

Review Agiflow Planning tasks for readiness, prioritize approved work, group related tasks into work units, and promote ready tasks to Todo. Use when grooming a backlog, organizing planned tasks, creating work units, or deciding what should be executed next.

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

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."

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

Use when the user wants to park an idea or feature request that is not ready for active planning, or says add it to the backlog. Writes a 999.x entry to ROADMAP.md and creates its phase directory for later promotion.

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

Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement backlog", "tackle improvements", or "implement noted improvements".

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

Scores backlog items with RICE/WSJF/Kano and files GitHub issues for top candidates. Use when triaging a roadmap or prioritizing features for a sprint.

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

Maintenance of the contributor issue pipeline for JSONbored/awesome-claude (HeyClaude) — closing issues that are already done but not marked so, and keeping a small, high-value contributor-available backlog stocked with real website/content/feature/bugfix work. Runs every ~24h via a dedicated scheduled task. Invoke for "run the issue gardening", "audit open issues for stale/complete ones", "generate new contributor issues", or any recurring/scheduled run of this process. `reference.md` (next to this file) has the exhaustive label/milestone/ template detail — read it before doing real work, not just this file. This is the awesome-claude-specific instance; JSONbored/loopover and JSONbored/metagraphed each have their own separate copy with different conventions and a much larger backlog target — do not cross-apply either repo's specifics to this one without being asked.

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

Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Loops through triage, dependency analysis, parallel fix streams, a test gate, and re-audit until the target is met. Use after a gap analysis, audit, or review produces 10+ findings, or to burn down a large bug or tech-debt backlog.

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

Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.

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

Review and promote backlog items to active milestone

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