「retrospective」の検索結果

Weekly business retrospective. Reads all snapshots, learnings, skill-usage telemetry, and (if provided) revenue data from the past week. Outputs: what got decided, what shipped, what's stalled, skill activity, suggested next focus. Surfaces unused skills as activation prompts. Use at end of week or end of sprint. Triggered by: 'weekly retro', 'business retro', 'what did we ship', 'how's the week going', '周复盘', '业务回顾', '本周复盘'.

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

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics. Per-person breakdowns with praise and growth areas. Modes: default 7d, 24h, 14d, 30d, compare, global cross-project. Shipping streaks and tweetable summary.

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

Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting

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

Scope management for legal matters — baseline capture, in-flight change control, OOS documentation, and scope retrospective. Use when asked to review scoping assumptions, assess whether work is in or out of scope, draft a scope change notice, track scope changes, prepare an OOS justification, run an OOS report, prepare a scope call agenda, or review what changed on a matter. Trigger on: 'scope change', 'out of scope', 'OOS', 'scope creep', 'is this in scope', 'the client wants us to also', 'additional work', 'scope review', 'what changed from the original scope', 'we need to revisit the quote', 'the budget assumed', 'OOS report', 'scope call with the client', 'run a scope report'.

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

Retrospective on past token and prediction market picks - what hit, what flopped, what the score is

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

Review affiliate campaign results and improve strategy. Triggers on: "review my results", "what went wrong", "how to improve conversions", "analyze my campaign", "affiliate retrospective", "why am I not converting", "improve my strategy", "what should I change", "campaign review", "optimize my approach", "learn from my results", "post-mortem on my campaign".

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

Dung khi da co huong launch va can QUY TRINH chay cho khong vo tran — timeline T-30 den D+7, checklist tung bo phan content, design, ads, sales, CSKH; war-room ngay launch, escalation matrix va tieu chi roll-back. Kich hoat khi user nhac 'launch playbook', 'quy trinh launch', 'checklist launch', 'war room', 'sap launch ma so sot', 'ai lam gi trong ngay launch', 'SOP ra mat', 'lan truoc launch bi loan'. Khong dung cho — chon phan khuc va thong diep de ra thi truong thi dung skill 59-go-to-market; tong ket bai hoc sau khi launch xong thi dung skill 63-campaign-retrospective; su co truyen thong bung phat thi dung skill 66-crisis-playbook.

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

Dung khi thuong hieu DANG bi tan cong hoac campaign gay phan ung xau — phan loai 5 cap L1 den L5, quy trinh 4 gio dau, template phan hoi tung tinh huong, ai duoc phat ngon, danh sach TUYET DOI khong lam va post-mortem sau khung hoang. Kich hoat khi user nhac 'khung hoang truyen thong', 'crisis', 'bi bao xau', 'review 1 sao lan rong', 'content gay phan ung', 'khach to tren mang', 'dang bi tay chay', 'phai xin loi the nao'. Khong dung cho — theo doi va canh bao som khi chua co su co thi dung skill 15-social-listening; campaign kem ve so lieu chu khong phai su co thi dung skill 03-danh-gia-hieu-suat; tong ket bai hoc sau khi da yen thi dung skill 63-campaign-retrospective.

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

Dung khi can danh gia CON NGUOI trong team marketing dua tren du lieu — KPI scorecard theo tung vai tro writer, designer, media buyer; diem manh co vi du that; diem can cai thien; development plan 30-90 ngay; rubric cham 1-5. Kich hoat khi user nhac 'danh gia nhan vien', 'performance review', 'review nhan su', '1:1 review thang', 'nguoi nay lam duoc khong', 'co nen tang luong khong', 'feedback cho team member'. Khong dung cho — tong ket mot campaign thay vi con nguoi thi dung skill 63-campaign-retrospective; duyet chat luong mot output cu the thi dung skill 62-marketing-review; giao viec va dat deadline thi dung skill 64-team-brief.

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

Use when a leader evaluates a marketing TEAM MEMBER using data — a KPI scorecard by role, strengths with real examples, areas to improve stated as observable behavior, a 30 and 90 day development plan, and a 1-5 rating rubric. Trigger on 'performance review for my marketer', 'evaluate a team member', 'monthly 1:1 review', 'feedback for my content writer', 'development plan for an employee', 'is this person underperforming'. Also use when the user is unhappy with someone and cannot articulate why. Not for — evaluating a campaign rather than a person, see `63-campaign-retrospective-global`; reviewing one piece of output, see `62-marketing-review-global`; scoring an external vendor, see `67-agency-vendor-brief-global`.

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

Use when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room, an escalation matrix, and roll-back criteria. Trigger on 'launch playbook', 'launch checklist', 'launch day plan', 'launch SOP', 'war room', 'we launch in two weeks and nothing is organized'. Also use when a GTM strategy exists and nobody knows who does what on the day. Not for — the strategy and beachhead choice, see `59-go-to-market-global`; the campaign brief, see `02-campaign-brief-global`; the post-launch review, see `63-campaign-retrospective-global`; a live crisis, see `66-crisis-playbook-global`.

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

Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for — monitoring before anything blows up, see `15-social-listening-global`; diagnosing weak performance numbers, see `03-performance-eval-global`; the routine post-campaign review, see `63-campaign-retrospective-global`.

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

Append a learning entry to AGENTS_LEARNING.md when an AI agent makes a mistake. Auto-activates after a pre-write audit auto-fix, a retrospective correction loop, or a mid-session user correction. Use when: mistake, wrong, correction, my bad, agent error, learning log.

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

Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

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

Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.

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

Process: retrospectives, session handoff, pair programming, subagent-driven development, condition-based waiting.

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

Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.

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

Learn from public breach disclosures — extract the audit question each one implies and check your own stack. Capital One IMDS abuse, LastPass vault exfiltration, Okta Lapsus$, Snowflake credential reuse, MOVEit, SolarWinds, Equifax, Target POS, Codecov, Uber, Twilio — what would you check now if your boss said 'could that happen to us?' Use when the user mentions 'breach analysis,' 'lessons learned,' 'security postmortem,' 'breach patterns,' 'breach lessons,' 'has this happened to us,' 'apply breach lessons,' 'preempt breaches,' 'security retrospective,' 'real-world security incidents,' or wants to harden against known attacker playbooks.

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

Generates LESSONS.md files capturing institutional knowledge and failures. Use when closing out projects or investigations.

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

Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection. Use for research storytelling, contribution framing, paper comparison, figure planning, or research retrospectives. Not an acceptance predictor or a routine grammar/citation formatter.

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

セッション終了時に自己改善Issueを自動生成するスキル。 「振り返りIssue出して」「レトロスペクティブ」「改善点をIssueにして」等のリクエストで発動。

Evaluates and improves skills, agents, commands, and hooks after a workflow slice. Use when execution felt slow, confusing, repetitive, or fragile.

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

Detect friction signals; graduate patterns into rules. Use for session retrospectives.

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

Generates structured OKR plans (Objectives and Key Results) for teams and companies following Google/Intel methodology. Takes company goals, team function, quarter, and current metrics to produce a comprehensive okr-plan.md with objectives, key results, scoring criteria, alignment mapping, tracking cadence, and retrospective templates.

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