Run any Skill in Manus with one click

developer-retro-capture

Stars30

Forks1

UpdatedJuly 10, 2026 at 08:52

Capture meaningful recognition mismatches, false completion claims, and verification misses into tmp/RETRO.md for rawsql-ts developer work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mk3008

mk3008/rawsql-ts

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	developer-retro-capture
description	Capture meaningful recognition mismatches, false completion claims, and verification misses into tmp/RETRO.md for rawsql-ts developer work.

Retro Capture

Use this skill when a rawsql-ts developer task hits a recognition mismatch, misleading completion claim, verification miss, or similar workflow mistake that should influence later reporting or PR readiness.

Use It For

Deciding whether an incident is important enough to record in tmp/RETRO.md.
Turning a vague "something went wrong" moment into a reusable retro entry.
Separating task-specific reflection from durable rule changes.
Identifying whether the prevention should become guidance, a test, a script, or a Codex skill.
Recording whether the item should block PR handoff.

Workflow

Decide whether the incident materially affected rework, verification, or trust in a completion claim.
If yes, add or update an entry in tmp/RETRO.md.
State what happened and why it happened in concrete terms.
Record the impact on the task, report, or review path.
Decide whether the prevention is mechanizable.
If the prevention is reusable, name the likely promotion target such as AGENTS.md, .codex/guidance/*.md, .codex/agents/*.toml, tests, scripts, or another Codex skill.
Set PR gate status to open, resolved, or accepted defer.
If the status is accepted defer, record the remaining risk, owner, and follow-up path.

Output Shape

Title
What happened
Why it happened
Impact
Mechanizable prevention
Promote to durable rule?
PR gate status
Resolution / follow-up
Defer rationale, when needed

Constraints

Use tmp/RETRO.md for task-specific reflection, not AGENTS.md.
Do not create retro entries for trivial typos or harmless corrections.
Do not mark an item resolved unless the reporting or workflow risk is actually closed.
Prefer open over accepted defer when the tradeoff is not explicit.

More from this repository

same repository

rawsql-task-orchestrator

mk3008/rawsql-ts

Assess and dispatch rawsql-ts developer tasks by tracing repository impact, concept and package boundaries, verification cost, difficulty, risk, model and reasoning effort, and Codex worktree requirements. Use when a new rawsql-ts issue, bug, feature, refactor, investigation, CI failure, review request, migration, or documentation change must be analyzed before action or handed to a new Codex task.

2026-07-1230

developer-attainment-reporting

mk3008/rawsql-ts

Report per-item attainment for completed rawsql-ts developer work.

2026-07-1030

package-spec-review

mk3008/rawsql-ts

Review tracked rawsql-ts package-level Scope, Test Policy, Authority Model, Technology Policy, review-plan, and generated review views before package implementation or documentation changes. Use only when those package-owned artifacts exist in the checked-out base.

2026-07-1030

developer-pr-readiness

mk3008/rawsql-ts

Prepare rawsql-ts pull requests with the repository PR template and local readiness gate so required merge, CLI migration, and scaffold proof sections are not missed.

2026-07-1030

developer-pre-pr-retro-gate

mk3008/rawsql-ts

Check tmp/RETRO.md before PR or human review so unresolved retro items do not slip through rawsql-ts developer workflow.

2026-07-1030

developer-self-review

mk3008/rawsql-ts

Run two-cycle self-review and triage before presenting rawsql-ts developer work to a human reviewer or requester.

2026-07-1030

name	developer-retro-capture
description	Capture meaningful recognition mismatches, false completion claims, and verification misses into tmp/RETRO.md for rawsql-ts developer work.

Retro Capture

Use It For

Deciding whether an incident is important enough to record in tmp/RETRO.md.
Turning a vague "something went wrong" moment into a reusable retro entry.
Separating task-specific reflection from durable rule changes.
Identifying whether the prevention should become guidance, a test, a script, or a Codex skill.
Recording whether the item should block PR handoff.

Workflow

Decide whether the incident materially affected rework, verification, or trust in a completion claim.
If yes, add or update an entry in tmp/RETRO.md.
State what happened and why it happened in concrete terms.
Record the impact on the task, report, or review path.
Decide whether the prevention is mechanizable.
If the prevention is reusable, name the likely promotion target such as AGENTS.md, .codex/guidance/*.md, .codex/agents/*.toml, tests, scripts, or another Codex skill.
Set PR gate status to open, resolved, or accepted defer.
If the status is accepted defer, record the remaining risk, owner, and follow-up path.

Output Shape

Title
What happened
Why it happened
Impact
Mechanizable prevention
Promote to durable rule?
PR gate status
Resolution / follow-up
Defer rationale, when needed

Constraints

Use tmp/RETRO.md for task-specific reflection, not AGENTS.md.
Do not create retro entries for trivial typos or harmless corrections.
Do not mark an item resolved unless the reporting or workflow risk is actually closed.
Prefer open over accepted defer when the tradeoff is not explicit.