pm-refactor

Refactor PM knowledge registers and decisions under human-approved governance workflows.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/LopeWale/amplLABS --skill pm-refactor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-refactor
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skills/pm-refactor
Command: npx skills add https://github.com/LopeWale/amplLABS --skill pm-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PM knowledge system can become crowded and ambiguous as registers and decisions proliferate; this skill provides a principled mechanism to refactor the structure, rename actions for clarity, and reorganize folders with human safeguards.

Core Features & Use Cases

  • Audit and identify structural issues in the decisions vault (registers, folders, titles).
  • Propose and execute governance-driven restructuring actions such as splitting overcrowded registers, merging thin ones, and renaming decisions, all under explicit human approval.
  • Update hub mappings and documentation to reflect the new architecture so future decisions remain navigable.

Quick Start

Execute a reorganization by issuing a command like "/pm-refactor" with subcommands such as "split [register]", "merge [register-a] [register-b]", or "reorganize" and confirm the human review.

Frequently Asked Questions about pm-refactor

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

FAQPage Schema
How do I restructure overcrowded decision registers in a PM knowledge vault?

To restructure overcrowded decision registers, you can execute a split command to divide them into smaller sets, reorganize folders, and update hub mappings while enforcing governance rules and requiring human approval before changes are applied.

What is the best way to merge thin registers and rename decisions under controlled workflows?

Merging thin registers and renaming decisions is handled through governance-driven workflows that generate auditable proposals for human review, ensuring structural clarity and updating documentation to reflect the new architecture.

How do I audit a PM knowledge system to identify structural ambiguity in folders and titles?

Auditing a PM knowledge system involves scanning the decisions vault to identify structural issues across registers, folders, and titles, then proposing governance-driven restructuring actions to improve clarity and navigability.

Can I execute vault architecture refactoring without explicit human approval?

No, vault architecture refactoring requires explicit human approval. The system generates auditable proposals for review and enforces governance rules to ensure all structural changes, like splitting or merging registers, are confirmed before execution.

When should I reorganize my PM knowledge system to improve governance and clarity?

You should reorganize your PM knowledge system when registers and decisions proliferate, causing crowding and ambiguity, requiring a principled mechanism to refactor structure, rename actions, and reorganize folders with human safeguards.

How do I update hub mappings after splitting or merging decision registers?

After splitting or merging decision registers, hub mappings and documentation are automatically updated to reflect the new architecture, ensuring future decisions remain navigable and governance rules track all structural changes.