'milestone' 검색 결과

Open, classify, and escalate support cases with Salesforce Technical Support via the Help portal: choosing severity, engaging Premier Success, the Escalate to Technical Support Management path, tracking incidents on the Trust site. NOT for escalating your own org's cases after N hours - use admin/escalation-rules. NOT for SLA milestone timers and entitlement processes - use admin/entitlements-and-milestones.

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

Configure and troubleshoot Salesforce Case Escalation Rules: time-based escalation entries, business hours configuration, escalation actions (email alerts and reassignment), and diagnosing why cases are not escalating. Covers the EscalationRules metadata shape, businessHoursSource and escalationStartTime semantics, staged escalationAction thresholds, deploy-inactive parallel-run cutover, and monitoring escalated cases. Trigger keywords: escalation rule, case not escalating, SLA breach notification, escalate after X hours, reassign case automatically, IsEscalated. NOT for SLA milestone timers — use admin/entitlements-and-milestones. NOT for case routing on creation — use admin/assignment-rules. NOT for the calendar itself — use admin/business-hours-and-holidays.

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

Configure Salesforce Billing (blng__ managed package) billing schedules, invoice plans, billing policies, and billing treatments on activated Orders. Triggers: 'billing schedule not generating invoices', 'blng__BillingSchedule__c missing after order activation', 'in-advance vs in-arrears billing', 'milestone billing', 'invoice run not picking up order products', 'evergreen billing setup', 'billing treatment configuration'. NOT for revenue schedules, GL transactions and ASC 606 - use admin/revenue-recognition-requirements. NOT for native Revenue Cloud (RLM) BillingSchedule objects - use data/revenue-cloud-data-model.

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

Configuring Salesforce case management: case queues, assignment rules, escalation rules, auto-response rules, Email-to-Case, Web-to-Case, case teams, entitlements, and milestones. Use when setting up or troubleshooting the Service Cloud case handling layer. Trigger keywords: email-to-case, web-to-case, escalation rules, case teams, entitlements, milestones, auto-response, case queue. NOT for Standard vs On-Demand Email-to-Case and routing-address setup — use admin/email-to-case-configuration. NOT for routing case work items to agents — use admin/omni-channel-routing-setup.

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

[Planning] Use ONLY when the user explicitly requests a product roadmap, roadmap update or milestone selection: outcome milestones, MVP scope, non-goals, risks, evidence gates.

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

Turns a schedule extract (milestone list or planning tool export) and the period's status notes into a DRAFT plain-language slip explanation: which milestones and activities slipped and by how many working days, arithmetic shown, why per the notes as verbatim fragments with source and date, what each slip pushes next per the extract, and the decision each slip needs framed as a question with the options the notes propose and the owner the governance documents name, every missing fact marked UNKNOWN. Use when the user asks to "explain the schedule slip", "what slipped this month and why", "write the schedule commentary for the steering pack", "put the delay in plain language for the sponsor" or "what decisions do these slips need". Do not use for the weekly status report, use project-status-tracker instead; for cost variances, use budget-variance-explainer; for one sprint's carry-over, use sprint-review-summary. Drafts for human review; never approves, authorises or signs off.

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

Builds a self-contained single-file HTML project dashboard (status banner, milestones table, risks heat list, decisions log, links) from the project tracker files the user attaches, pastes or holds in configured knowledge sources, and returns the complete HTML source in chat ready to save as dashboard-project-date.html. Use when the user asks to "build a dashboard for this project", "make a status page I can pin in the team channel", "give me an HTML overview of milestones, risks and decisions", "refresh the project dashboard from the tracker" or "turn these tracker files into a one-page visual summary". Do not use for creating or updating the tracker files or for the written weekly status report, use project-status-tracker instead. Drafts for human review; never approves, authorises or signs off.

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

Assemble a full multi-tier content episode from a milestone session's hot context and publish it out of band, ahead of the nightly schedule: teasers go to chats right after one approval, the rest follow by topology. Triggers: "/wow", "this is a milestone", "this session is great, tell everyone".

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

Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).

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

