[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N7FPRPTTKA2VC0PKMGKET":3,"skill-same:01M71N7FPRPTTKA2VC0PKMGKET":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":6,"updatedAt":74,"install":75,"resources":88},"01M71N7FPRPTTKA2VC0PKMGKET","kpi-dashboard-design",null,"Use when designing business KPI dashboards: choosing SMART metrics, strategic, tactical and operational layers, executive views and visualization layout. Focus is business metrics (MRR, churn, LTV\u002FCAC), unlike dashboard-builder, which targets Grafana-style operational monitoring.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fkpi-dashboard-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fkpi-dashboard-design\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"dashboard","kpi dashboard design","dashboard design","kpi","kpi dashboard","design","metrics","dashboards","analytics","data","layout","focus","monitoring","grafana","when","tactical","churn","which","visualization","builder","2026-11-10 10:56:23",false,"---\nname: kpi-dashboard-design\ndescription: \"Use when designing business KPI dashboards: choosing SMART metrics, strategic, tactical and operational layers, executive views and visualization layout. Focus is business metrics (MRR, churn, LTV\u002FCAC), unlike dashboard-builder, which targets Grafana-style operational monitoring.\"\ntags: [\"data\",\"operations\",\"visualization\",\"analytics\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fwshobson\u002Fagents\nsource_path: \"plugins\u002Fbusiness-analytics\u002Fskills\u002Fkpi-dashboard-design\"\nsource_commit: 4236bb91f8395b0435f1d8b8baf9e8e4c69a8620\n---\n# KPI Dashboard Design\n\nComprehensive patterns for designing effective Key Performance Indicator (KPI) dashboards that drive business decisions.\n\n## When to Use This Skill\n\n- Designing executive dashboards\n- Selecting meaningful KPIs\n- Building real-time monitoring displays\n- Creating department-specific metrics views\n- Improving existing dashboard layouts\n- Establishing metric governance\n\n## Core Concepts\n\n### 1. KPI Framework\n\n| Level           | Focus            | Update Frequency  | Audience   |\n| --------------- | ---------------- | ----------------- | ---------- |\n| **Strategic**   | Long-term goals  | Monthly\u002FQuarterly | Executives |\n| **Tactical**    | Department goals | Weekly\u002FMonthly    | Managers   |\n| **Operational** | Day-to-day       | Real-time\u002FDaily   | Teams      |\n\n### 2. SMART KPIs\n\n```\nSpecific: Clear definition\nMeasurable: Quantifiable\nAchievable: Realistic targets\nRelevant: Aligned to goals\nTime-bound: Defined period\n```\n\n### 3. Dashboard Hierarchy\n\n```\n├── Executive Summary (1 page)\n│   ├── 4-6 headline KPIs\n│   ├── Trend indicators\n│   └── Key alerts\n├── Department Views\n│   ├── Sales Dashboard\n│   ├── Marketing Dashboard\n│   ├── Operations Dashboard\n│   └── Finance Dashboard\n└── Detailed Drilldowns\n    ├── Individual metrics\n    └── Root cause analysis\n```\n\n## Detailed worked examples and patterns\n\nDetailed sections (starting with `## Common KPIs by Department`) live in `references\u002Fdetails.md`. Read that file when the navigation summary above is insufficient.\n\n## Best Practices\n\n### Do's\n\n- **Limit to 5-7 KPIs** - Focus on what matters\n- **Show context** - Comparisons, trends, targets\n- **Use consistent colors** - Red=bad, green=good\n- **Enable drilldown** - From summary to detail\n- **Update appropriately** - Match metric frequency\n\n### Don'ts\n\n- **Don't show vanity metrics** - Focus on actionable data\n- **Don't overcrowd** - White space aids comprehension\n- **Don't use 3D charts** - They distort perception\n- **Don't hide methodology** - Document calculations\n- **Don't ignore mobile** - Ensure responsive design\n\n## Troubleshooting\n\n### MRR shown on dashboard contradicts finance's number\n\nThe most common cause is inconsistent treatment of annual plans. Finance may prorate to a daily rate while the dashboard normalizes to monthly. Align on a single formula and document it directly on the dashboard card:\n\n```sql\n-- Explicit formula shown in tooltip \u002F data dictionary\n-- Annual plans: divide total contract value by 12\n-- Quarterly plans: divide by 3\n-- Monthly plans: use as-is\nCASE subscription_interval\n    WHEN 'monthly'   THEN amount\n    WHEN 'quarterly' THEN amount \u002F 3.0\n    WHEN 'yearly'    THEN amount \u002F 12.0\nEND AS normalized_mrr\n```\n\n### Dashboard shows green but product team reports users complaining\n\nThe dashboard likely tracks system uptime (a lagging indicator) but not user-facing quality metrics. Add customer-perceived metrics alongside infrastructure metrics:\n\n| Infrastructure (green) | User-perceived (add these) |\n|---|---|\n| API uptime 99.9% | P95 page load time |\n| Error rate 0.1% | Task completion rate |\n| Queue depth normal | Support ticket volume |\n\n### Retention cohort looks flat — no variation between cohorts\n\nCheck whether the cohort query is partitioning by signup month correctly. A common bug is using `created_at::date` instead of `DATE_TRUNC('month', created_at)`, which groups by day and produces cohorts too small to show trends:\n\n```sql\n-- Wrong: too granular, cohorts are too small\nDATE_TRUNC('day', created_at) AS cohort_date\n\n-- Correct: monthly cohorts\nDATE_TRUNC('month', created_at) AS cohort_month\n```\n\n### Real-time dashboard hammers the database\n\nA live dashboard refreshing every 10 seconds with complex cohort SQL will degrade production query performance. Separate OLAP workloads from OLTP by writing pre-aggregated metrics to a summary table via a scheduled job, and have the dashboard read from that:\n\n```python\n# Scheduled every 5 minutes via cron\u002FCelery\ndef refresh_mrr_summary():\n    conn.execute(\"\"\"\n        INSERT INTO kpi_snapshot (metric, value, snapshot_at)\n        SELECT 'mrr', SUM(...), NOW()\n        FROM subscriptions WHERE status = 'active'\n        ON CONFLICT (metric) DO UPDATE SET value = EXCLUDED.value\n    \"\"\")\n```\n\n### Alert thresholds fire constantly, team ignores them\n\nStatic thresholds set once and never reviewed cause alert fatigue. Use dynamic thresholds based on rolling averages so alerts fire only when the metric deviates significantly from its own baseline:\n\n```python\n# Alert if current value is > 2 standard deviations from 30-day rolling mean\ndef is_anomalous(current: float, history: list[float]) -> bool:\n    mean = statistics.mean(history)\n    stdev = statistics.stdev(history)\n    return abs(current - mean) > 2 * stdev\n```\n\n## Related Skills\n\n- `data-storytelling` - Turn dashboard findings into narratives that drive executive decisions\n","# KPI Dashboard Design\n\nComprehensive patterns for designing effective Key Performance Indicator (KPI) dashboards that drive business decisions.\n\n## When to Use This Skill\n\n- Designing executive dashboards\n- Selecting meaningful KPIs\n- Building real-time monitoring displays\n- Creating department-specific metrics views\n- Improving existing dashboard layouts\n- Establishing metric governance\n\n## Core Concepts\n\n### 1. KPI Framework\n\n| Level           | Focus            | Update Frequency  | Audience   |\n| --------------- | ---------------- | ----------------- | ---------- |\n| **Strategic**   | Long-term goals  | Monthly\u002FQuarterly | Executives |\n| **Tactical**    | Department goals | Weekly\u002FMonthly    | Managers   |\n| **Operational** | Day-to-day       | Real-time\u002FDaily   | Teams      |\n\n### 2. SMART KPIs\n\n```\nSpecific: Clear definition\nMeasurable: Quantifiable\nAchievable: Realistic targets\nRelevant: Aligned to goals\nTime-bound: Defined period\n```\n\n### 3. Dashboard Hierarchy\n\n```\n├── Executive Summary (1 page)\n│   ├── 4-6 headline KPIs\n│   ├── Trend indicators\n│   └── Key alerts\n├── Department Views\n│   ├── Sales Dashboard\n│   ├── Marketing Dashboard\n│   ├── Operations Dashboard\n│   └── Finance Dashboard\n└── Detailed Drilldowns\n    ├── Individual metrics\n    └── Root cause analysis\n```\n\n## Detailed worked examples and patterns\n\nDetailed sections (starting with `## Common KPIs by Department`) live in `references\u002Fdetails.md`. Read that file when the navigation summary above is insufficient.\n\n## Best Practices\n\n### Do's\n\n- **Limit to 5-7 KPIs** - Focus on what matters\n- **Show context** - Comparisons, trends, targets\n- **Use consistent colors** - Red=bad, green=good\n- **Enable drilldown** - From summary to detail\n- **Update appropriately** - Match metric frequency\n\n### Don'ts\n\n- **Don't show vanity metrics** - Focus on actionable data\n- **Don't overcrowd** - White space aids comprehension\n- **Don't use 3D charts** - They distort perception\n- **Don't hide methodology** - Document calculations\n- **Don't ignore mobile** - Ensure responsive design\n\n## Troubleshooting\n\n### MRR shown on dashboard contradicts finance's number\n\nThe most common cause is inconsistent treatment of annual plans. Finance may prorate to a daily rate while the dashboard normalizes to monthly. Align on a single formula and document it directly on the dashboard card:\n\n```sql\n-- Explicit formula shown in tooltip \u002F data dictionary\n-- Annual plans: divide total contract value by 12\n-- Quarterly plans: divide by 3\n-- Monthly plans: use as-is\nCASE subscription_interval\n    WHEN 'monthly'   THEN amount\n    WHEN 'quarterly' THEN amount \u002F 3.0\n    WHEN 'yearly'    THEN amount \u002F 12.0\nEND AS normalized_mrr\n```\n\n### Dashboard shows green but product team reports users complaining\n\nThe dashboard likely tracks system uptime (a lagging indicator) but not user-facing quality metrics. Add customer-perceived metrics alongside infrastructure metrics:\n\n| Infrastructure (green) | User-perceived (add these) |\n|---|---|\n| API uptime 99.9% | P95 page load time |\n| Error rate 0.1% | Task completion rate |\n| Queue depth normal | Support ticket volume |\n\n### Retention cohort looks flat — no variation between cohorts\n\nCheck whether the cohort query is partitioning by signup month correctly. A common bug is using `created_at::date` instead of `DATE_TRUNC('month', created_at)`, which groups by day and produces cohorts too small to show trends:\n\n```sql\n-- Wrong: too granular, cohorts are too small\nDATE_TRUNC('day', created_at) AS cohort_date\n\n-- Correct: monthly cohorts\nDATE_TRUNC('month', created_at) AS cohort_month\n```\n\n### Real-time dashboard hammers the database\n\nA live dashboard refreshing every 10 seconds with complex cohort SQL will degrade production query performance. Separate OLAP workloads from OLTP by writing pre-aggregated metrics to a summary table via a scheduled job, and have the dashboard read from that:\n\n```python\n# Scheduled every 5 minutes via cron\u002FCelery\ndef refresh_mrr_summary():\n    conn.execute(\"\"\"\n        INSERT INTO kpi_snapshot (metric, value, snapshot_at)\n        SELECT 'mrr', SUM(...), NOW()\n        FROM subscriptions WHERE status = 'active'\n        ON CONFLICT (metric) DO UPDATE SET value = EXCLUDED.value\n    \"\"\")\n```\n\n### Alert thresholds fire constantly, team ignores them\n\nStatic thresholds set once and never reviewed cause alert fatigue. Use dynamic thresholds based on rolling averages so alerts fire only when the metric deviates significantly from its own baseline:\n\n```python\n# Alert if current value is > 2 standard deviations from 30-day rolling mean\ndef is_anomalous(current: float, history: list[float]) -> bool:\n    mean = statistics.mean(history)\n    stdev = statistics.stdev(history)\n    return abs(current - mean) > 2 * stdev\n```\n\n## Related Skills\n\n- `data-storytelling` - Turn dashboard findings into narratives that drive executive decisions\n",{"name":5,"tags":60,"tools":62,"source":63,"license":14,"description":7,"source_path":64,"source_commit":65},[44,61,53,43],"operations",[],"https:\u002F\u002Fgithub.com\u002Fwshobson\u002Fagents","plugins\u002Fbusiness-analytics\u002Fskills\u002Fkpi-dashboard-design","4236bb91f8395b0435f1d8b8baf9e8e4c69a8620","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fkpi-dashboard-design",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add monoes\u002Fmonomind --skill kpi-dashboard-design",{"tool":81,"command":82},"bunx","bunx skills add monoes\u002Fmonomind --skill kpi-dashboard-design",{"tool":84,"command":85},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill kpi-dashboard-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fkpi-dashboard-design\u002FSKILL.md",true,[89,94],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1068,{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fdetails.md","REFERENCE","参考文档",14987,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fkpi-dashboard-design\u002Freferences\u002Fdetails.md",[101,129,160,186,208,235],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":128},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[109,110,111,112,113,114,40,115,116,117,118,119,120,121,122,123,124,125,126,127],"zk","zk steward","steward","zero-knowledge","engineer","choice","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":142,"publishedAt":128},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[136,139],{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":140,"categoryName":141,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[143,144,145,113,146,147,49,148,117,149,150,151,152,153,154,155,156,157,158,159],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":128},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理",[153,171,172,173,174,115,175,49,176,177,178,152,179,180,181,41,182,183,184,185],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","feature","problem statement","use","document",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":190,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":128},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[193],{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[117,153,195,196,197,198,115,184,49,199,200,201,202,178,203,204,205,206,207,44],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":220,"publishedAt":128},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[214,217],{"categoryNo":215,"categoryName":216,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":218,"categoryName":219,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[221,222,223,224,197,225,226,227,228,116,229,230,231,117,120,203,232,233,234,205],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":239,"categories":240,"keywords":242,"publishedAt":128},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[241],{"categoryNo":218,"categoryName":219,"taxonomyType":21,"taxonomyTypeDesc":22},[223,243,244,245,246,247,248,197,249,250,149,251,252,253,120,203,254,61,205,255],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","systems"]