relay

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

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.

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 built by Relay.

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.

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.

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.md.

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.

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.

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.

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 design-system.md.

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. Reference whenever designing or reviewing Canvas App UI.

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.

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. Stylist decides whether to use this pattern after reading the project context or analyzing the user's reference screenshot.

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.

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.