Runs the test-first build loop (spec, plan, thin slices, failing test first, verify, commit) for a Godot 4 game in GDScript or C# first; in a TypeScript, Python or other repo when test-first, slices or a reproduce-first fix is asked for. Trigger to build or add a game feature, mechanic, stat, system or milestone, even when told to test later; to turn a spec or grill record into slices; to fix a game bug from a reproduction, one hypothesis at a time; on "write the test first", "what's the next slice", "is this slice done" or "is this milestone ready to exit"; or say slicesmith (spec, plan, slice, fix, exit). Run proof and gate rulings are godotsmith's; diff review a review tool's; repo maps researchscribe's; art pixelsmith's; audio soundsmith's; interviews grillwright's; fan-out dispatchwright's.

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

Generate a comprehensive project summary from milestone artifacts for team onboarding and review

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

Archive completed milestone and prepare for next version

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

Start a new milestone cycle — update PROJECT.md and route to requirements

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

Create phases to close all gaps identified by milestone audit

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

Audit milestone completion against original intent before archiving

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

실제 브라우저에서 웹 페이지의 로딩 시간과 전송량을 측정합니다. 기준값 및 코드 변경 전후 결과를 비교해 속도 저하를 찾고 장기적인 성능 추이를 확인합니다.

• 변경 전 성능 기준값을 저장할 때
• 코드 변경 후 페이지 속도 확인
• 느린 리소스와 큰 전송량 조사

신입 직원의 온보딩 계획을 한 페이지 HTML로 정리합니다. 첫날과 첫 주 일정, 상사와 동료 안내, 30·60·90일 목표, 참고 자료와 완료 조건을 모읍니다.

• 신입 직원의 첫 주 일정 준비
• 30·60·90일 목표 설정
• 상사·온보딩 동료·참고 자료 공유

Coordinate 15 agents implementing claude-flow v3 across security, core systems, integration, testing, performance, and release work. Provides role assignments, task dependencies, GitHub tracking examples, and a four-phase schedule spanning 14 weeks.

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

• Assign claude-flow v3 work across 15 agents
• Run tasks in parallel while respecting dependencies
• Track milestones and progress through GitHub issues

Investigate a GitHub project through repository data and web sources, then produce a Markdown report covering its development history, technical structure, activity metrics, and alternatives, with citations and diagrams where useful.

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

• Investigating an open source project's technical structure
• Reconstructing development milestones from commits and releases
• Comparing a project with competing alternatives

Turn software development goals into manageable milestones with clear deliverables, dependencies, effort estimates, and success criteria. Use it to plan feature implementation, bug fixes, refactoring, performance improvements, and testing work.

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

• Planning OAuth2 authentication implementation
• Setting measurable database performance targets
• Breaking refactoring into incremental steps

Coordinate 15 agents implementing claude-flow v3 across security, core systems, integration, testing, performance, and release work. Provides role assignments, task dependencies, GitHub tracking examples, and a four-phase schedule spanning 14 weeks.

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

• Assign claude-flow v3 work across 15 agents
• Run tasks in parallel while respecting dependencies
• Track milestones and progress through GitHub issues

Build a marketing plan matched to a company's budget, team, and stage. Organize acquisition, first use, retention, referrals, and revenue into a 90-day roadmap and 12-month outlook, with owners, metrics, and tools in Notion-ready Markdown.

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

• Build a marketing roadmap for founders or investors
• Turn audit findings into a prioritized action plan
• Combine scattered marketing work into one plan

Turn supplied data or optional research into infographic drafts for reports, presentations, or social posts. Choose layouts and visual styles, generate PNG images, and use automated reviews to guide revisions while retaining review logs.

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

• Turning report statistics into an infographic
• Creating a timeline of project milestones
• Comparing product features visually

Build a tabbed project status page with goals, workstreams, owners, risks, and next actions. Publish it privately on claude.ai, then refresh the same URL from current sources and report what changed since the previous update.

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

• Sharing progress across multiple workstreams
• Tracking a software migration across several PRs
• Summarizing research or launch milestones