264 件 ・ 関連度順
概要と使いどころ
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
日本語の概要は準備中です。原文の説明を表示しています。
设计里程碑和交付门禁时使用。适用于阶段评审、上线前检查、重要节点验收。优先使用 Stage-Gate 方法 + 验收标准 + 强制门禁清单。
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously work a `.pm` workstream to completion — pick the next pending milestone, implement every task end to end, /ship it, then move to the next until none remain. Use when the user asks to "loop", drain, or work through a whole workstream's backlog (e.g. `/loop-worker w1`). Sequential, not interval-based; for a timed poll use /loop.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when one milestone is too large for a single specification or plan and must ship as several ordered stages across sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Review execution against the frozen Execution Contract, produce Evidence/Gaps, and decide pass or unfreeze. Use after ac-execute or at milestone acceptance gates.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a project charter that defines scope, stakeholders, success criteria, and initial risk register. Covers problem statement, RACI matrix, milestone planning, and scope boundaries for both agile and classic methodologies. Use when kicking off a new project or initiative, formalizing scope after an informal start, aligning stakeholders before detailed planning begins, or transitioning from discovery to active project work.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant incident or success, at a quarterly review of ongoing processes, or before starting a similar project to capture lessons learned.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to review learning progress after a milestone. Not for engineering retrospectives, use engineering-retrospective. For agent-environment ones, use agent-environment-retrospective.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to create a multi-session learning plan. Returns a milestoned plan, practice, and review rubric. Don't use for tasks that require source or remote-system changes.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations. Use when someone wants word-of-mouth growth, viral loops, invite programs, or says 'referral', 'viral loop', 'word of mouth', 'invite program', 'refer a friend', 'growth loop', 'referral incentive', 'affiliate program', 'ambassador program', 'get users to invite friends', or 'organic growth'. Even casual mentions like 'how do I get my users to spread the word' or 'can users invite others' should trigger this. Includes anti-fraud measures and copy templates for both referrer and referee. Use this whenever user-driven acquisition or viral mechanics are discussed.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Convert scattered progress notes, RAID changes, and milestone movement into a clean weekly or biweekly status update. Use when the work is routine status packaging or steering prep. Do not use for project governance design, root cause analysis, or deep portfolio risk assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Create practical role-specific onboarding checklists with owners, timing, access needs, and first-week milestones. Use for new hire, contractor, client, or team onboarding.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。
Refresh tracked pre-launch stablecoin milestones, dates, launch phases, featured content, and promotion evidence. Use for the recurring upcoming-assets review.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.
日本語の概要は準備中です。原文の説明を表示しています。