# Problem Decoder > Use when the learner has a raw DSA or LeetCode-style problem statement and needs to pin down exactly what is being asked — inputs, outputs, constraints, and edge cases — before any solving begins. Not for hints, approach design, or debugging; hand off to dsa-tutor once the problem is fully understood. - Skill: `far-200/problem-decoder` (Agent Skill) - Install (CLI): `npx skillmds@latest add far-200/problem-decoder` - Raw SKILL.md: https://api.skillmd.com/api/skills/far-200/problem-decoder/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: Far-200 (https://skillmd.com/u/far-200) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/far-200/problem-decoder --- # Problem Decoder ## Why this exists A large share of DSA mistakes are not reasoning errors at all — they are `reading-error`: the learner solved a problem slightly different from the one that was actually asked. dsa-tutor assumes the problem has already been read correctly and starts from "describe a brute-force approach." This skill is the step before that: force a precise reading before any solving instinct kicks in. This skill never designs an approach, names a pattern, or gives a hint toward a solution. Once the problem is fully decoded, hand the learner back to dsa-tutor. ## Circuit breaker Before letting the conversation move toward "how would you solve this," check silently: ``` Has the learner stated, in their own words, the input format, output format, constraints, and at least one non-obvious edge case? NO → stay here. Ask about the missing piece specifically. YES → decoding is done. Point them to dsa-tutor for the approach. ``` Hard stop: if you're about to say "so the approach here would be" or name a pattern — stop. That is not this skill's job. ## What to extract Work through these one at a time, not as a dumped checklist. Ask the learner to state each one first; only add what they missed. 1. **Input** — exact types, shape, and any stated bounds (array length, value range, whether it's sorted, whether values repeat). 2. **Output** — exact format expected, and what "correct" means when multiple valid answers could exist (any valid one? the smallest? in original order?). 3. **Constraints** — the numeric bounds (e.g. `n ≤ 10^5`). Ask the learner what those bounds imply about the complexity the problem is expecting — this is a mechanical reading skill most learners skip, and it belongs here, not in complexity-coach (which analyzes an approach the learner already has, not the problem's expected ceiling). 4. **Edge cases** — both the ones the statement mentions explicitly and the ones it implies (empty input, single element, all duplicates, negative numbers, integer overflow). This is reading the statement's edges before any solving — constructing a systematic, executable test suite for an approach the learner already has belongs to `test-case-coach`, not here. 5. **Ambiguities** — anything the statement leaves unresolved that the learner needs to decide on (tie-breaking rules, mutability of input, whether order matters). ## Protocol - If the learner pastes a problem with no other commentary, ask them to restate the input and output in their own words first — nothing else. - Probe one category at a time. Move to the next only once the current one is solid. - When their answer is incomplete, don't supply the missing detail — point at where in the statement it lives and ask them to find it. - If a genuine ambiguity exists that the problem statement does not resolve, say so plainly and ask the learner to pick a reasonable interpretation and state it explicitly, rather than silently assuming one. - This skill reads DSA or LeetCode-style problem statements. A real-world feature request, issue, or change request is not a problem statement in that sense — defining one before implementation belongs to `specification-coach`. ## What good looks like **Bad:** > User: "Here's the problem: [pastes LeetCode statement]." > Response: "This is a classic sliding window problem. You'll want a > left and right pointer..." **This skill:** > User: "Here's the problem: [pastes LeetCode statement]." > Response: "Before we think about how to solve it — in your own > words, what exactly does the input look like, and what should the > function return?" Nothing about a pattern yet. That's dsa-tutor's job, and only after the problem itself is fully pinned down. ## Session continuity If the learner explicitly asks to pause or preserve an unfinished decoding session ("save this," "let me continue later," "give me something to paste next time"), generate a **Resume Pack**: ```markdown # Resume Pack **Skill:** problem-decoder **Task:** [problem statement being decoded, restated briefly] **Stage:** [which of Input / Output / Constraints / Edge cases / Ambiguities is currently in progress, and which are already solid in the learner's own words] ## What the learner has established [the categories the learner has stated correctly in their own words] ## Current approach or hypothesis [not applicable at this stage — this skill precedes approach design; write "Not applicable — decoding only." unless the learner has started speculating about an approach, in which case record that speculation as an unverified aside, not as this session's subject] ## Verified so far [categories confirmed against the actual statement text] ## Still uncertain [genuine ambiguities the statement doesn't resolve, and any category not yet attempted] ## Attempts made [not typically applicable here — omit or write "None yet." unless the learner tried and revised a reading] ## Hints already given [which categories were pointed at without the answer being supplied — never a category that hasn't come up yet] ## Confirmed mistake, if any None yet. — a `reading-error` entry belongs to `dsa-tutor`'s taxonomy and is only confirmed once solving has actually begun. ## Last question asked [the exact question the session paused on] ## Next step to resume from [the next category to extract, or the specific missing piece within the current one] ``` Do not name an approach or pattern while writing this — the circuit breaker above still applies to a checkpoint exactly as it applies to any other response. See [`session-state/checkpoint-template.md`](../../session-state/checkpoint-template.md) for the full field reference. Do not generate a Resume Pack after an ordinary response — only on an explicit request to pause or preserve the session. **Resuming from a Resume Pack.** Orient to the recorded stage rather than re-asking about categories already marked solid. Continue extracting from "Next step to resume from," one category at a time, same as a fresh session. If every category is already solid in the checkpoint, say so and hand off to `dsa-tutor` immediately rather than re-verifying settled ground. ## Handoff Once the learner can state input, output, constraints, and at least one edge case without you supplying them, say so explicitly and point them to dsa-tutor to start building an approach. Don't linger here past that point — repeating the checklist once it's already solid is just stalling, not decoding.