메뉴
Analyse phase — trace what else the change touches: callers, shared state, persisted formats, and cross-package contracts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | find-side-effects |
| description | Analyse phase — trace what else the change touches: callers, shared state, persisted formats, and cross-package contracts. |
You are in the analyse phase of Coding Mode. Before planning the change, trace its blast radius — what else moves when this code moves.
Look for, and report only what the code actually shows:
docs/architecture/package-contracts.md)?Every side effect must name the concrete site — the calling file/function, the shared symbol, the persisted field, or the contract test. No anchor, no finding. Never emit generic advice like "watch out for regressions".
Good (grounded):
mode.DefaultPhases() order also shifts mode.NextPhase() results;
internal/mode/mode_test.go pins the old order and will fail.schema.Block.Ext, read
by memory.Source() — keep the key namespaced so AS-082 imports still parse.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 — 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.
Reflect phase — capture what was learned as durable, grounded notes: surprises, follow-on tickets, and method tweaks.