power-platform-developer-suite

Cut a PPDS release — CHANGELOG refresh, version bump, tag push sequence, CI monitoring, post-publish verification. Use when preparing a new prerelease or stable release across CLI, TUI, MCP, Extension, and NuGet libraries.

Triage and merge open dependabot PRs per docs/MERGE-POLICY.md — classify each PR (auto-merge / verify-then-merge / manual review), enable auto-merge for safe ones, run targeted test suites for risky ones, and surface anything needing human judgment. Use when there's a backlog of dependabot PRs, after a quiet period, or as a routine drain.

AI self-verification of implemented work across surfaces (extension, CLI, MCP, TUI, workflow). Use after implementation to verify code works in its runtime environment.

Create, triage, and manage GitHub issues per PPDS backlog conventions. Use when creating issues, grooming the backlog, reviewing what to work on next, or filing bugs.

Brainstorm ideas into specs and plans through collaborative dialogue. Use when starting a new feature, exploring an idea, or designing a system — before any implementation.

Gates

Execute a checked-in implementation plan end-to-end using parallel agents. Use when a spec and plan exist in .plans/ and you're ready to build.

Create PR, wait for the configured automated review, triage every comment, and present a summary. Use when work is ready to ship — after gates, verify, QA, and review are complete.

QA — Three-Agent Blind Verification. Use when making code changes that need product-level validation — after implementation, after fix rounds, before PRs. Dispatches agents that test the running product without seeing source code.

Bias-isolated code review — reviewer sees only the diff, constitution, and spec ACs, never the implementation plan or task context

Setup

Structured multi-surface product validation — systematically test Extension, TUI, MCP, and CLI with parity comparison and architecture audit. Use before releases, after large features, or to kick the tires.

Author or modify skills following PPDS conventions — naming, structure, frontmatter, discoverability. Use when creating, editing, or restructuring skills.

Run manifest-driven PNG captures of TUI and extension surfaces for design audits. Emits a schema-conformant capture tree for consumption by a Claude design-audit session.

Interactive debugging with systematic root-cause analysis. Use when encountering any bug, test failure, or unexpected behavior — before proposing fixes.

Building or modifying VS Code webview panels and multi-surface panel features. Use when creating new panels, adding features to existing panels, designing panel architecture across Extension/TUI/MCP/CLI.

PPDS test conventions — which test framework to use per area, trait categories, file placement, coverage bar. Use when writing or organizing tests across .NET, TypeScript, or MCP code.

Spec Audit

Spec