Use at the start of any development workflow to verify that all required tools and services are available. Caches results to avoid repeated checks.
Verify that all tools required for the development workflow are available before starting work. Cache results to avoid repeating checks in subsequent sessions.
Location:
~/.copilot/preflight-status.json%USERPROFILE%\.copilot\preflight-status.jsonStrategy: If the file exists and lastChecked matches today's date, report
the cached results and ask the user whether to re-run or proceed. Otherwise run
all checks fresh. Before writing the cache file, ensure the .copilot directory
exists under the user's home directory; create it if necessary.
Format:
{
"lastChecked": "<today-iso-date>",
"results": {
"gh": { "available": true },
"intellij": { "available": true, "command": "idea64" },
"figmaMcp": { "available": true },
"jetbrainsMcp": { "available": true },
"docker": { "available": true },
"playwrightCli": { "available": true },
"superpowersPlugin": { "available": true, "version": "4.3.1" }
}
}
Run each check below. Record pass/fail and any metadata noted.
Run gh --version and gh auth status.
gh auth login.Run idea64 --version. If that fails, try idea --version.
idea64 or idea) in the cache under
results.intellij.command — this value is used later to launch IntelliJ.bin directory (or launcher script) is on PATH.C:\Program Files\JetBrains\IntelliJ IDEA <version>\bin./Applications/IntelliJ IDEA.app/Contents/MacOS to PATH.bin directory from the installation (e.g.
/opt/idea-IU-<version>/bin) to PATH.Check whether Figma MCP tools are available in the current tool list (look for
tools with a figma prefix).
Check whether JetBrains MCP tools are available in the current tool list (look
for tools with a jetbrains prefix).
Run docker --version, then docker info (suppress verbose output, e.g.
redirect to /dev/null on Unix/macOS, pipe to Out-Null on PowerShell, or
simply check the exit code).
Run playwright-cli --version (or check the PATH for playwright-cli).
npm install -g @playwright/cli@latest and ensure
playwright-cli is on PATH. See https://github.com/microsoft/playwright-cli
for details. The standalone CLI is required (rather than the Gradle Playwright
task or MCP server) to support parallel smoke testing across multiple
worktrees using named sessions (playwright-cli -s=<name>).Run /plugin list and check whether the superpowers plugin is installed (look
for superpowers@superpowers-marketplace).
Copilot does not auto-update plugins, so version pinning ensures consistency across developers.
4.3.1.cd ~/.copilot/installed-plugins/superpowers-marketplace/superpowers
git fetch --tags --depth=1 origin v4.3.1
git checkout v4.3.1
~ with %USERPROFILE%.)
The user may need to restart the Copilot CLI afterwards./plugin install superpowers-marketplace/superpowers, then pin to the
correct version using the git commands above. The user may need to restart
the Copilot CLI for plugin changes to take effect.When the team agrees to adopt a new version, update the pinned version in this skill and in the cache format below.
After all checks complete:
Tool Status
────────────────── ──────
gh CLI ✓
IntelliJ CLI ✓ (idea64)
Figma MCP ✗ — not connected
JetBrains MCP ✓
Docker ✓
Playwright CLI ✓
Superpowers Plugin ✓