claude

relay

AI squad for Power Platform development — Scout, Drafter, Auditor, Warden, Critic, Vault, Forge specialists, Sentinel

1 on GitHubby Genv0.7.0MITupdated 5 months ago
/

Plugin relay from marketplace relay-marketplace in Genb2nu/Relay. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (23)

  • canvas-app-design-patterns

    Visual design patterns and Power Fx colour/layout conventions for Canvas Apps. Covers Fluent-aligned colour tokens, accessible contrast ratios, standard control sizing, gallery patterns, status badge patterns, and navigation patterns — all expressed as Power Fx values ready for Stylist to use. Refer

  • canvas-app-design-reading

    How to analyze a screenshot or wireframe and extract a Canvas App design system from it. Used by Stylist when the user provides a reference image. Produces a project-specific design-system.md that captures layout, structure, component patterns, and visual style — without assuming any fixed template.

  • canvas-app-enterprise-layout

    Reference pattern for enterprise Canvas Apps with vertical pill navigation. Three-zone layout: pill nav left, search bar top, tiles + table in body. Component-based with HtmlText containers. Use as a reference ONLY when the project or user-provided screenshot matches this pattern — not as a default.

  • canvas-app-screen-layout

    Six standard screen layout archetypes for Canvas Apps with exact zone dimensions, responsive formulas, and ASCII zone diagrams. Stylist references this when assigning layouts to screens. forge-canvas references this when positioning controls. - screen layout - canvas layout - zone dimensions - layou

  • canvas-mcp-prompt-patterns

    Library of Canvas Authoring MCP prompt patterns — what works, what doesn't, and lessons learned from real projects. Stylist references this when writing MCP prompt sections in design-system.md. Grows after each project. - mcp prompt - generate-canvas-app - canvas prompt - prompt pattern - canvas gen

  • dataverse-plugin-deployment-cycle

    Complete Dataverse plugin deployment cycle: compile, upload DLL, register types, register steps, register pre-images, cache flush, verify via trace logs. Covers exact Web API calls, error codes, and the mandatory ordering that prevents runtime failures. - plugin registration - plugin deployment - pr

  • dataverse-privilege-depth-patterns

    Privilege depth semantics in Dataverse: User/BU/Parent-Child BU/Org depths, flat-BU limitations, AddPrivilegesRole vs ReplacePrivilegesRole, Access Teams vs Owner Teams, and RetrieveUserPrivileges diagnostic API. Essential for Warden, Vault, and Sentinel when designing and testing security. - privil

  • dataverse-schema-api

    Dataverse Web API patterns for schema operations: creating tables, columns, relationships, option sets, and alternate keys via the Metadata API. Covers EntityDefinitions, AttributeDefinitions, and RelationshipDefinitions endpoints with exact request bodies and common error codes. - create table - cr

  • playwright-testing

    End-to-end UI testing for Power Platform apps using Microsoft's official power-platform-playwright-toolkit. Covers Canvas App iframe scoping, Model-Driven App grid/form components, authentication setup, Playwright MCP for AI-assisted test generation, and Page Object Model patterns. Used by Sentinel

  • power-fx-patterns

    Proven Power Fx patterns for Canvas Apps on Dataverse. Covers current-user filtering, lookup column comparisons, delegation-safe queries, balance calculations, navigation, and common anti-patterns. Grows with every project — add learnings here so they're never re-discovered. Reference whenever writi

  • power-platform-alm

    ALM pipeline patterns for Power Platform. Covers solution export/import, Azure DevOps integration, Git integration, environment promotion strategy, and PAC CLI workflows. Reference for Drafter when planning deployment and for Courier when executing it. - ALM - deployment - solution export - pipeline

  • power-platform-footgun-checklist

    Critic's structured checklist of known Power Platform footguns, anti-patterns, and common oversights. Critic walks this list before any free-form review. Each item is marked PASS / FAIL / N/A with a one-line justification. - footgun - checklist - critic review - adversarial check - Read

  • power-platform-security-patterns

    Warden's knowledge base. Covers the Dataverse security model, common UI-vs-actual-security traps, FLS verification procedures, connection reference risks, and security role design patterns. Reference this skill whenever reviewing or designing Power Platform security. - security role - field level se

  • relay-analysis

    Analyst's knowledge base. How to map existing Power Platform solutions, document component inventories, identify gaps vs plan, and produce docs/existing-solution.md for audit/change workflows. - existing solution - solution analysis - component inventory - analyse - audit existing - change impact -

  • relay-auditing

    Auditor's knowledge base. 20-point completeness checklist for reviewing technical plans against requirements. Covers how to identify gaps, write issues with severity ratings, and make the approval decision. - plan review - completeness check - auditor checklist - plan gap - plan quality - Read

  • relay-debugging

    Systematic root cause diagnosis for Power Platform bugs. Used by Critic in /relay:bugfix mode to diagnose before Drafter fixes. Traces the full execution path, identifies root cause, eliminates alternative causes. Adapted from Superpowers systematic-debugging — no external dependency required. - deb

  • relay-discovery

    Socratic discovery for Power Platform projects. Used by Scout to turn a one-paragraph brief into a fully validated requirements document. Asks questions one at a time, proposes approaches, validates design sections before writing. Adapted from Superpowers brainstorming skill — no external dependency

  • relay-orchestration

    Conductor orchestration patterns for dispatching and coordinating Relay specialist agents. Covers how to dispatch subagents with precise context, handle their responses, manage phase transitions, and maintain state. Adapted from Superpowers subagent-driven-development — no external dependency requir

  • relay-parallel-agents

    Patterns for dispatching Relay agents in parallel. Covers Phase 3 (Auditor + Warden), Phase 5 (Vault + Stylist), and Phase 6 (Sentinel + Warden). Both agents must complete and pass before the phase gate clears. Adapted from Superpowers dispatching-parallel-agents — no external dependency required. -

  • relay-planning

    Structured plan writing for Power Platform projects. Used by Drafter to turn approved requirements into a locked implementation plan with exact component specifications, build order, and security design. Adapted from Superpowers writing-plans — no external dependency required. - write plan - impleme

  • relay-recovery-playbook

    Recovery sequences for common Relay smoke-test and environment blockers. Covers Power Pages provisioning failures, missing Power Pages triggers in Power Automate, and Model-Driven App deployment recovery patterns so agents can continue from prior evidence instead of repeating blind retries. - recove

  • relay-verification

    Verification patterns for Sentinel — checking that what was built matches what was planned. Never declare completion without verification. Cross-checks built components against plan.md spec item by item. Adapted from Superpowers verification-before-completion — no external dependency required. - ver

  • relay-workflow

    Master workflow skill for Relay. Defines the end-to-end lifecycle for Power Platform projects: discovery → planning → review → adversarial pass → build → verification → deploy. Automatically triggered when Conductor starts a project. - relay - start project - new power platform project - begin relay

