328건 · 관련도순
Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop. Use when the user asks to "triage improvements", "triage the backlog", "clean up the backlog", "clean up improvements", "groom the backlog", "prune the improvements backlog", or "go through the backlog with me".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews deferred project tasks alongside their descriptions and supporting files, then lets users promote, keep, or remove each item. Promoted tasks join the active milestone with updated phase numbers and roadmap entries.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
EXPERIMENTAL. Use when working the project-wide out-of-scope backlog at .reviews/code/backlog.md and .reviews/security/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is the agentic-review skill — and not for reviewing a branch diff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
EXPERIMENTAL. Use when working the project-wide out-of-scope backlog at paad/code-reviews/backlog.md and paad/security/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is /agentic-review — and not for reviewing a branch diff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides agents through authoring BACKLOG.md and OpenSpec change folders. Use when running /cc-backlog or /cc:backlog, creating or appending backlog items, or preparing work for /cc-openspec. Delivery is skill openspec.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess incoming leads or rank a lead backlog by customer fit and buying intent. Receive evidence-based priorities, routing recommendations, and suggested first responses, with existing account ownership checked when CRM records are available.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn feature ideas into backlog items, a team's planned units of work, using Why, What, and Acceptance Criteria. Connect each item to business goals and define observable outcomes in independent pieces sized for one sprint.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. _workspace/discovery*/FEATURE_BACKLOG*.md), 'all the features', many features across multiple releases, or a long autonomous build campaign, AND for every follow-up: continue/resume the campaign, run the next wave, re-run a failed wave, fold in QA results, or check campaign status. Backed by a ledger.json so re-running is idempotent (skips shipped work, resumes interrupted work) and resilient (retry-once then quarantine-and-continue). For a SINGLE feature or one small batch, use tdmcp-pipeline instead; this skill is for the whole ledger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-PLCのスキル（/04-operation 等）を通さずに済ませた作業を、あとから対象 Layer に記録する。どの Layer の作業かを決め、会話にしか無い中間生成物を Documents/ に書き起こし、backlog に ad-hoc タスクとして足し、04-operation の Phase 5.5〜7（検証・ステータス更新・Propagation）を通す。書き込み前に必ず承認を取る。「Propagationして」「さっきの作業を記録して」「Layerに残して」「backlogに後追いで入れて」で使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and maintain a product or project backlog with prioritized items, acceptance criteria, and estimates. Covers user story writing, MoSCoW prioritization, backlog grooming, item splitting, and status tracking. Use when starting a new project and converting scope into actionable items, during ongoing grooming before sprint planning, re-prioritizing after stakeholder feedback or scope changes, or splitting oversized items into implementable pieces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan, order and deliver a batch of backlog items (e.g. every High item) in a Conventional Docs repo, one decision, branch, worktree, draft PR, review and merge per item. Use when asked to work through the backlog, implement all items of a priority, or sequence several backlog items end to end.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. _workspace/discovery*/FEATURE_BACKLOG*.md), 'all the features', many features across multiple releases, or a long autonomous build campaign, AND for every follow-up: continue/resume the campaign, run the next wave, re-run a failed wave, fold in QA results, or check campaign status. Backed by a ledger.json so re-running is idempotent (skips shipped work, resumes interrupted work) and resilient (retry-once then quarantine-and-continue). For a SINGLE feature or one small batch, use tdmcp-pipeline instead; this skill is for the whole ledger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize a GitHub issue backlog by shared root cause, with one main tracking issue and design document per group. Route new reports into existing plans and prepare pull requests that address related bugs together with regression checks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Rank problems and proposed fixes using four scored criteria: expected benefit, implementation cost, deployment ease, and risk. The skill produces a sorted priority table with scoring rationales and explains why the top three items should come first.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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 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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare feature ideas by expected impact, required effort, uncertainty, and fit with product goals. Get five ranked recommendations, with reasons for each choice, trade-offs, and explanations of which ideas should receive lower priority.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review new and spiking Sentry errors, rank their impact, and check for existing GitHub issues. Create triage issues for the highest-impact untracked errors and post a Slack summary, while leaving Sentry error states and assignments unchanged.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn rough meeting notes, customer requests, and product ideas into structured backlog entries, a list of possible improvements. Capture who needs each idea and why, categorize it, and update matching entries with new evidence.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Map a user's journey into activities, steps, and tasks, then organize the work by priority and release. The skill helps teams define a usable first version, place backlog items in context, and spot missing parts of the experience.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.