「stones」の検索結果

Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.

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

Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.

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

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.

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

Structures IPO execution from organizational meeting through pricing with workstream coordination and timeline management. Use when managing IPOs, coordinating offering processes, or tracking ECM execution milestones.

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

Coordinates fundraising execution with PPM preparation, DDQ completion, legal documentation, and closing mechanics. Use when managing fund launches, coordinating formation processes, or tracking fundraising milestones.

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

Field identification of minerals and ores using hardness, streak, luster, cleavage, crystal habit, and simple chemical tests. Covers the systematic elimination methodology, Mohs scale application, and common ore indicators for precious metals, gemstones, and industrial minerals. Use when encountering an unknown rock or mineral specimen, when prospecting and assessing whether a site shows valuable mineral indicators, when distinguishing ore-bearing rock from barren rock in the field, or when building geological literacy through systematic observation.

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

Use when a user requests an engineering retrospective for a period. Not for agent-environment retrospectives: use agent-environment-retrospective. For learning milestones: use learning-retrospective.

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

Audit one bounded Proto UI collaboration-governance slice and route policy-determined drift toward reversible correction. Use across Issues, pull requests, Discussions, labels, milestones, Project, rules, permissions, or Actions. This evidence leaf is read-only; authorized corrections continue in their registered leaves.

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

30/60/90 Day Onboarding Plan — Day 1 setup, week 1 ramp, month 1 milestones, month 2 contributions, month 3 evaluation criteria

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

Break the spell of local productivity. Ask whether completing all open beads actually closes the gap to the project goal. Use at milestones or when busy agents feel directionally off.

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

Create structured employee onboarding plans using the 30-60-90 day framework aligned with SHRM best practices. Cover pre-boarding, Day 1, Week 1, and monthly milestones with task owners, success criteria, and buddy assignments. Use when hiring new employees or revamping the onboarding process.

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

Build multi-project RAID and RAG views for portfolios, programs, or cross-functional workstreams. Use when PMOs, program managers, or leaders need a real status picture across milestones, dependencies, owners, and escalations. Do not use for a single standup note, one issue ticket, or generic meeting minutes.

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

Create practical role-specific onboarding checklists with owners, timing, access needs, and first-week milestones. Use for new hire, contractor, client, or team onboarding.

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

Refresh tracked pre-launch stablecoin milestones, dates, launch phases, featured content, and promotion evidence. Use for the recurring upcoming-assets review.

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

Develop research proposals with solicitation alignment, reviewer-focused logic, evidence-bounded preliminary results, milestones, risks, and compelling figures. Use for federal, foundation, equipment, partnership, or internal research proposals.

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

Synthesize project documentation and codebase into comprehensive roadmap status, gaps analysis, and blockers. Use when assessing project health, identifying blockers, tracking progress, comparing plan vs reality, documenting risks, or planning next milestones. Triggers: "roadmap", "project status", "blockers", "risks", "progress", "next milestone", "gaps", "what's done".

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

Distinguishing aims, objectives, hypotheses, and milestones — the hierarchy that keeps proposals logically tight.

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

Read and manage software issues, tickets, projects, and planning data in Linear. Use to review sprints and cycles, identify ticket rollover and release blockers, and update issue status, assignees, priorities, and milestones through Linear's official MCP server.

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

Map a cloud system against NIST SP 800-53 Rev. 5 + FedRAMP baselines to produce the documentation an authorization needs — System Security Plan (SSP), Control Implementation Summary (CIS), Plan of Action and Milestones (POA&M), Continuous Monitoring (ConMon) Plan..

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

Build a velocity-based release roadmap with risk buffers. Use when the user says "release plan", "when will we ship", "plan the next release", "map sprints to milestones", "estimate our release date", "how many sprints until done", or wants to translate a backlog into a delivery timeline - even if they don't say "release planning". Based on "Agile Estimating and Planning" by Mike Cohn (velocity, story points, cone of uncertainty, risk buffers).

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

Write press releases for product launches, funding announcements, partnerships, executive hires, and milestones using the Inverted Pyramid (AP journalism) and Ogilvy on Headlines (David Ogilvy, Ogilvy on Advertising). The lede answers Who/What/When/Where/Why in 40 words or fewer. The headline selects the right audience and promises a specific benefit. Use when the user asks for a press release, media release, news announcement, PR for X, launch announcement, funding announcement, or "write a press release". Reads brand voice and positioning from knowledge/. For pitching it to a journalist, see pr-pitch-writer. For the customer story behind it, see case-study-writer.

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

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

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

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.

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