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.
中文简介正在准备中。当前显示原文说明。
374 个 · 按相关度排序
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 a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
中文简介正在准备中。当前显示原文说明。
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".
中文简介正在准备中。当前显示原文说明。
Reflect reusable learnings into the current workspace / repository design and automation assets (.github/**, AGENTS.md, repo scripts/tasks). Not for ~/.copilot personal assets or a private skills repository. Use when running a workspace/repo retro. Detects whether a project folder exists and, if not, asks before creating one. Triggers on "retro workspace", "repo retro", "workspace cleanup", "ワークスペース知見反映".
中文简介正在准备中。当前显示原文说明。
Run a retro for personal global ~/.copilot assets and turn incident learnings into updates for copilot-instructions, instructions, skills, agents, and hooks. Not for workspace/repository assets or a private skills repository. Triggers on retro, retrospective, incident learning, error analysis, copilot setup, instructions update, インシデント, and 知見反映.
中文简介正在准备中。当前显示原文说明。
"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.".
中文简介正在准备中。当前显示原文说明。
Session retrospective. Runs after a workflow, coding session, or multi-step task completes. Analyzes what shipped, what failed, patterns observed, and growth opportunities. Generates a retro summary with per-step breakdowns, shipping streaks, and test health trends. Use after any significant session (>3 steps or >15 min). Proactively suggest when the user finishes a workflow, completes a feature, or says "let's review what we did." Also supports global retro across all projects.
中文简介正在准备中。当前显示原文说明。
Create a technical journey retrospective document from the current session's work. Use when the user asks for a retrospective, technical journey, dev blog post, session writeup, or wants to document what was built and why. Triggers on phrases like "write a retrospective", "create a journey doc", "document this session", "write a blog post about what we did".
中文简介正在准备中。当前显示原文说明。
Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.
中文简介正在准备中。当前显示原文说明。
Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.
中文简介正在准备中。当前显示原文说明。
Retrofit + OkHttpを使用したAPIクライアント実装のベストプラクティスを提供する。 「API実装」「APIクライアント」「Retrofit」「OkHttp」「ネットワーク」と言われたら使う。
中文简介正在准备中。当前显示原文说明。
Generate a backward-looking retrospective of vault activity (addressed callouts + Log entries) over a time window (1w / 1m / 1q), overlay with newsflow + earnings transcripts + price action, and rank trade ideas by the gap between official narrative and market reaction. Output is an immutable Research note. Use when user says "retro", "retrospective", "what did I do this week/month/quarter", "review activity against market", or "recommend trades from recent research".
中文简介正在准备中。当前显示原文说明。
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.
中文简介正在准备中。当前显示原文说明。
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)
中文简介正在准备中。当前显示原文说明。
Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.
中文简介正在准备中。当前显示原文说明。
审查现有代码的一个部分,从设计决策记录、实现惯例、缺失功能和技术选型四个方面整理问题,并推进计划、测试、修复及再次审查。
将功能提案、路线图、设计评审和复盘材料整理为辅助决策的HTML幻灯片。从八种主题中选择一种,统一所有页面的视觉风格,并支持横向翻页。
将识别网络钓鱼的迹象、练习及最初60秒的应对整理为员工培训HTML幻灯片,保留Windows 95风格,并按内容调整页数。
将爱好、收藏经历或游戏话题整理成HTML幻灯片,用深海军蓝背景、霓虹色和像素画风格,向朋友及同好讲述其中的故事。
将季度回顾或未来计划整理为蓝、橙、奶油色的复古演示文稿,以单个HTML文件呈现封面、三项重点、路线图与关键绩效指标,并提供动画切换和键盘翻页。
使用Hyperframes的HTML模板制作复古像素风格的三场景视频,替换标题、标签和配色,同时保留场景转换节奏及可重复的动画时序。
Find, generate, and prepare media for HyperFrames projects, saving assets locally with records for reuse. Covers images, music, voiceovers, transcription, captions, background removal, media edits, and visual treatments such as color correction or retro styling.
中文简介正在准备中。当前显示英语简介。
[omh] Team minutes, retros, and decision history to keep: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history. Use when the user says: operating-rhythm, operating rhythm, meeting minutes, meeting history, scrum record, sprint planning, sprint review, sprint retrospective.
中文简介正在准备中。当前显示原文说明。
Use when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a structured D1/W1/M1 retrospective — a per-channel actual-vs-target table (UTM-attributed own analytics as the truth column, platform self-reported numbers as reference, every figure labeled Measured / User-provided / Estimated), a 5-Whys chain on the single largest miss, keep / kill / change decisions per channel, 3-5 actionable learnings for the next launch, and an outcome snapshot submitted to the launch registry. Not for return math (CPA / ROI) — use roi-calculator; not for the stakeholder-facing report writeup — use report-generator; not for a metric deep-dive — use performance-analyzer. 发布复盘/渠道归因/5-Whys/keep-kill
中文简介正在准备中。当前显示原文说明。