「grooming」の検索結果

Use when creating, grooming, planning, or closing a backlog item. Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend. Activates on interactive browsing with no arguments, loading an item by issue reference or title match to run grooming and SAM planning, autonomous unattended runs that substitute evidence-derived decisions for clarifying questions, a quick path for one-file fixes where full grooming is disproportionate, dismissing an item without completion under a required reason (duplicate, out of scope, superseded, wontfix, blocked), marking an item done with an evidence trail and required summary, or initializing GitHub tracking infrastructure for a project. Stops when the item already has a plan or is blocked on missing information.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.

日本語の概要は準備中です。原文の説明を表示しています。

Hourly error-backlog grooming sweep for {{sentry_project}}. Groups new and spiking errors, dedupes against existing GitHub issues in {{triage_repo}} by Sentry issue ID, drafts a GitHub issue with the stack trace and impact for the top {{max_issues_per_run}}, and posts a sweep summary to {{alert_channel}}. Never resolves, ignores, mutes, or assigns an error.

日本語の概要は準備中です。原文の説明を表示しています。

Canonical three-section structure for Linear and Superset tickets in this repo. Use when creating, drafting, or grooming a ticket.

日本語の概要は準備中です。原文の説明を表示しています。

Triages a repository's open GitHub issues and pull requests via the gh CLI. Optionally reviews and merges ready PRs — incrementally merging passing automated/bot PRs and maintainer-approved ones, and spawning review subagents for never-reviewed ones — then closes already-resolved issues with comments citing the resolving PR or commit, cross-links issues with their pending fix PRs, and assigns local-only priority and change-size estimates for everything outstanding. Use when triaging, grooming, or reviewing a repository's open issues and PRs.

日本語の概要は準備中です。原文の説明を表示しています。

Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.

日本語の概要は準備中です。原文の説明を表示しています。

Use when grooming hair or fur in Maya with XGen (Interactive Groom splines or legacy descriptions): scalp hair, eyebrows, eyelashes, fur, guides, clumps, noise, parting, density maps, a fill layer, aiStandardHair shading, noisy or flickering hair renders, hair that must move (Linear Wire, nHair, Alembic caches), or a groom for Unreal (groom Alembic, cards). Also when XGen hair looks CG, clumps look uniform, the scalp shows through, or an XGen script fails.

日本語の概要は準備中です。原文の説明を表示しています。

Use when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games. Also covers the Essentials hair node assets (Interpolate, Clump, Curl, Frizz, Noise, Trim), density masks, bald spots, parting lines, strand shading in Cycles or EEVEE, and slow grooms. Use it too when a hair script misbehaves headless, for example stale modifier inputs or curve sculpt brushes that do nothing.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting

日本語の概要は準備中です。原文の説明を表示しています。

Hair and fur grooming in Blender using curves, particle hair, geometry nodes, and game hair-card workflows. Use for characters, creatures, and real-time hair cards via MCP.

日本語の概要は準備中です。原文の説明を表示しています。

Same reverse-thinking method as dh:rt-ica (see dh:rt-ica or dh-glossary for the definition), but localizes any MISSING input to the affected task only, as a non-blocking information-completeness pre-pass before task decomposition and plan generation. Use when grooming backlog items, generating plans, decomposing tasks under uncertainty, or working in brownfield and refactor scenarios. Produces completeness summary (APPROVED-FOR-PLANNING, APPROVED-WITH-GAPS, or BLOCKED-FOR-PLANNING), missing input report with dependency mapping, required unblock actions, and planning annotations for downstream tasks. Use dh:rt-ica instead at the S2 implementation gate where missing inputs must halt execution.

日本語の概要は準備中です。原文の説明を表示しています。

Transitions a GitHub milestone from planning to active execution. Use when the team is ready to begin a sprint or release cycle — bulk-transitions open issue labels from status:needs-grooming to status:in-progress, updates GitHub Projects V2 Status to In Progress, and confirms before applying changes. Requires milestone number as argument. Use after /group-items-to-milestone.

日本語の概要は準備中です。原文の説明を表示しています。

Expert product management guidance for day-to-day PM work. Use when creating roadmaps, prioritizing features, managing stakeholders, planning sprints, grooming backlogs, scoping features, planning releases, defining OKRs, managing technical debt, or coordinating go-to-market. Covers RICE, ICE, MoSCoW frameworks, cross-functional collaboration, and product metrics.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Conduct structured insect behavior observations using sampling protocols, ethogram categories, event recording, interaction logging, environmental context, and summary analysis. Covers focal animal sampling, scan sampling, all-occurrences sampling, and instantaneous sampling methods. Defines a standard insect ethogram with locomotion, feeding, grooming, mating, defense, communication, and rest categories. Includes timestamped event recording, intraspecific and interspecific interaction logging, environmental covariate documentation, and time budget analysis. Use when studying insect behavior for ecological research, documenting behavioral repertoires for a species, observing pollinator activity or predator-prey dynamics, or supporting conservation assessments with behavioral data.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

ที่ปรึกษาเลี้ยงสัตว์เลี้ยง (หมา/แมว/exotic) — nutrition, training, health check, grooming, pet travel พร้อมคำแนะนำเฉพาะสภาพอากาศไทย

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when you need to validate a PBI against Definition of Ready before grooming.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Azure Boards Deep — deep Azure Boards management covering work items, sprints, backlogs, queries, and team velocity analytics. Use when performing deep audits of Azure DevOps Boards, analyzing sprint health, reviewing backlog grooming, or assessing team capacity and velocity across Azure DevOps projects.

日本語の概要は準備中です。原文の説明を表示しています。

Use when planning a Humans sprint — grooming the backlog into work batches and publishing the Peter-approved subset as a cloud sprint tracking issue. Runs locally with gh access to both repos.

日本語の概要は準備中です。原文の説明を表示しています。

Permanent-delete grooming for leftover Docker builds, agent worktrees, and .next caches. Use when creating or finishing a git worktree, after a local docker build, when the disk is full, or when /tmp or .wt trees were left behind.

日本語の概要は準備中です。原文の説明を表示しています。