Return issue to plan-ready status for re-implementation after major review issues
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add MarcusJellinghaus/mcp-workspace --skill implementation_needs_rework --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Implementation Needs Rework?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/marcusjellinghaus-implementation-needs-rework)More formats (shields.io, HTML) on the badges page.
---
description: Return issue to plan-ready status for re-implementation after major review issues
disable-model-invocation: true
allowed-tools:
- "Bash(mcp-coder gh-tool set-status *)"
---
# Return to plan-ready after major review issues
Transitions the issue back to `plan-ready` status for re-implementation when code review identifies major issues that cannot be fixed with minor changes.
## When to Use
| Situation | Action |
|-----------|--------|
| Minor fixes | Fix directly, re-run `/implementation_review` or `/implementation_review_supervisor` |
| **Major issues** | **This command** (after `/implementation_new_tasks` + `/commit_push`) |
| Approved | `/implementation_approve` |
## Prerequisites
- New implementation steps created (`/implementation_new_tasks`)
- Changes committed and pushed (`/commit_push`)
## Instructions
```bash
mcp-coder gh-tool set-status status-05:plan-ready
```
Confirm the status change was successful. If it fails, report the error. Do not use `--force` unless explicitly asked.
## Next Steps
Run `mcp-coder implement` to process the new steps, then `/implementation_review` or `/implementation_review_supervisor`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
