cerredz Rubber Duck Debugging Reasoning Trace Medium
Goal
Use Rubber Duck Debugging to answer the user's question through explaining a problem aloud step-by-step to an inanimate listener to discover the solution, not through a generic checklist or interchangeable trace. The trace should explain a problem aloud step-by-step to an inanimate listener until the act of articulation reveals the flaw or solution, so the visible reasoning follows the same path the strategy is known for. The goal is to create a public scratchpad that a reviewer can audit without exposing hidden private chain-of-thought. Center the scratchpad on subquestions, assumptions, evidence, contrasts, tests, intermediate conclusions, and implications, because those artifacts make rubber duck debugging useful rather than decorative. Preserve the user's domain, constraints, definitions, and evidence standards so the trace stays tied to the actual task. Keep uncertainty visible by naming weak assumptions, missing evidence, rival interpretations, and confidence changes as they arise. Write the result to root memory/{question_name}.md so the reasoning trace becomes a durable project artifact.
Instructions
Derive {question_name} from the user's actual question by lowercasing it, replacing non-alphanumeric runs with hyphens, trimming extra hyphens, and using reasoning-trace if no safe name remains. Create the root memory directory when needed, then write or replace memory/{question_name}.md with this trace. Start the file with the question, selected strategy, scale note, source constraints, and a brief statement of what the trace will inspect. Build the scratchpad by repeatedly applying the Rubber Duck Debugging move: explain a problem aloud step-by-step to an inanimate listener until the act of articulation reveals the flaw or solution. Use a medium trace, usually around 100 numbered lines, and give each major reasoning step room to be inspected. Prefer concise public reasoning artifacts over hidden deliberation, and make every numbered item contribute a question, observation, test, comparison, inference, or synthesis. End the file with a synthesis and final answer that follow from the trace, including any important uncertainty that remains.
Background Information About The Reasoning Strategy
Rubber Duck Debugging is a reasoning strategy for turning a question into an auditable public trace instead of an unstructured opinion. It should give the output document a visible sequence of decisions, tests, and intermediate conclusions, so the reader can see how the answer was reached without exposing hidden private chain-of-thought. Use it when the problem benefits from the core move "explain a problem aloud step-by-step to an inanimate listener until the act of articulation reveals the flaw or solution" and when the final answer needs evidence, assumptions, and uncertainty kept in view. A strong Rubber Duck Debugging trace lets that move determine the order and granularity of the scratchpad, then compresses the result into a concise final answer.
Algorithm for the output document:
- Restate the user's question, constraints, and evidence standard, then derive the subquestions or working items that Rubber Duck Debugging needs to inspect.
- Apply the core move explicitly: explain a problem aloud step-by-step to an inanimate listener until the act of articulation reveals the flaw or solution.
- For each subquestion, case, option, hypothesis, or criterion the move creates, write numbered public reasoning items that answer it before advancing.
- Record assumptions, missing evidence, disconfirming signals, and confidence changes where they affect the analysis.
- Synthesize the completed trace into the final answer, showing how the conclusion follows from Rubber Duck Debugging rather than from a generic summary.
Output Information
Write the scratchpad as Markdown in root memory/{question_name}.md before responding to the user. Include this scale note near the top of the file: "Scale: medium - aim for around 100 numbered lines, or roughly 2,000 to 3,500 tokens, while preserving enough detail for review." Use numbered scratchpad items for scanability, but treat the number target as approximate and subordinate to usefulness. Keep the scratchpad public, inspectable, and concise enough per line that the structure remains easy to review. After writing the file, respond with the path, selected strategy, scale note, and final answer summary.
Specify Files And Length And Structure Of Output
Write the artifact to memory/{question_name}.md at the repository root, using the literal memory directory name. Structure the file with the sections Question, Strategy, Scale, Scratchpad, Synthesis, and Final Answer. The Scratchpad section should target around 100 numbered lines or roughly 2,000 to 3,500 tokens of public scratchpad detail, adjusted reasonably for very small or unusually broad questions. Use subsections inside Scratchpad when the trace becomes long enough that phases, branches, hypotheses, cases, or criteria would improve readability. If the user supplies a domain format, evidence source, or output constraint, preserve it inside this structure while keeping the medium scale approximate.