Plan Interrogate
Skill Verified ActiveStress-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.
To provide a structured method for pressure-testing designs and plans by systematically resolving all decision points before committing to implementation.
Features
- Walks decision trees for plans
- Asks precise, focused questions
- Recommends answers with reasoning
- Identifies and resolves open decisions
- Outputs a resolved decision ledger
Use Cases
- Pressure-testing a design before implementation
- Ensuring all decision points in a plan are resolved
- Refining project plans for clarity and completeness
- Getting user confirmation on design choices
Non-Goals
- Asking multiple questions at once
- Asking without exploring existing context
- Offloading design decisions entirely onto the user
- Proceeding with unresolved decisions
Workflow
- Restate the plan and confirm with the user.
- Extract the decision tree, marking nodes as open or resolved.
- Resolve nodes in dependency order.
- For each ready open node, ask exactly one question with a recommended answer and reasoning.
- Check existing codebase/docs for answers before asking.
- Exit when all nodes are resolved, printing the decision ledger.
Practices
- Decision analysis
- Plan refinement
- Systematic questioning
Versioning
- info:Release ManagementThe project includes a README with versioning information and links to npm, but there isn't a distinct manifest version declared specifically for this skill.
Practical Utility
- info:Usage examplesWhile the SKILL.md describes the output contract, there are no concrete end-to-end examples showing input, invocation, and output for this specific skill.
Installation
First, add the marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowQuality Score
VerifiedTrust Signals
Similar Extensions
Ce Brainstorm
100Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.
Claude Handoff
100Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
Review Pull Request
100Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Unslop Review
100Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment", "make this feedback sound human", "review this PR", "code review", "/review", "/unslop-review". Auto-triggers when reviewing PRs.