lbruton

Use when starting a new patch session and needing to pick a Plane issue to work on before claiming a version lock and creating a worktree.

Use when starting a new patch session and needing to pick a Plane issue to work on before claiming a version lock and creating a worktree.

Post-deploy verification for both Portainer (home) and Fly.io (cloud) environments. Runs environment-appropriate health checks, log inspection, env var verification, cron validation, and endpoint smoke tests. Covers the gap between "deploy succeeded" and "deploy actually works." Triggers on: "deploy verify", "post-deploy", "verify deploy", "smoke test deploy", "did the deploy work", "check the deploy", "/deploy-verify"

StakTrakr-specific Phase 1 version bump — edits 6 files, trims What's New, delegates sw.js to pre-commit hook.

API feeds, pollers, feed thresholds, data paths, StakTrakrApi structure, Fly.io and health badge issues.

Ship dev→main — PR, resolve threads, GitHub Release. Only on explicit user "ready to ship".

Use when adding, editing, or removing StakTrakr in-app FAQ entries in the Settings FAQ tab, including known or honest limitation copy.

Guide branch completion — structured options for merge, PR, or cleanup when implementation is done.

Spec-driven development orchestrator. Creates and executes spec-workflow specifications from an issue — Requirements → Design → Tasks → Implementation with dashboard approvals and subagent dispatch.

Run the i18n validation script to check for missing, extra, or misformatted translation keys before publishing

On-demand project health check — code quality (CGC), security (Codacy SRM), instruction file drift (CLAUDE.md vs Agents.md vs Gemini.md), issue landscape, index health. Triggers: "audit", "health check", "check project health", "scan codebase", "code health", "instruction drift", "check for drift".

Casual, freeform discovery mode (Phase 0 of the Spec Flow Lifecycle). Explore an idea without committing to code, issues, or specs. Dispatch subagents for research, surface past work from mem0, and build context until the idea is ready for an issue and formal spec. Triggers on "/chat", "/talk", "let's explore", "I have an idea", "what if we".

Structured brainstorm and research phase (Phase 1 of the Spec Flow Lifecycle). Takes an issue ID, dispatches research agents, runs codebase analysis, and produces a Discovery Brief with all open questions resolved. Bridges the gap between casual exploration (/chat) and formal spec creation (/spec). Triggers on "/discover", "/brainstorm", "research this issue", "explore this before we spec it".

Issue management — create, read, update, list. Backend is driven by `.specflow/config.json` `issue_backend` field: `plane` (Plane MCP, primary going forward) or `docvault` (legacy markdown — for projects not yet migrated). Triggers on: "create issue", "issue", "new issue", "new bug", "file a bug", "track this".

Migrate a user-level skill into the specflow plugin's skills directory. Use when porting a proven skill from ~/.claude/skills/ to the plugin for distribution. Covers generic vs project-specific classification, MCP prompt extraction, deprecation of user-level shims, and verification.

Universal session boot — indexes code, digests past sessions, checks code health, gathers project status, and presents a unified startup report. Works on any project with a .claude/project.json. Run at the start of every session. Triggers: "prime", "boot", "get me up to speed", "session status", "where are we", "what's the status", "catch me up", "project overview", "what's open". Also use proactively at session start if the user hasn't run it yet.

Forge-specific release override — Phase 1 version bump recipe for package.json, version.lock, and CHANGELOG.md.