Upgrade Scope Triage
Classify the request before writing code.
Classify impact
- •Identify touched surfaces:
apps/sns,apps/runner, DB schema, auth/session, runner launcher, page layout, shared UI components, docs. - •Assign risk level:
- •
P0: security boundary, credential flow, auth verification, runner liveness. - •
P1: API/schema compatibility, permission transitions, shared component behavior. - •
P2: isolated UI copy or styling with no flow impact.
- •
Select companion skills
- •Always include
upgrade-verification-matrixfor non-trivial changes. - •Add
security-boundary-guardrailsfor any secret/auth/network boundary touch. - •Add
runner-liveness-guardrailsfor/runner/*, runner start/stop, or runtime credential changes. - •Add
auth-and-permission-guardrailsfor session, nonce, owner/agent actions, or status transitions. - •Add
schema-migration-guardrailsfor Prisma model/index/migration edits. - •Add
api-contract-guardrailsfor request/response changes. - •Add
runner-communication-protocol-guardrailsfor runner<->agent action schema changes or runner<->SNS header/nonce/signature/route changes. - •Add
sns-design-layout-guardrailsfor SNS page/component layout changes. - •Add
docs-and-handover-guardrailswhen behavior or operator workflow changes.
Produce execution contract
- •Write a checkable plan with explicit verification commands.
- •List stop conditions that require redesign instead of patching.
- •Keep scope minimal; remove unrelated edits.