Root-Cause Debugging

Use DeepSeek to isolate the actual cause of a recurring technical failure, optimized for technical reasoning, coding and structured data.

Id: deepseek/root-cause-debugging · Status: Untested · FREE · Primary action: COPY / USE (not a live RUN claim).

What is this

A FREE DeepSeek resource. Open the full body below, copy it, and use it in a compatible AI surface you control.

What you can do now

Copy the complete instructions and fill in the placeholders ([GOAL], [INPUTS], [CONTEXT_OR_FILES], [CONSTRAINTS]) with your real material.

Full FREE body

Back to DeepSeek

Pack body is English. UI language controls translate chrome labels only.

You are handling **Root-Cause Debugging** in DeepSeek.

GOAL
[GOAL]

INPUTS
[INPUTS]

CONTEXT / ASSETS
[CONTEXT_OR_FILES]

CONSTRAINTS
[CONSTRAINTS]

EXECUTION
1. State the concrete objective and identify only missing information that would make execution unsafe or materially unreliable. Continue without blocking on optional details.
2. Inspect/analyze the supplied context before changing anything or drawing conclusions.
3. Define input/output contracts; identify edge cases; for structured data obey the requested schema and never invent missing values; validate the artifact.
4. Keep evidence, assumptions and unknowns separate. Never invent files, source facts, tool results, metrics, test results or completed actions.
5. Produce the actual artifact for this task; do not return generic advice about how to do it.
6. Verify the artifact against [CONSTRAINTS] and the requested outcome before returning it.
7. For this use case specifically, ensure the result can isolate the actual cause of a recurring technical failure and includes concrete validation or acceptance criteria.

TARGET-SPECIFIC RULE
For JSON, output only valid requested fields; represent missing values explicitly. Validate transformations against edge cases.

OUTPUT CONTRACT
RESULT: [completed | blocked]
DELIVERABLE: [DeepSeek prompt/API task specification with strict I/O, edge cases and validation]
VALIDATION: [checks performed / evidence used]
ASSUMPTIONS: [material assumptions only]
REMAINING: [none, or exact unresolved issue]

PLACEHOLDERS
[GOAL] desired outcome
[INPUTS] raw task material
[CONTEXT_OR_FILES] repository, documents, data, workflow context or API constraints
[CONSTRAINTS] scope, format, safety, compatibility, privacy, budget or policy constraints

Related FREE resources

Discovery links only — not a claim that BSV executes these together.

All Library DeepSeek shelf