Software Development
Complexity Refactor Plan
Complexity Refactor Plan turns code quality & refactoring material into an operator-ready artifact with a concrete cyclomatic and cognitive complexity hotspots, refactor sequencing, and blast-radius containment. It is built for teams that need a usable draft artifact, not a broad summary with a familiar title. The skill asks for code excerpts, dependency map, or static-analysis notes, complexity, duplication, or naming concerns, and risk tolerance and test coverage context up front, then organizes the output around complexity, refactor, plan, code, and quality. It is delivered with adapters for Claude Code, Codex, OpenClaw, and Antigravity so teams can use the same workflow across their preferred agent environment. Complexity Refactor Plan is scoped to the Code Quality & Refactoring workflow and is distinct from adjacent catalog skills by producing this specific deliverable rather than a broad summary.
One-Time Purchase
$19.99
Complexity Refactor Plan — Sample Brief
Headline
Builds a code-quality repair plan for complexity refactor plan work, turning code excerpts, dependency map, or static-analysis notes, complexity, duplication, or naming concerns, and risk tolerance and test coverage context into cyclomatic and cognitive complexity hotspots, refactor sequencing, and blast-radius containment. In this example, target repository module needs a repository-backed review with commands, files, and acceptance tests that engineering can rerun. The output is a concrete operator-ready artifact: source evidence, reviewer checks, and the owner decision that determines whether the work is ready.
Evidence Packet
| Input | Example | Status |
|---|---|---|
| code excerpts, dependency map, or static-analysis notes | target repository module needs a repository-backed review with commands, files, and acceptance tests that engineering can rerun. | Provided |
| complexity, duplication, or naming concerns | Three representative examples from the current workflow | Reviewed |
| risk tolerance and test coverage context | Approval threshold and final reviewer | Confirm |
| desired refactor size and review path | Code Quality & Refactoring owner and downstream audience | Ready |
Complexity Evidence Model
| Field | What must be captured | Review consequence |
|---|---|---|
| Complexity signal | Anchor the result in complexity, refactor, and plan evidence from the supplied material. | Treat as draft until cyclomatic and cognitive complexity hotspots is source-backed. |
| Cyclomatic And Cognitive Complexity Hotspots | Separate Complexity signal, Refactor judgment, and Plan action before drafting. | Escalate when complexity evidence is missing or contradicted. |
| Refactor Sequencing | Name the review question that makes Complexity Refactor Plan different from the rest of Code Quality & Refactoring. | Reviewer resolves blast-radius containment before final use. |
Complexity Acceptance Checks
| Check | Required evidence | Review action |
|---|---|---|
| Complexity depth | Anchor the result in complexity, refactor, and plan evidence from the supplied material. | Keep, revise, or ask a targeted follow-up |
| Refactor boundary | Separate Complexity signal, Refactor judgment, and Plan action before drafting. | Confirm this is not a renamed adjacent bundle skill |
| Plan handoff | Name the review question that makes Complexity Refactor Plan different from the rest of Code Quality & Refactoring. | Assign the owner decision before final use |
Complexity Refactor Plan Work Map
Complexity Refactor Plan focus areas
Draft Operator Ready Artifact
| Complexity signal | Cyclomatic And Cognitive Complexity Hotspots | Refactor Sequencing | Blast Radius Containment | Refactor decision |
|---|---|---|---|---|
| Complexity | cyclomatic and cognitive complexity hotspots | refactor sequencing | blast-radius containment | Keep if source-backed |
| Refactor | cyclomatic and cognitive complexity hotspots | refactor sequencing | Complexity evidence is missing or contradicted. | Revise missing evidence |
| Plan | Anchor the result in complexity, refactor, and plan evidence from the supplied material. | Separate Complexity signal, Refactor judgment, and Plan action before drafting. | blast-radius containment | Assign owner decision |
Use now
Complexity Refactor Plan
Best when code quality & refactoring work needs a concrete operator-ready artifact.
Hold back
Missing evidence
Best deferred when a key input would change the artifact.
Reviewer note
The output is structured so an operator can validate the draft, edit the artifact, and hand it to the next owner without re-reading the entire packet. The final answer should label unknowns plainly and avoid inventing metrics, policies, quotes, or commitments.
This sample illustrates the skill's output format. The artifact reviewed is illustrative and should be validated against the real repository before implementation.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Code Quality & Refactoring
Bundle price: $44. Compare this skill with the full workflow bundle or Pro access.
Best for
Engineers planning a refactor of a tangled module — complexity hotspots, a safe sequencing order, and blast-radius containment. Most useful on a high-churn file everyone is afraid to touch, where the value is a low-risk path through it.
Not ideal for
Greenfield code with no complexity to unwind, and rewrites that need a product decision first. The plan sequences the work — an engineer must confirm test coverage is real before executing each step.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short setup in the repository or workspace where the skill will run. Some coding familiarity helps for implementation-heavy outputs.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.