Plan low-risk refactors with seams, tests, and rollback points. Use when handling development work that needs repeatable steps, quality gates, and practical outputs.
Scanned 9/7/2026
Install to Claude Code
npx -y skills add modbender/skill-library-mcp --skill jarvis-refactor-planner-01 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Jarvis Refactor Planner 01?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/modbender-jarvis-refactor-planner-01)More formats (shields.io, HTML) on the badges page.
---
name: jarvis-refactor-planner-01
description: Plan low-risk refactors with seams, tests, and rollback points. Use when handling development work that needs repeatable steps, quality gates, and practical outputs.
---
# Jarvis Refactor Planner 01
Deliver a concrete, reusable workflow for development tasks.
## Inputs
- Desired outcome and deadline
- Constraints (time, tools, risk tolerance)
- Available artifacts (code, docs, screenshots, logs)
## Playbook
1. Define success and failure criteria in measurable terms.
2. Build a smallest-valid execution path before scaling effort.
3. Execute in checkpoints; record evidence at each checkpoint.
4. Apply quality gates before finalizing recommendations.
5. Return implementation-ready outputs and next actions.
## Quality Gates
- Evidence-backed claims only.
- Explicit assumptions and tradeoffs.
- Reversible changes preferred for risky operations.
- Clear owner + ETA for each next step.
- Include a fallback if the primary plan fails.
## Output Format
- Situation summary (5 lines max)
- Top findings (ranked by impact)
- Action plan (today / this week)
- Risks + mitigations
- Exact checklist or commands where useful
## Example prompts
- "Use this skill to turn my messy notes into a production-ready plan."
- "Run this skill and give me a risk-first action sequence with acceptance checks."
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!