337건 · 관련도순
Diagnose stalled, blocked, overloaded, or unhealthy Agiflow projects and recommend specific corrective actions. Use for project health checks, blocked work, conflicting priorities, obsolete tasks, overloaded assignees, or an unmanageable backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story or acceptance criteria, scope a spike, open an epic, or break work into tasks. Triggers on write a ticket, create an issue, file a bug, bug report, user story, spike, epic, task breakdown, turn this into tickets, break this down, acceptance criteria, definition of ready, ready for dev, backlog item, capitalization stage. Also triggers when the user pastes a PRD, a spec, or a bug description and asks what to do with it, even if they never say the word ticket.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a trusted capture-and-triage front door so no commitment lives in your head. Use when open loops keep slipping, an inbox has become a backlog, or vague notes never turn into action.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map, measure and improve business processes — SIPOC and swimlane capture, cycle-time and bottleneck analysis, handoff diagnosis, and a payback-ranked improvement backlog. Use when a process is slow, error-prone, or crosses too many teams.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integrates with Atlassian products to manage project tracking and documentation via MCP protocol, including Jira issue management, Confluence page editing, sprint and backlog management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하며, 인용되는 콘텐츠를 계속 생산하는 서브 블로그·콘텐츠 운영 파이프라인까지 세팅하는 스킬. 사이트를 검색엔진·답변엔진·생성 AI·네이버 AI 브리핑이 인용하는 1차 소스로 만든다. "SEO 해줘", "AI에 인용되게 해줘", "네이버 노출 늘려줘", "llms.txt 만들어줘", "블로그 만들어줘/글 써줘", "콘텐츠 백로그·캘린더 잡아줘", "낡은 글 갱신해줘" 류 요청에 사용. Use for "audit my site's SEO", "get my site cited by ChatGPT/Perplexity/AI Overviews", "improve search visibility", "create llms.txt", "answer engine / generative engine optimization", "set up a blog that gets cited", "content backlog / calendar / refresh", and any AI-search-visibility request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Close the post-launch loop — turn a live app's App Store signals (reviews, analytics, sales, crashes, listing conversion) into a metric-tagged backlog for the next version, AND verify whether last cycle's changes moved the metric they promised to move. Read-only on App Store Connect; every change is surfaced and routed to another command, never auto-applied. Use before planning the next version, on a monthly cadence, or ~1-2 weeks after shipping to check if a change worked.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execution-gap audit - cross-references the startup idea backlog against shipped skills, prototypes, and cross-repo PRs, surfacing the top 3 ideas to build next by narrative and operator fit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Three-mode idea engine - generate collides the week's zeitgeist with what you can ship into scored wedges; validate viability-screens the idea backlog; memo writes evidence-backed startup memos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from `git status`, or to review a specific backlog task by id such as `task-65` or `TASK-65`. Also trigger when the user says things like "review", "review current changes", "check my changes", "look over the diff", or "review task-42".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
User story mapping for backlog management and outcome-based prioritization. Load during Phase 2.5 (User Story Mapping) to produce story-map.md and prioritization.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
LeanUX backlog management methodology - user story template, story sizing, story states, task types, Definition of Ready/Done, anti-pattern detection and remediation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Podcast knowledge workflows powered by Podwise CLI: search podcasts and episodes by keyword, monitor followed shows for new releases, find popular episodes, ask questions and extract insights from transcript content, process Podwise episode URLs, YouTube videos, Xiaoyuzhou links, and local audio or video files to retrieve transcripts, summaries, chapters, Q&A, mind maps, highlights, and keywords — plus catch up on your backlog, refine your listening taste, generate weekly recaps, export episode notes to PKM tools, research topics across podcasts, debate episode ideas, and generate language learning cards. Use when the user wants to find, summarize, transcribe, or extract insights from any podcast or audio content, or manage their listening library.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something improvable during work that falls outside the current task's scope, or after deliberately shipping a simpler approach that accepts a known ceiling — briefly mention it to the user and offer to note it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load code-style and task-specific skills, make the change described by the current context, then run post-implementation QA. Use for ad-hoc changes when no plan file or improvements backlog governs the work, and when the user asks to "just implement", "implement directly", "implement without a plan", or "apply the change".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.