patleeman

Use when deciding between follow-up queues, scheduled callbacks, automation-owned attention, wakeups, and async follow-up surfaces.

Use when a task benefits from JavaScript orchestration, explicit phases, structured progress logs, parallel fanout, or multiple daemon-backed subagents coordinated through the workflow tool.

Use when starting, inspecting, rerunning, following up, or cancelling durable background commands or subagents.

Use when designing, creating, editing, building, validating, installing, or debugging Neon Pilot extensions, application pages, contributions to existing applications, or complete first-class applications from the bundled desktop app. This skill is self-contained and must be used without a Neon Pilot source checkout.

Use when working with the built-in desktop Workbench Browser, browser comments, browser snapshots, CDP actions, screenshots, or the browser versus agent-browser boundary.

Use the unified Neon Pilot CLI/control plane for self-administration, delegated agent control, conversations, workspace/sidebar state, runs, automations, extensions, settings, and extension-contributed administration surfaces.

Use when installing, inspecting, or explaining Codex and Claude Code style agent plugins in Neon Pilot.

Use when controlling native desktop applications through Cua Driver. Prefer browser tools for web-only tasks.

Use task-factory CLI commands to manage workspaces, tasks, and workflows. Use when the user needs to create tasks, manage task execution, check queue status, or work with the Task Factory system via CLI.

Capture a browser screenshot for task validation and attach it to the active task using attach_task_file.

Create a branch, commit all agent changes, push, and open a pull request. Use when work is ready for review and should be submitted as a PR rather than just checkpointed.

Commit and push the agent's current work without opening a PR. Stages only files modified by the agent, creates a descriptive commit message, and pushes to the current branch.

Review all code changes for bugs, edge cases, naming, complexity, and missing error handling. Use after completing implementation work to catch issues before marking a task complete.

Repeatedly check if there is more work to do until the task is truly complete. Use after implementation to ensure nothing was missed against the acceptance criteria.

Scan code changes for security vulnerabilities including OWASP Top 10, hardcoded secrets, injection flaws, and authentication issues. Use after implementation to catch security problems before marking a task complete.

Enforce test-first behavior before implementation by writing or updating tests and running them in pre-execution.