planning-refactor-mart

Generate a markdown refactor plan for bounded mart-domain units in dbt projects.

3|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/accelerate-data/migration-utility --skill planning-refactor-mart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-refactor-mart
Source: https://github.com/accelerate-data/migration-utility/tree/main/skills/planning-refactor-mart
Command: npx skills add https://github.com/accelerate-data/migration-utility --skill planning-refactor-mart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes one or more selected targets that form a bounded mart-domain unit and outputs a markdown plan of refactor candidates. This skill is planning-only: do not mutate dbt models.

Core Features & Use Cases

  • Identify the bounded mart-domain unit from selected targets.
  • Propose staging, intermediate, and mart candidates with clear dependencies and execution order.
  • Enforce governance by referencing the plan-file-contract and dbt project standards before drafting changes.

Quick Start

Provide a bounded mart target set and run the planning flow to generate the plan at the path you specify.

Frequently Asked Questions about planning-refactor-mart

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

FAQPage Schema
How do I plan a dbt mart refactor without modifying existing data models?

You can plan a dbt mart refactor by identifying a bounded mart-domain unit from selected targets and generating a markdown plan of refactor candidates. The process proposes staging, intermediate, and mart models while ensuring no models are mutated.

What is a bounded mart-domain unit in dbt data modeling?

A bounded mart-domain unit in dbt data modeling is a selected set of targets that form a cohesive logical group. Identifying this unit allows you to propose staging, intermediate, and mart refactor candidates with clear dependencies and execution order.

Do I need a dbt manifest or catalog to plan mart refactoring?

Yes, planning mart refactors requires access to the active project root, catalog, manifest, and dbt context. These components validate the proposed staging, intermediate, and mart candidates against the plan-file-contract and dbt project standards.

How do I generate a markdown refactor plan for staging, intermediate, and mart layers?

Generate a markdown refactor plan by applying the planning flow to a bounded mart target set. You specify a plan output path, and the flow drafts staging, intermediate, and mart candidates with dependencies, enforcing governance via the plan-file-contract.

What are the limitations of planning dbt mart refactors?

The primary limitation is that this dbt mart planning process is planning-only and does not mutate dbt models. It is strictly bounded to analyzing the staging, intermediate, and mart layers you select and outputting a markdown plan of refactor candidates.