Slash commands (22)

  • /relay:agent

    Talk directly to a specific Relay agent for a follow-up question, outside the normal workflow.

  • /relay:analyse

    Map an existing Power Platform solution before making changes. Invokes Analyst to read the deployed solution via Dataverse MCP and PAC CLI and produce a complete inventory of what exists. Run this before /relay:change or /relay:bugfix on an existing solution. - relay analyse - relay analyze - analys

  • /relay:audit

    Audit an existing Power Platform solution. Points Analyst + Auditor + Warden + Critic at a live deployed solution and produces a comprehensive audit report covering technical completeness, security gaps, footgun risks, and remediation recommendations. Use on any existing solution — not just ones bui

  • /relay:bugfix

    Fix a specific bug in an existing Power Platform solution. Critic diagnoses the root cause first, Drafter writes a minimal fix plan, Forge touches only what the fix requires. Designed to be surgical — no unintended side effects. - relay bugfix - fix bug - bug fix - something is broken - not working

  • /relay:change

    Add a feature or make a scoped change to an existing Power Platform solution. Requires /relay:analyse to have run first. Produces a change-plan that explicitly scopes what is touched and what is not — preventing unintended side effects on working components. - relay change - add feature - modify sol

  • /relay:config

    View or edit Relay configuration — enforcement mode, model overrides, tool limits.

  • /relay:deploy

    Package the solution for deployment. Exports managed solution and prepares for environment promotion.

  • /relay:doctor

    Pre-flight environment check. Validates all CLI tools, plugins, MCP servers, and auth profiles are properly configured. Run once after installing Relay, or any time you suspect a missing dependency. Supports --fix flag for auto-remediation of fixable issues. - relay doctor - check setup - prerequisi

  • /relay:inspect

    Inspect an existing Power Platform solution. Maps all components, runs security and quality analysis, and produces a comprehensive audit report. Strictly read-only during inspection. Fix phase is opt-in after the report is reviewed by the user. - relay inspect - inspect solution - inspect existing -

  • /relay:learn

    Extracts patterns from a completed project's execution log and proposes additions to Relay skill files. Learns from what worked and what failed so the squad improves with every project. Run after Phase 7 (complete). - relay learn - extract patterns - update skills - feedback loop

  • /relay:load

    Load project documents into Relay's context before starting. Drop BRDs, wireframes, task lists, data models, emails, or any project file into the context/ folder, then run this command. Scout will read all documents first and ask only about gaps the documents didn't cover — turning a 15-question dis

  • /relay:plan-review

    Force a fresh plan review cycle. Clears existing approvals and re-runs Auditor + Warden + Critic on the current plan.

  • /relay:relay-agent

    Talk directly to a specific Relay agent for a follow-up question, outside the normal workflow.

  • /relay:relay-config

    View or edit Relay configuration — enforcement mode, model overrides, tool limits.

  • /relay:relay-deploy

    Package the solution for deployment. Exports managed solution and prepares for environment promotion.

  • /relay:relay-plan-review

    Force a fresh plan review cycle. Clears existing approvals and re-runs Auditor + Warden + Critic on the current plan.

  • /relay:relay-security-audit

    Run Warden's security verification against the current build on demand, outside the normal workflow.

  • /relay:relay-status

    Show current phase, active agent, blockers, and next step for this Relay project.

  • /relay:security-audit

    Run Warden's security verification against the current build on demand, outside the normal workflow.

  • /relay:start

    Start a new Relay project. Scaffolds the project folder structure and begins discovery with Scout.

  • /relay:status

    Show current project status using real execution data from plan-index.json and execution-log.jsonl. Not a guess — actual system state. - relay status - what phase - where are we - what's done - project status

  • /relay:visualise

    Generate visual diagrams and a stakeholder deck from the project docs. Converts requirements, plan, and security design into Mermaid diagrams (renders in GitHub, Azure DevOps, VS Code). Optionally generates a PowerPoint deck for sharing with business stakeholders. - relay visualise - relay visualize

