القائمة
Run a sprint retrospective — gather data, analyze incidents, propose action items. Any agent can facilitate.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Compare two test262 result files to find exactly which tests changed status. Use after a test262 run shows unexpected pass count changes.
Compile a source file to WAT and analyze the output for codegen inefficiencies. Use after a codegen change to verify the output is clean, when investigating performance issues, or when creating optimization issues from real compiler output.
Write an implementation spec for a hard issue. Read compiler source, identify exact functions/lines, design the fix, document edge cases.
Quickly find which commit introduced a test262 regression using git bisect with automated test.
Atomically claim an issue for a developer (human or agent) via the cross-developer lock ref, so two devs never pick up the same task. Syncs with origin first, refuses if already claimed or already done on main, and pushes the claim immediately without touching main or triggering CI.
Create a new issue file from a test262 failure pattern. Includes smoke test, sample extraction, and proper frontmatter.
| name | sprint-retrospective |
| description | Run a sprint retrospective — gather data, analyze incidents, propose action items. Any agent can facilitate. |
Reviews the sprint and proposes process improvements.
# Sprint doc
cat plan/issues/sprints/{N}/sprint.md
# Diary entries from this sprint
cat plan/diary.md
# Git history for the sprint
git log --oneline --since="YYYY-MM-DD"
# Recently completed issues
rg -n '^status: done$' plan/issues/*.md | tail -20
# Task completion times (if available)
# Check TaskList or sprint doc task table
For each merge/task, assess:
What went well — with evidence:
What didn't go well — with root cause:
For each problem, propose a specific change to a specific file:
| # | Change | File | Priority |
|---|---|---|---|
| A1 | {what to change} | {which file} | HIGH/MEDIUM/LOW |
Each action item should be:
Write to plan/issues/sprints/{N}/sprint.md:
# Sprint {N} Retrospective
**Date**: YYYY-MM-DD
**Baseline**: {start numbers}
**Final**: {end numbers}
## What went well
- (with evidence)
## What didn't go well
### Incident 1: {title}
**What happened**: ...
**Root cause**: ...
**Impact**: ...
**Action item**: ...
## Action items summary
| # | Change | File | Priority |
...
## Proposed file edits
(exact diffs for each action item)
Share the retro with tech lead and user. Don't apply edits unilaterally — propose and wait for approval.
Message tech lead: "Sprint-{N} retro complete. {X} incidents, {Y} action items. Review at plan/issues/sprints/{N}/sprint.md"