Mmcp.market

plan-interrogate skill

by rohitg00·rohitg00/pro-workflow·2.9k stars

Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.

A100/100content scan

Is the plan-interrogate skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the plan-interrogate skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/rohitg00/pro-workflow.git /tmp/pro-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/pro-workflow/skills/plan-interrogate ~/.claude/skills/plan-interrogate
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

plan-interrogate

Drive a plan from sketch to commitment by resolving every open decision before any code is written.

Method

the plan being interrogated. Do not proceed on a mis-restatement.

  1. Restate the plan in one paragraph. Confirm with the user that this is

each node as open (undecided) or resolved. A resolved node carries a source tag: user (the user answered), inferred (the codebase or an existing constraint settled it).

  1. Extract the decision tree. Every branch point becomes a node. Mark

depends on is resolved.

  1. Resolve in dependency order. A node is ready when every node it

tight and binary or small-multiple-choice when possible.

  1. For each ready open node, ask exactly one question. Keep the question

reasoning. The user can confirm, pick a different option, or push back.

  1. Pair every question with a recommended answer and one sentence of

prior commits, or an existing doc. If so, skip the question and mark the node resolved with source inferred: .

  1. Before asking, check whether the answer already lives in the codebase,

list: Decision - Choice - Source (user | inferred: ).

  1. Exit only when zero nodes are open. Print the resolved tree as a flat

Anti-patterns

the ability to react to each answer individually.

  • Asking multiple questions at once. The user loses context and you lose

question, read first.

  • Asking before exploring. If a fifteen-second read would answer the

survey; it offloads design onto the user.

  • Asking without a recommendation. A question without a stance is a

downstream question is premature.

  • Rolling past an unresolved node. If a dependency is not pinned, the

Outputs

The interrogation produces three artifacts, not just answers. Offer to write each; do not force it.

Decision - Choice - Source (user | inferred: ).

  1. Decision ledger (always). The resolved tree as a flat list:

A short shared-language file: every domain term you and the user had to pin down, with a one-line definition in the project's own words. This is what stops the agent from using twenty words where one will do next session, and keeps names in code consistent. One term per line: term - what it means here. Point future sessions at it. On re-run, merge new terms in place rather than overwriting existing ones.

  1. CONTEXT.md (when the interrogation surfaced project-specific terms).

short record per decision that a future reader would question: the context, the choice, the alternatives rejected, and why. Keep them in docs/decisions/NNNN-slug.md. Read the directory first and number from the highest existing record so two records never collide. Skip the obvious ones - a record for a trivial choice is noise.

  1. Decision records (for contested or hard-to-reverse nodes only). One

Output contract

The decision ledger the user can paste into the plan doc. No prose summary. No hedging. If the user declines to decide a node, mark it DEFERRED with the reason the user gave - this is not the same as open. When you write CONTEXT.md or a decision record, keep it in the project's language, not a generic template.

More skills from rohitg00/pro-workflow

  • Aagent-teamsCoordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
  • Aauto-setupAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
  • Abatch-orchestrationDecompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
  • Cbug-captureCapture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
  • Acompact-guardSmart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
  • Acontext-engineeringMaster the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
  • Acontext-optimizerOptimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.
  • Acost-trackerTrack session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
  • Adesign-engineeringApply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an animation", "polish the UI", "review this component".
  • AdeslopRemove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
  • Adomain-modelingBuild the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages.
  • Afile-watcherConfigure file watching hooks to auto-react to config changes, env file updates, and dependency modifications. Use to set up reactive workflows.

All agent skills → · MCP servers