plan-interrogate skillA
plan-interrogate is agent-read markdown (skill) from rohitg00/pro-workflow: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# plan-interrogate Drive a plan from sketch to commitment by resolving every open decision before any code is written. ## Method 1. Restate the plan in one paragraph. Confirm with the user that this is the plan being interrogated. Do not proceed on a mis-restatement. 2. Extract the decision tree. Every branch point becomes a node. Mark 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). 3. Resolve in dependency order. A node is ready when every node it depends on is resolved. 4. For each ready open node, ask exactly one question. Keep the question tight and binary or small-multiple-choice when possible. 5. Pair every question with a **recommended answer** and one sentence of reasoning. The user can confirm, pick a different option, or push back. 6. Before asking, check whether the answer already lives in the codebase, prior commits, or an existing doc. If so, skip the question and mark the node resolved with source `inferred: <path>`. 7. Exit only when zero nodes are open. Print the resolved tree as a flat …
Read the whole file at its exact version.
How to install
mdr add rohitg00/pro-workflow/plan-interrogate@git:20260718.7f7209dmdr add rohitg00/pro-workflow/plan-interrogate@sha256:9e8f7295f03f71fcPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_p2edguba4thqxklq)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260718.7f7209d latest | 2026-07-18 | 7f7209d | 3,419 B | A | view · diff |
| git:20260417.f9e421e | 2026-04-17 | f9e421e | 2,152 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3419 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
rohitg00/pro-workflow · 2,879 stars · license none · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p2edguba4thqxklq GET https://markdownregistry.com/api/v1/resolve?ref=rohitg00/pro-workflow/plan-interrogate GET https://markdownregistry.com/api/v1/blob/9e8f7295f03f71fc9a4df90fbfacc73c915d1cd8d6c0032421ad19b0b40ca98e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.