Pre-defined architectures for Microsoft Fabric — powered by an AI agent that guides you step by step.
Microsoft Fabric is powerful — but knowing which services to combine and how to wire them together takes time. @fabric-advisor asks the right questions about your business problem, picks the architecture, and hands you a fully deployable script. Zero to deployed in the cloud in minutes.
Describe Problem → Pick Architecture → ★ You Approve → Deploy → One Brief
Prerequisites: Python 3.11+, GitHub Copilot with agent mode
python _shared/scripts/run-pipeline.py start "My Project" --problem "describe your business problem"The pipeline runner generates agent prompts — paste each into Copilot chat. Use advance and next to progress through phases. See _shared/workflow-guide.md for the full pipeline reference.
The Item Type Registry is the single source of truth for all Fabric item types — 25+ items with metadata including API paths, CI/CD deployment strategies, and wave ordering. This registry drives task flows, deployment scripts, and decision resolution.
The _shared/templates/ directory contains empty-state definition files for every deployable Fabric item type, sourced from Microsoft's REST API documentation. These are the single source of truth for item content — what you see on disk is byte-for-byte what fabric-cicd will base64-encode and POST to the Fabric Items API.
Each project produces two deliverables — one doc, one deployment:
_projects/your-project/
├── docs/project-brief.md ← ONE human-readable doc (problem, architecture, decisions, validation)
└── deploy/ ← Deployable scripts (fabric-cicd, .platform files, config)
No wiki sprawl. No 17-file documentation explosion. One brief a CTO can read in 10 minutes, plus the scripts to deploy it.
| Resource | Description |
|---|---|
| 13 Task flows | Pre-defined architectures — batch, streaming, hybrid, ML, API, governance |
| 7 Decision Guides | Storage, ingestion, processing, visualization, skillset, parameterization, API |
| Deployment Diagrams | Dependency-ordered wave plans for each task flow |
| Skill | Purpose | Status |
|---|---|---|
/fabric-discover |
Understand your problem, recommend an architecture | ✅ Available |
/fabric-design |
Design your architecture with decision records | ✅ Available |
/fabric-deploy |
Generate deployment scripts via fabric-cicd |
✅ Available |
/fabric-heal |
Improve pattern matching over time | ✅ Available |
/fabric-test |
Test plans and post-deployment validation | ✅ Available |
/fabric-document |
Synthesizes pipeline handoffs into a single project brief | ✅ Available |
.github/agents/ → Orchestrator agent (@fabric-advisor)
.github/skills/ → Composable skills with pre-compute scripts
decisions/ → 7 decision guides (YAML frontmatter + decision trees)
diagrams/ → 13 deployment diagrams (dependency-ordered)
_shared/registry/ → Canonical JSON registries (item types, deployment order, skills)
_shared/templates/ → Empty-state item definition files (source of truth for fabric-cicd)
_shared/lib/ → Shared Python modules
_shared/scripts/ → Pipeline CLI (run-pipeline, new-project, fleet-runner)
_shared/tests/ → Test suite (862 tests)
_projects/ → Per-project workspaces (gitignored)
We welcome contributions — especially to the Item Type Registry. See CONTRIBUTING.md for guidelines on adding task flows, decision guides, skills, and more.