Subagents (15)

  • analyst

    Existing solution mapper. Reads a deployed Power Platform solution via Dataverse MCP and PAC CLI and produces a complete map of what exists — tables, columns, relationships, security roles, plugins, flows, apps. Used by /relay:analyse before change requests or audits. Produces docs/existing-solution

  • auditor

    Plan completeness and clarity reviewer. Reads docs/plan.md and tears it apart. Asks hard questions. Loops with Drafter via Conductor until there are zero gaps. Does NOT review security — that's Warden's job. - Read - WebSearch

  • critic

    Adversarial reviewer. Red-teams the approved plan and security design after Auditor and Warden have both signed off. Runs a structured footgun checklist first, then goes free-form only if the checklist surfaces issues. Last gate before plan lock. Produces docs/critic-report.md. - Read - Write - WebS

  • drafter

    Power Platform Technical Planner. Writes complete implementation plans with Dataverse schema, app layer, flows, security design, and complete code snippets. Produces docs/plan.md and docs/security-design.md. Invoke after docs/requirements.md is approved. - Read - Write - WebSearch

  • forge-canvas

    Canvas App specialist. Builds Canvas App screens via Canvas Authoring MCP (sync_canvas, compile_canvas). Reads design-system.md for visual tokens and plan.md for screen specifications. Writes .pa.yaml source files. Invoke after plan is locked, Vault has completed schema, and Stylist has produced des

  • forge-flow

    Power Automate flow specialist. Generates Dataverse-shaped flow JSON, creates workflow records via Dataverse API, activates via clientData PATCH on the workflows table, and wires connection references by querying existing connections first. Invoke after plan is locked and Vault has completed schema.

  • forge-mda

    Model-Driven App specialist. Builds MDA sitemap XML, form XML, and deploys via Dataverse API solution export/modify/reimport pattern. Deploys immediately after generating — does not leave files undeployed. Invoke after plan is locked and Vault has completed schema. - Read - Write - Edit - Bash - Web

  • forge-pages

    Power Pages portal specialist. Builds Power Pages portals using the /create-site command from power-pages@power-platform-skills. Invoke after plan is locked and Vault has completed schema. Only invoked when the plan includes a Power Pages portal. - Read - Write - Edit - Bash - WebSearch

  • forge

    Power Platform developer. Builds plugins, code apps, web resources, PCF controls, seed data, and environment variables as specified in docs/plan.md. Uses PAC CLI, Dataverse MCP, and code-apps-preview@power-platform-skills. Automates everything that can be automated. Invoke after plan is locked and V

  • mender

    Fix coordinator for /relay:inspect. Manages the snapshot-fix-verify lifecycle. Captures before-state snapshots, routes findings to the right Forge specialist with user approval per finding, and runs fix verification with regression gating. Handles rollback at both component (surgical) and solution (

  • scout

    Power Platform Business Analyst. Gathers requirements through Socratic discovery, researches the client domain, and produces docs/requirements.md. Invoke when starting a new project or when requirements need re-gathering. - Read - Write - WebSearch

  • sentinel

    Functional tester and code reviewer. Verifies the build against the approved plan. Runs test cases, catches bugs, and loops with Forge via Conductor until everything passes. Produces docs/test-report.md. Invoke after build is complete. - Read - Write - Bash - WebSearch

  • stylist

    Canvas App + MDA UI Designer, wireframe author, MCP Prompt Author, and YAML reviewer. THREE MODES: (1) Wireframe Mode — produces docs/wireframes.html during Phase 2 planning. (2) Design Mode — produces docs/design-system.md with design tokens, screen layouts, structured MCP prompts for Canvas App ge

  • vault

    Dataverse / Data Engineer. Creates tables, columns, relationships, option sets, and security roles in Dataverse using MCP and PAC CLI. Follows the locked plan exactly. Invoke after plan is locked. - Read - Write - Bash - WebSearch

  • warden

    Security Architect for Power Platform solutions. Reviews plan and security design for security gaps. Owns security roles, FLS, DLP analysis, and UI-vs-actual-security traps. Also runs security verification tests after build. Produces docs/security-design.md revisions and docs/security-test-report.md

View source on GitHub

Maintain relay?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted