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

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

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

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.

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

• Review new and spiking errors every hour
• Avoid duplicate GitHub issues for Sentry errors
• Create issues with stack traces and impact details

Draft and refine Linear or Superset tickets using a consistent structure for context, references, and implementation notes. Clarify the desired outcome, record where requests came from, and add code details when enough context is available.

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

• Draft a bug report or feature request
• Standardize ticket structure across a team
• Record feedback sources and links

Organize open GitHub issues and pull requests using the gh CLI, GitHub's command-line tool. Identifies resolved issues and pending fixes, estimates priorities and change sizes locally, and proposes closures, links, reviews, or merges for approval.

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

• Clean up resolved issues left open
• Link issues to pull requests with pending fixes
• Estimate priorities and change sizes for outstanding work

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.

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

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

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

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.

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

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.

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

Adopt a virtual Persian cat at animalhouse.ai. High maintenance. Rewards grooming. Hates being rushed. Feeding every 5 hours. Uncommon tier cat.

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