Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
42 lines
821 B
Markdown
42 lines
821 B
Markdown
---
|
|
name: data explain
|
|
---
|
|
|
|
# /data explain - dbt Model Explanation
|
|
|
|
## Skills to Load
|
|
- skills/dbt-workflow.md
|
|
- skills/lineage-analysis.md
|
|
- skills/mcp-tools-reference.md
|
|
- skills/visual-header.md
|
|
|
|
## Visual Output
|
|
|
|
Display header: `DATA-PLATFORM - Model Explanation`
|
|
|
|
## Usage
|
|
|
|
```
|
|
/data explain <model_name>
|
|
```
|
|
|
|
## Workflow
|
|
|
|
1. **Get model info**: Use `dbt_lineage` for metadata (description, tags, materialization)
|
|
2. **Analyze dependencies**: Show upstream/downstream as tree
|
|
3. **Compile SQL**: Use `dbt_compile` to get rendered SQL
|
|
4. **Report**: Purpose, materialization, dependencies, key SQL logic
|
|
|
|
## Examples
|
|
|
|
```
|
|
/data explain dim_customers
|
|
/data explain fct_orders
|
|
```
|
|
|
|
## Required MCP Tools
|
|
|
|
- `dbt_lineage` - Get model dependencies
|
|
- `dbt_compile` - Get compiled SQL
|
|
- `dbt_ls` - List related resources
|