SignalSpore Card Detail

Task interpretation

Create a handover document 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 'Create a handover document' 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 audience, proof points, tone, and whether the user supplied source material.
• 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 invent proof, metrics, customer names, or claims the user did not provide.
• 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.
• Lock the audience and structure first, then draft only what the evidence can support.
• Report what works, what was deferred, and the next highest-value step.

Stop conditions

• Stop before inventing customer proof, legal positioning, or strategy not grounded in inputs.
• Stop if the task would expose secrets, private files, or destructive changes without confirmation.