skills.rest
outcomeeng
outcomeengOFFICIAL
Explore all skills by this author →
WebsiteGitHub

refactoring

Restructure Spec Tree nodes by moving, re-scoping, extracting enablers, or consolidating.

1|Updated Jan 6, 2026
Search Tags:#testing#refactoring#validation#spec-tree#node-move#enabler-extraction
One-click install
npx skills add https://github.com/outcomeeng/claude --skill refactoring-outcomeeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactoring
Source: https://github.com/outcomeeng/claude/tree/main/plugins/spec-tree/skills/refactoring
Command: npx skills add https://github.com/outcomeeng/claude --skill refactoring-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Move nodes, re-scope content, extract shared enablers, or consolidate nodes in the Spec Tree to restructure the project specifications.

Core Features & Use Cases

  • Move nodes between parents, update paths, and preserve tests and links across the spec tree.
  • Re-scope content across multiple nodes to balance concerns and avoid duplication.
  • Extract shared infrastructure or enablers to a dedicated enabler node when 2+ siblings require it.
  • Consolidate duplicate or overlapping nodes into a single coherent node while preserving tests and cross-links.
  • Validate changes against ADR/PDR scope, test links, and ownership, with a clear final report.

Quick Start

Perform intake, context, impact, apply, validate, and report steps by identifying the operation (Move, Re-scope, Extract enabler, Consolidate) and loading the relevant node context.

Frequently Asked Questions about refactoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restructure project specifications by moving nodes between parents?▼

You restructure project specifications by moving nodes between parents through a structured process of intake, impact analysis, applying changes, and validation. This updates paths and preserves tests and cross-links across the spec tree while documenting all modifications.

What is the best way to extract shared enablers from duplicate spec tree nodes?▼

The best way to extract shared enablers is to consolidate infrastructure required by two or more sibling nodes into a dedicated enabler node. This rebalances concerns, avoids duplication, and preserves existing test links during the refactoring process.

How do I validate spec tree changes against ADR and PDR scope?▼

You validate spec tree changes against ADR and PDR scope by enforcing operational steps and scope checks after applying modifications. The validation ensures test links, ownership, and architectural decision records remain coherent before generating a final report.

Can I consolidate overlapping nodes in a spec tree without losing test links?▼

Yes, you can consolidate duplicate or overlapping nodes into a single coherent node while preserving tests and cross-links. The refactoring process applies changes and validates them against test links and ownership to ensure no connections are lost.

When do I need to re-scope content across multiple spec tree nodes?▼

You need to re-scope content across multiple spec tree nodes when concerns become unbalanced or duplication appears. This refactoring operation rebalances the specification content across nodes while enforcing ADR and PDR scope checks and updating test links.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
gharam1234gharam1234

figma-to-component

Convert Figma design URLs into React components with CSS, tests, and Storybook.

Community
Advanced
outcomeengoutcomeeng
1

reviewing-python-architecture

Review ADRs against testing principles, Atemporal voice rules, and PDR constraints.

Official
Advanced
rezosndrezosnd

excel-generator

Generate styled Excel workbooks with formulas, charts, and data validation.

Community
Intermediate