Read a GitHub issue and all comments, review the implementation plan, and present findings
From mach10npx claudepluginhub leanandmean/mach10 --plugin mach10<issue-number>opusYou are reviewing the implementation plan for a GitHub issue. Your goal is to read the issue and all comments, independently assess the plan, and present your findings.
User input: $ARGUMENTS
The user's input contains:
Extract the issue number from the input. If the input is ambiguous, ask the user to clarify.
Read the issue title and body:
gh issue view <issue-number>
Then read all comments (--comments returns only comments and silently drops the title and body, so both calls are required):
gh issue view <issue-number> --comments
Understand:
Locate the implementation plan comment by searching all issue comments for the <!-- mach10-plan --> HTML marker. If multiple comments contain the marker, use the last one (the most recent revision). If no comment contains the marker, fall back to identifying the most recent substantive comment that contains a staged implementation plan. If no plan exists at all, inform the user and suggest running /mach10:issue-plan <issue-number> first.
Before launching exploration agents, look for project contribution guidelines in order of precedence:
CONTRIBUTING.md
DEVELOPMENT.md
.github/CONTRIBUTING.md
Read only the first file found; skip the rest.
If found, read the file and extract any planning-relevant guidance: expected project layers (e.g., models, migrations, API routes, services, UI, documentation), testing expectations (test frameworks, coverage requirements, test types), and any other requirements that a complete plan should satisfy.
Record these as project review criteria -- they will serve as benchmarks when assessing the plan in Step 4.
If no contributing guide exists, proceed without project-specific requirements.
Launch 2-3 exploration agents in parallel using the Task tool (subagent_type: "feature-dev:code-explorer"). Each agent should trace through the code comprehensively and target a different aspect of plan verification:
If project review criteria were recorded in Step 3a, include them in each agent's context so exploration can verify whether the plan covers the relevant project layers and testing infrastructure.
Each agent should return a list of key files and observations. After agents complete, read all identified files.
For each stage in the plan, assess:
Also assess the plan holistically:
Present your review to the user, organized as:
Use AskUserQuestion to ask the user how they want to proceed:
If the user selects "Update the plan", draft a revised plan incorporating the findings, and present it for review before posting. When posting the revised plan as a comment, include <!-- mach10-plan --> as the very first line of the comment body (this invisible HTML marker enables reliable identification in future sessions). If the user selects "Discuss findings", walk through the specific findings they want to explore, then ask again how to proceed. If the user selects "Cancel", stop and confirm that no changes were made.
After the user's choice is executed (unless cancelled), suggest as CLI output only (do NOT include in any GitHub comment): /clear then /mach10:issue-implement <issue-number> 1 to begin implementation.