'milestone' 검색 결과

Use this skill to design, configure, and troubleshoot Salesforce Entitlement Management on Cases: entitlement processes, milestone definitions, recurrence types, milestone actions (success/warning/violation), business hours assignment, and entitlement templates. Covers the deployable EntitlementProcess / MilestoneType / EntitlementTemplate / EntitlementSettings metadata, signed timeLength time triggers, recurrenceType semantics, process versioning, and how a milestone actually completes. Trigger keywords: entitlement process, milestone, SLA timer, milestone tracker, first response SLA, time trigger, recursChained, CaseMilestone, EntitlementId, SlaProcess, stopped clock. NOT for SLA milestones on Field Service work orders — use admin/fsl-sla-configuration-requirements. NOT for time-based case escalation rules — use admin/escalation-rules. NOT for the business-hours calendar itself — use admin/business-hours-and-holidays.

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

Grooms a GitHub milestone for parallel execution — batch-grooms ungroomed items, assesses scope gaps, analyzes cross-item dependencies via Impact Radius overlap, builds conflict groups, assigns items to execution waves, and persists the dispatch plan via dispatch_create_plan MCP tool. Calls dispatch_wave_start per wave to register state. Use when preparing a milestone for /work-milestone execution. Pass the milestone number as the first argument. Requires milestone items assigned via /group-items-to-milestone.

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

Review a development milestone using sprint reports, feature status, bugs, and risks. Summarize completion, quality, and delivery pace, then recommend whether to proceed, proceed with conditions, or stop, with scope choices and action items.

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

• Reviewing progress before a milestone deadline
• Identifying blockers and quality risks
• Choosing features to protect or defer

Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.

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

• Checking completion criteria before archiving a milestone
• Reviewing coverage of milestone requirements
• Checking connections and user flows across phases

Close a completed development milestone by checking finished work, summarizing achievements, and archiving plans and requirements. Update project records and create a Git version tag to prepare for the next milestone.

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

• Archive plans and requirements for a completed version
• Summarize milestone achievements and change statistics
• Update project records before the next milestone

Assign backlog items to a GitHub milestone by bridging per-item files to GitHub Issues. Use when populating a sprint or release milestone, after create-milestone, or when a milestone number is specified with optional P0/P1/P2 or title filter. Creates missing GitHub Issues for selected P0/P1 items, assigns all selected items to the milestone, and updates Project V2 Status to Backlog.

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

Scope a milestone to a fixed time window with variable scope. Use when the user says "scope this milestone", "what fits in the sprint", "cut scope for the release", "define the MVP for this milestone", "we need to ship by [date] what do we cut", "shape the work to fit the cycle", or needs to make hard scope decisions under a time constraint - even if they don't explicitly say "milestone scoping". Based on "Shape Up" by Ryan Singer (appetite, shaping, betting table) and "The Art of Project Management" by Scott Berkun (milestones as forcing functions, scope as a variable).

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

Assigns a specified set of GitHub issues to a milestone, owners, or both. Checks that each target is an open issue, applies changes individually, and reports results with verification of milestone counts and selected issue details.

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

• Grouping issues into a release milestone
• Assigning owners to multiple issues
• Moving issues to a renamed or newly created milestone

Check new customer onboarding progress using HubSpot and Postgres, identify stalled or overdue milestones, and prepare emails tailored to the missed step. Notify the customer success manager while leaving customer communication to human review.

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

• Daily checks of new customer onboarding progress
• Drafting helpful emails for stalled setup steps
• Reminding customer success managers about overdue accounts

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

Turn completed milestone artifacts into one readable project summary. It explains what was built, how it works, and why decisions were made, helping new team members get started and supporting project reviews.

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

• Introducing a completed project to new team members
• Reviewing a milestone's deliverables and decisions
• Summarizing requirements and technical debt for handover

Organize accumulated planning folders by archiving phase directories from completed milestones. Review a preview of the proposed moves, then confirm to place those directories in a versioned milestone archive.

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

• Organize phase folders after a milestone is completed
• Review proposed archive moves before confirming
• Keep completed phase records in versioned archives

项目管理里程碑跟踪器（Project Milestone Tracker）——当用户要求代理在代码库/项目会话中规划、跟踪里程碑、记录承诺或事件、生成进度报告时使用。核心：三层里程碑规则（文件依据/客户提供/待确认）+ 原话+时间戳事件记录。Project milestone tracker: plan and track project milestones, record events with original text + timestamp, generate status reports, using a three-tier milestone rule (contract-sourced / stakeholder-stated / pending-confirmation).

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

Executes a groomed milestone with parallel kage-bunshin sessions in isolated worktrees. Use when a milestone has been groomed and /groom-milestone has produced a dispatch plan. Reads the dispatch plan, creates an integration branch, spawns one kage-bunshin (independent claude -p process) per wave item in its own worktree — each session is a full orchestrator with the Agent tool. Sequentially merges worktree branches, relays wave discoveries to subsequent waves, then lands the integration branch to main. Takes a milestone number as argument.

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

Use when assigning backlog items to a GitHub milestone. Args: {milestone-number} [P0|P1|P2|title-filter]. Uses backlog list to load items, shows items with GitHub Issue status, lets user select which to assign. Creates missing GitHub Issues for selected P0/P1 items, assigns all to the milestone, updates Project V2 Status to Backlog. Use after create-milestone to populate a sprint or release.

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

Close a completed GitHub milestone. Args: {milestone-number}. Audits open and closed issues, offers to carry forward open items to a new or existing milestone, closes the GitHub milestone, updates Project V2 Status to Done for closed issues, and generates a completion summary. Use when a sprint or release is finished and needs to be officially closed.

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

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.

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

Turn an approved decision into a 90-day execution plan with weekly milestones, named accountable owners, review meetings, dependencies, and risks. The plan preserves the decision’s success measures and criteria for stopping the work.

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

• Turning an approved decision into a quarterly plan
• Assigning owners and weekly milestones
• Setting progress reviews and stopping criteria

Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.

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

Close a completed GitHub milestone and generate a completion summary. Use when a sprint or release is finished and needs to be officially closed. Audits open and closed issues, offers to carry forward open items to a new or existing milestone, closes the milestone, updates Project V2 Status to Done for closed issues, and produces a completion report.

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

Creates a GitHub milestone on the current repository and returns its number for downstream use. Use when starting a new sprint, release, or theme grouping of backlog items. No args triggers guided intake (title, due date, description); 'quick {title}' skips to description only. Checks for duplicates before creating. Returns milestone number for /group-items-to-milestone.

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

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.

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

Close out a finished memex milestone slice by writing the handoff trail: update `docs/CONTINUE_HERE.md` §1 current-state and §3 next-slice, tick the `docs/ROADMAP.md` scoreboard (milestone header ✅ + version, `- [x]` items), confirm any new observation is logged (deferring to memex-observe), and propose the git tag plus a `MN Slice X:` commit subject. Use after you finish a milestone slice in the memex repo and before you commit/tag it, when handing the next slice to a fresh session, or whenever CONTINUE_HERE and ROADMAP have drifted behind what actually shipped.

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

Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.

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