From studio-insight
Create a behavior matrix that cross-references actors, actions, events, and data flows across a business domain. Use when you need a comprehensive view of who does what with what data, for gap analysis, permission modeling, test planning, or when someone asks "what are all the interactions in this system". Produces a structured matrix document.
How this skill is triggered — by the user, by Claude, or both
Slash command
/studio-insight:behavior-matrixThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce a behavior matrix — a comprehensive cross-reference table showing every actor, the actions they perform, the events those actions trigger, and the data that flows between them. Reveals gaps, redundancies, and automation opportunities.
Produce a behavior matrix — a comprehensive cross-reference table showing every actor, the actions they perform, the events those actions trigger, and the data that flows between them. Reveals gaps, redundancies, and automation opportunities.
This skill uses dynamic expert loading. On every run:
architect.md (leads system analysis)studio/agents/*.md — load all custom experts the team has created${CLAUDE_SKILL_DIR}/../../agents/*.md — load shipped experts (skip any already loaded from project)## Your Domain section and title against the user's input topic. Include 1-3 most relevant domain experts._domain-expert-template.md — it's for creating new experts, not for consultation.The primary role produces the initial artifact. Domain experts review and correct it in the Expert Review step.
Accept one of:
$ARGUMENTS (e.g., "儿童健康管理")event-storm.md for events, personas/ for actors, processes/ for flowsList every actor in the system:
| Actor | Type | Description |
|---|---|---|
| 家长 | User | 记录数据、查看报告、调整计划 |
| 营养AI | AI Agent | 评估营养、生成建议、创建膳食计划 |
| 系统 | System | 数据聚合、定时任务、推送通知 |
| 外部数据源 | External | 食物营养数据库 |
Actor types: User (human), AI Agent (Claude-powered), System (automated), External (third-party).
For each actor, list all actions they can perform:
| Actor | Action | Frequency | Trigger |
|---|---|---|---|
| 家长 | 记录一餐 | 每餐 | 主动 |
| 家长 | 查看周报 | 每周 | 主动 |
| 家长 | 设置目标 | 偶尔 | 主动 |
| 营养AI | 评估单餐 | 每次记录后 | 自动 |
| 营养AI | 生成膳食计划 | 每周 | 手动/自动 |
| 系统 | 聚合日数据 | 每天 | 定时 |
| 系统 | 推送提醒 | 条件触发 | 自动 |
For each action, identify what events it triggers:
| Action | Triggers Event | Consumed By |
|---|---|---|
| 记录一餐 | meal_recorded | 营养AI (评估) |
| 评估单餐 | nutrition_assessed | 系统 (聚合), 家长 (查看) |
| 生成膳食计划 | plan_generated | 家长 (查看/调整) |
| 聚合日数据 | daily_summary_ready | 系统 (检查阈值) |
| 检查阈值 | alert_triggered | 家长 (收到提醒) |
For each action, identify data inputs and outputs:
| Action | Reads (input) | Writes (output) |
|---|---|---|
| 记录一餐 | — | meal-log entry |
| 评估单餐 | meal-log entry, nutrition-profile | assessment result |
| 生成膳食计划 | nutrition-profile, meal history | weekly-plan |
| 聚合日数据 | all meal-logs of the day | daily-summary |
| 推送提醒 | daily-summary, thresholds | notification |
Cross-reference into the full behavior matrix:
┌────────────┬───────────────┬─────────────────┬──────────────┬──────────────┐
│ Actor │ Action │ Event │ Data In │ Data Out │
├────────────┼───────────────┼─────────────────┼──────────────┼──────────────┤
│ 家长 │ 记录一餐 │ meal_recorded │ — │ meal-log │
│ 家长 │ 设置目标 │ goal_set │ — │ nutrition- │
│ │ │ │ │ profile │
│ 家长 │ 查看周报 │ report_viewed │ weekly- │ — │
│ │ │ │ summary │ │
├────────────┼───────────────┼─────────────────┼──────────────┼──────────────┤
│ 营养AI │ 评估单餐 │ nutrition_ │ meal-log, │ assessment │
│ │ │ assessed │ profile │ │
│ 营养AI │ 生成膳食计划 │ plan_generated │ profile, │ weekly-plan │
│ │ │ │ meal-history │ │
│ 营养AI │ 个性化建议 │ advice_given │ assessments, │ advice │
│ │ │ │ profile │ │
├────────────┼───────────────┼─────────────────┼──────────────┼──────────────┤
│ 系统 │ 聚合日数据 │ daily_summary_ │ meal-logs │ daily- │
│ │ │ ready │ │ summary │
│ 系统 │ 推送提醒 │ alert_triggered │ summary, │ notification │
│ │ │ │ thresholds │ │
└────────────┴───────────────┴─────────────────┴──────────────┴──────────────┘
From the matrix, identify:
List all unique data entities and who reads/writes them:
| Entity | Written by | Read by |
|---|---|---|
| meal-log | 家长 | 营养AI, 系统 |
| nutrition-profile | 家长 | 营养AI |
| weekly-plan | 营养AI | 家长 |
| daily-summary | 系统 | 系统, 家长 |
Each row in the matrix can potentially map to a plugin skill:
If domain experts were discovered in Expert Discovery, use the Agent tool to have each relevant expert review the behavior matrix.
Give each expert subagent:
Incorporate corrections. Common improvements from domain experts:
If no relevant domain experts were found, skip this step.
Present the matrix and analysis to the user:
If working within a studio workspace:
studio/changes/{domain}/behavior-matrix.md
If standalone, write to the current directory.
The file contains:
npx claudepluginhub ameng2001/astra-studio-plugins --plugin studio-insightSimulates event storming workshops with multi-persona agents to discover domain events, commands, actors, and bounded contexts. Use full-simulation, quick, or guided modes for domain modeling.
Maps, analyzes, and redesigns product systems—service blueprints, ecosystem maps, process architecture, and dependency diagrams. Use when investigating structural issues behind user experiences.
Creates BPMN process diagrams using flowchart patterns, including activities, gateways, events, swimlanes, and decision points for workflow documentation.