Menu
Reflect phase — capture what was learned as durable, grounded notes: surprises, follow-on tickets, and method tweaks.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | reflect-notes |
| description | Reflect phase — capture what was learned as durable, grounded notes: surprises, follow-on tickets, and method tweaks. |
You are in the reflect phase of Coding Mode. The work is done; capture what the next session (human or agent) would want to know, so the lesson is not relearned. Keep it short and concrete.
Capture, only where there is something real:
AS-NNN-shaped ticket title, not a vague TODO.Every note must anchor to a concrete file, symbol, or ticket. A reflection with no anchor teaches nothing next time. Never write "went well" or "learned a lot".
Good (grounded):
skill.loadFS() already handled embed.FS via fs.FS, so AS-074
needed only a thin LoadFS() wrapper, not a new parser.coding-mode/skills blocks to the active phase in the projection.Bad (rejected — no anchor):
Start an Agent Smith ticket the right way — read the ticket, its dependencies, the PRD Decision Log, and the affected architecture/docs before editing. Use when picking up an AS-NNN ticket, deciding what to work on next, or before touching code for a backlog item. Triggers: "work on AS-", "start a ticket", "implement the ticket", "what should I work on next", "pick a ticket".
Agent Smith pull-request lifecycle — open a PR, subscribe to activity, reply to and resolve every review thread, handle the Gemini/Copilot review order, and auto-merge when clean. Use when work on a branch is committed and pushed, when a PR exists for the branch, or when handling review comments or CI on a PR. Triggers: "open a PR", "PR review", "review comment", "CI failed on the PR", "merge the PR", "is the PR ready".
Reflect phase — produce the three success artifacts (a measurable success metric, an instrumentation diff, a check-back ticket draft) without ever reading shipped-app runtime data.
Analyse phase — trace what else the change touches: callers, shared state, persisted formats, and cross-package contracts.
Analyse phase — interrogate the request for missing requirements, unstated assumptions, and unhandled cases before any code is written.
Plan phase — pressure-test the proposed plan: smallest viable change, ordering, and the test that will prove it.