q

Work feedback on an open pull request — the reviewer's comments, questions, and requested changes. Invoke it with a PR number or URL. Given nothing, it resolves the PR for the current branch. Invoke it on a PR carrying no comments too, when the user has revisions of their own. The user rules on every item before anything changes. Agreed fixes are implemented, adversarially reviewed, and delivered to the PR under the review mode the user picks. Replies are posted back on the PR only when the user wants them.

Collaboratively create a plan in docs/plans, grounded in the codebase, hardened by adversarial review, and iterated with the user until it's ready for /q:implement-plan. The argument can be anything from a rough phrase to a detailed writeup. Produces the plan doc — never implements, never commits.

Bring the product or toolchain up and exercise it — to see a change working, or to settle a question only running something can. Name what to exercise. Records what it learned in the project's driving manual. Never fixes what it finds.

Audit the project's whole documentation surface against the documentation policy and consolidate what has drifted. Approved edits ship as a PR. Use when docs feel inflated or stale, after a stretch of merged changes, or on a docs-cleanup request.

Implement a plan from docs/plans end-to-end and open the PR or stacked PRs its delivery call names, with every commit, push, and PR gated by the review mode the user picks up front. Name the plan or give its path.

Install q into a project, or add an extension to one. Invoke bare to set q up; name an extension to install it. Idempotent, safe to re-run on a partially set-up project. The changes ship as a PR.

Give a repo's parallel sessions their own copies of what they contend over while driving — ports, databases, caches, devices. Use when sessions collide over something the repo holds only one of, or to prepare a repo before parallel work starts. Invoke it bare to sweep the repo, or name a resource to scope it. Isolates what can be isolated, names what sessions must take turns over instead, and records both in the driving manual. Changes the repo and ships a PR, escalating to /q:create-plan when the build is plan-sized.

Review anything ad hoc — the session's change, a diff, a file or directory, a doc's prose, a feature, a plan doc — through the project's conventions-grounded adversarial reviewer. The user rules on the findings; approved fixes are applied, and delivery is the user's choice — shipped as their own PR, or left in the working tree for later delivery. Given no target, reviews the session's outstanding change. A finding can indict a convention rather than the artifact — either side may change. Planned work is reviewed inside its own run.

Set up or repair this machine for a q-using project, handing off to /q:install, /q:update, or /q:uninstall-extension when the project's records don't match its pins. Use on a fresh clone or a new machine, or whenever the session-start check says the project's q setup did not validate. Never moves pins and never reconciles docs; the only tracked file it may touch is a lockfile a dependency install rewrites.

Take on unplanned work — an issue, a bug, a task at any fidelity. Ground it in the code, then route it on the user's go-ahead — fix it here in a single adversarially reviewed PR, escalate to /q:create-plan when it's plan-worthy, or show with evidence that nothing needs doing. The expected entry point for work without a plan; planned work runs under /q:implement-plan.

Choose what to work on next from a set of items — a Jira board, GitHub issues, a Notion doc, a file or pasted list — and work through it one pick at a time. Priority guidelines steer the ranking when given ("newest first"). Each agreed pick runs as a /q:tackle cycle in this session, claimed in the source (assignee, status) only with the user's agreement. For a single known item, invoke /q:tackle directly.

Remove a q extension from a project, or reconcile a removal already made out of band — a hand-run npm uninstall, a teammate's merge. Invoke with the extension name. Uninstalls the package, removes its briefing index lines, drops its watermark, and surfaces the project docs that reference it for the user's ruling. Refuses @lab43/q. The changes ship as a PR.

Update q and the project's installed extensions — move pins to the latest releases with the user's go-ahead, reconcile the project's docs with what each release changed, and catch up any pin that moved out of band. Invoked bare it covers q and every installed extension; a named target — q, or an extension — scopes the run. Use after a release ships, or whenever pins may be behind. To audit docs without updating, use groom-docs; to repair this machine without touching docs, use sync. A pin move or catch-up ships as a PR.

Create or update any project documentation — conventions, README, guides, the agent briefing, plan amendments. The argument can be a spelled-out change (applied as given), a rough topic, or nothing — bare invocation sweeps the session for changes worth recording. Invoked directly, the changes ship as a PR; invoked from another skill's run, they join that run's change unless the caller asks for full delivery. Use for any doc change, including a lesson or gotcha worth recording mid-session, even mid-investigation or mid-debugging.

Turn session friction and the project's recorded deviations into upstream PRs against the repos that own the rules — q's own, or a third-party extension's. Use when friction with a q skill, one of q's rules, or an extension's surfaces, when upstream candidates were flagged this session or have accumulated in the project's rulings, or to change how the workflow works.