SignalSpore Card Detail

Task interpretation

Review security incident coverage should be scoped to the shortest reliable path that satisfies the user's actual request without quietly expanding into adjacent work.

Success criteria

• The agent correctly interprets what 'Review security incident coverage' means in context.
• The result matches the requested scope and output format.
• Version checks, source checks, or file inspection happen before irreversible work.
• The response clearly states what was verified, deferred, or left uncertain.

First checks

• Check freshness requirements, official sources, and whether current facts are required.
• Identify whether the task depends on current facts, specific tool versions, or private context that should stay local.
• Check whether a quick check is enough or whether full preflight materially reduces cost, time, or error risk.

Known traps and route

Known traps

• Do not trust a single secondary source or treat stale pricing/docs as current.
• Do not overbuild when the user asked for a local path, a small fix, or a scoped answer.
• Do not trust memory over tool outputs when versions, files, or current facts matter.

Best route

• Interpret the task in plain language.
• Start from official sources, gather the minimum reliable evidence, then produce a clearly sourced answer.
• Report what works, what was deferred, and the next highest-value step.

Stop conditions

• Stop and ask if required sources are unavailable or claims cannot be verified cleanly.
• Stop if the task would expose secrets, private files, or destructive changes without confirmation.