A3 Problem Solving Reasoning Trace
Goal
Use A3 Problem Solving to answer the user's question through fitting problem analysis, root cause, corrective action, and follow-up on a single sheet, not through a generic checklist or interchangeable trace.
The trace should fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up, 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 a3 problem solving 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 A3 Problem Solving move: fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up.
Use a medium-depth trace by default, usually around 100 numbered lines, unless the user asks for a different depth.
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
A3 Problem Solving 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 "fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up" and when the final answer needs evidence, assumptions, and uncertainty kept in view.
A strong A3 Problem Solving 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 A3 Problem Solving needs to inspect.
- Apply the core move explicitly: fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up.
- 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 A3 Problem Solving 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: default - aim for around 100 numbered lines, or roughly 2,000 to 3,500 tokens, while adapting to the real complexity of the question."
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 default scale approximate.
1---2name: a3-problem-solving-trace3description: Use this skill when the user invokes /a3-problem-solving-trace or asks for a default public reasoning trace using A3 Problem Solving. The skill writes a durable scratchpad to root memory/{question_name}.md and uses A3 Problem Solving as the actual structure of the analysis. Treat the scale as a rough effort target rather than a fixed quota: around 100 numbered lines or roughly 2,000 to 3,500 tokens of public scratchpad detail. Use this skill when the user wants the answer shaped by fitting problem analysis, root cause, corrective action, and follow-up on a single sheet instead of a generic response.4---56# A3 Problem Solving Reasoning Trace78## Goal9Use A3 Problem Solving to answer the user's question through fitting problem analysis, root cause, corrective action, and follow-up on a single sheet, not through a generic checklist or interchangeable trace.10The trace should fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up, so the visible reasoning follows the same path the strategy is known for.11The goal is to create a public scratchpad that a reviewer can audit without exposing hidden private chain-of-thought.12Center the scratchpad on subquestions, assumptions, evidence, contrasts, tests, intermediate conclusions, and implications, because those artifacts make a3 problem solving useful rather than decorative.13Preserve the user's domain, constraints, definitions, and evidence standards so the trace stays tied to the actual task.14Keep uncertainty visible by naming weak assumptions, missing evidence, rival interpretations, and confidence changes as they arise.15Write the result to root memory/{question_name}.md so the reasoning trace becomes a durable project artifact.1617## Instructions18Derive {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.19Create the root memory directory when needed, then write or replace memory/{question_name}.md with this trace.20Start the file with the question, selected strategy, scale note, source constraints, and a brief statement of what the trace will inspect.21Build the scratchpad by repeatedly applying the A3 Problem Solving move: fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up.22Use a medium-depth trace by default, usually around 100 numbered lines, unless the user asks for a different depth.23Prefer concise public reasoning artifacts over hidden deliberation, and make every numbered item contribute a question, observation, test, comparison, inference, or synthesis.24End the file with a synthesis and final answer that follow from the trace, including any important uncertainty that remains.2526## Background Information About The Reasoning Strategy27A3 Problem Solving is a reasoning strategy for turning a question into an auditable public trace instead of an unstructured opinion.28It 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.29Use it when the problem benefits from the core move "fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up" and when the final answer needs evidence, assumptions, and uncertainty kept in view.30A strong A3 Problem Solving trace lets that move determine the order and granularity of the scratchpad, then compresses the result into a concise final answer.3132Algorithm for the output document:331. Restate the user's question, constraints, and evidence standard, then derive the subquestions or working items that A3 Problem Solving needs to inspect.342. Apply the core move explicitly: fit the entire problem-solving cycle on a single A3 sheet: background, current state, goal, root cause analysis, countermeasures, check, and follow-up.353. For each subquestion, case, option, hypothesis, or criterion the move creates, write numbered public reasoning items that answer it before advancing.364. Record assumptions, missing evidence, disconfirming signals, and confidence changes where they affect the analysis.375. Synthesize the completed trace into the final answer, showing how the conclusion follows from A3 Problem Solving rather than from a generic summary.3839## Output Information40Write the scratchpad as Markdown in root memory/{question_name}.md before responding to the user.41Include this scale note near the top of the file: "Scale: default - aim for around 100 numbered lines, or roughly 2,000 to 3,500 tokens, while adapting to the real complexity of the question."42Use numbered scratchpad items for scanability, but treat the number target as approximate and subordinate to usefulness.43Keep the scratchpad public, inspectable, and concise enough per line that the structure remains easy to review.44After writing the file, respond with the path, selected strategy, scale note, and final answer summary.4546## Specify Files And Length And Structure Of Output47Write the artifact to memory/{question_name}.md at the repository root, using the literal memory directory name.48Structure the file with the sections Question, Strategy, Scale, Scratchpad, Synthesis, and Final Answer.49The 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.50Use subsections inside Scratchpad when the trace becomes long enough that phases, branches, hypotheses, cases, or criteria would improve readability.51If the user supplies a domain format, evidence source, or output constraint, preserve it inside this structure while keeping the default scale approximate.
cerredz