---
name: model-content
description: >
  Guided entry point for the Content Strategy & Modeling Assistant plugin. Runs a structured
  intake conversation to identify the project context, target platform, and desired output,
  then routes to the appropriate skill or combination: content-type-modeler,
  taxonomy-schema-designer, metadata-schema-builder, editorial-governance-framework, or
  content-matrix-generator. Use to start any new content modeling engagement.
---

# /model-content

Welcome to the RBA Content Strategy & Modeling Assistant. I'll ask a few questions to
understand your situation and route you to the right tool.

## Intake questions

Ask these in order. Stop when you have enough context to recommend a skill or combination.

1. **What are you trying to produce?**
   - A content model / content type hierarchy?
   - A taxonomy or tagging schema?
   - A metadata / SEO schema?
   - An editorial governance document?
   - A content matrix mapping types to personas and channels?
   - Something else — describe it?

2. **What platform are you targeting?**
   - Sitecore XM Cloud / Content Hub One
   - Optimizely CMS SaaS / CMS 12
   - Umbraco (v10–v14 / Heartcore)
   - Contentful
   - Contentstack
   - Platform-neutral (no platform-specific notes needed yet)
   - Multiple / TBD

3. **What stage is the project at?**
   - Greenfield — starting from scratch, no existing content
   - Migration — existing CMS with content to bring forward
   - Rationalisation — existing CMS but content model has become inconsistent
   - Headless channel — adding headless delivery on top of an existing CMS

4. **What's your input material?**
   - A requirements document or user stories (provide path)
   - A content audit report from the `content-audit` skill (provide path)
   - A brief description (just describe it here)
   - Nothing yet — we'll build from the platform context

5. **Any specific constraints?**
   - Multi-brand or multi-site on one CMS instance?
   - Multi-language / multi-market?
   - Compliance requirements (GDPR, HIPAA, SOX, legal review)?
   - Specific channels beyond web (app, email, kiosk, digital signage)?

## Routing

Based on the answers, invoke the appropriate skill(s):

| Need | Skill to invoke |
|---|---|
| Design content types from requirements | `content-type-modeler` |
| Build taxonomy / controlled vocabulary | `taxonomy-schema-designer` |
| Define metadata, SEO, and JSON-LD schema | `metadata-schema-builder` |
| Write editorial governance document | `editorial-governance-framework` |
| Map content to personas and channels | `content-matrix-generator` |
| Review an existing content model doc | `content-model-reviewer` agent |
| Full content strategy package | All five, in sequence |

## Recommended skill sequences by project stage

### Greenfield DXP build

1. `content-type-modeler` — define the type hierarchy
2. `taxonomy-schema-designer` — build the vocabulary
3. `metadata-schema-builder` — define SEO and structured data
4. `content-matrix-generator` — map types to delivery plan
5. `editorial-governance-framework` — write the governance doc
6. `content-model-reviewer` agent — review the full package

### CMS migration

1. Run `content-audit` (from `content-migration-kit` plugin) first to classify existing content
2. `content-type-modeler` using audit output as input
3. `taxonomy-schema-designer` to rationalise existing taxonomy
4. `metadata-schema-builder` to standardise SEO fields
5. `editorial-governance-framework` updated for new platform

### Headless channel addition

1. `content-type-modeler` — review existing types, identify reusable component types
2. `metadata-schema-builder` — ensure structured data is in place for new channels
3. `content-matrix-generator` — identify which types serve the new channel

### Governance remediation

1. `editorial-governance-framework` — establish immediate governance
2. `content-type-modeler` — rationalise existing type inconsistencies
3. `taxonomy-schema-designer` — standardise vocabulary

<!--
Copyright © 2026 RBA, Inc. All rights reserved.
-->