docs(agents): rely on quest context for shared rules

.claude/rules/prompting.md

@@ -2,8 +2,7 @@
 paths:
   - "**/AGENTS.md"
   - "CONTRIBUTING.md"
-  - "PROMPTING.md"
   - ".claude/skills/**"
 ---
 
-Before editing this file, read `PROMPTING.md` at the repository root and apply it.
+Before editing this file, follow Prompting in `quest context`.

.claude/skills/quest-afk/SKILL.md

@@ -4,4 +4,4 @@ description: Keep quest work moving while the user is away, leaving every decisi
 ---
 
 Run `quest skill afk` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-audit/SKILL.md

@@ -4,4 +4,4 @@ description: Audit and fix outstanding quests for disagreements, conflicts, misa
 ---
 
 Run `quest skill audit` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-complete/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: quest-complete
-description: Decide which open PRs to merge, then merge them in parallel.
+description: Decide which open PRs to merge, then queue them.
 ---
 
 Run `quest skill complete` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-delete/SKILL.md

@@ -4,4 +4,4 @@ description: Abandon a quest.
 ---
 
 Run `quest skill delete` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-export/SKILL.md

@@ -4,4 +4,4 @@ description: Turn active quests into GitHub issues before leaving Quest. Use whe
 ---
 
 Run `quest skill export` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-grill/SKILL.md

@@ -0,0 +1,7 @@
+---
+name: quest-grill
+description: Settle open decisions through an interactive interview with the user. Use when the user invokes /quest-grill or wants unsettled thinking challenged before action.
+---
+
+Run `quest skill grill` and follow its output.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-import/SKILL.md

@@ -4,4 +4,4 @@ description: Import GitHub issues as quests.
 ---
 
 Run `quest skill import` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-iterate/SKILL.md

@@ -4,4 +4,4 @@ description: Iterate on an open PR to settle its open decisions, fix CI and revi
 ---
 
 Run `quest skill iterate` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-merge/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: quest-merge
-description: Merge a quest once reviews and CI pass.
+description: Queue a PR to land, running /quest-iterate first when it needs work.
 ---
 
 Run `quest skill merge` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-plan/SKILL.md

@@ -4,4 +4,4 @@ description: Scope and create quests through an interactive interview. Use when
 ---
 
 Run `quest skill plan` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-recurring/SKILL.md

@@ -4,4 +4,4 @@ description: Plan a quest that repeats, such as a periodic audit or a release cu
 ---
 
 Run `quest skill recurring` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-review/SKILL.md

@@ -0,0 +1,7 @@
+---
+name: quest-review
+description: Review a PR's branch locally with the other vendor's model, then mark it ready for review.
+---
+
+Run `quest skill review` and follow its output.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-spawn/SKILL.md

@@ -4,4 +4,4 @@ description: Start multiple quests in parallel.
 ---
 
 Run `quest skill spawn` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-start/SKILL.md

@@ -4,4 +4,4 @@ description: Start work on a quest.
 ---
 
 Run `quest skill start` and follow its output.
-If `quest` is not installed, follow https://github.com/kixelated/quest/blob/main/SETUP.md first.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

.claude/skills/quest-unblock/SKILL.md

@@ -0,0 +1,7 @@
+---
+name: quest-unblock
+description: Walk the maintainer through every quest and draft PR waiting on them, and clear waits that have resolved.
+---
+
+Run `quest skill unblock` and follow its output.
+If `quest` is not installed, follow https://github.com/moq-dev/quest/blob/main/SETUP.md first.

AGENTS.md

@@ -1,42 +1,15 @@
 Read `README.md` for the three sites (moq.dev, moq.pub, moq.watch), setup, and the broadcast URL scheme.
 
-# Required
+# Rules
 
-- Dig into the root cause and fix it at the source. Never work around a fixable bug with a retry, sleep, or timeout.
-- Fail loud and early. Error on unsupported or malformed input rather than warn and continue.
-- Reproduce bugs before fixing them. Land each fix with a regression test that fails without it, when one is easy.
-- Keep the PR focused. No unrelated refactors, formatting churn, or drive-by changes; split when in doubt.
-- Refactor aggressively for long-term maintainability, but re-evaluate the direction as you learn.
-- Propose a course change, even suggest abandoning a PR, rather than finish a half-solution.
-- When a decision is the maintainer's (design, copy, naming, scope), ask with 2-3 options and a recommendation.
 - Never deploy to any environment, including staging, without the user's explicit permission for that deployment. A coding task or quest does not authorize a deploy.
 - Protocol, player, and publisher fixes belong upstream in moq-dev/moq (`@moq/publish`, `@moq/watch`, ...). Fix them there first, then bump the `moq` submodule here; the `@moq/*` packages build from it.
-- Never edit an `AGENTS.md`, `PROMPTING.md`, or skill without being prompted. Read `PROMPTING.md` before editing one or instructing other agents via context, memory, plans, or reviews.
-- No em dashes in code, comments, or agent-written prose.
-- Match the existing conventions, patterns, and naming when possible.
-- Fix any outdated docs and comments inline; don't add a separate PR for it.
-- Add the AI marker `(Written by <model>)` to any posts on GitHub, excluding commit messages that contain `Co-Authored-By:` trailers.
-- Any AI comments may be challenged, and not confused with human maintainers.
-
-# Guidelines
-
-- Comments should explain the non-obvious why, and never the history.
-- Inline simple helpers.
-- Question whether functionality is needed at all before adding it.
-- Deleting code is better than adding code.
-- Prefer the simple solution.
-- New dependencies use the newest stable version.
-- Say it once, in the fewest words that hold up.
-- Suggest follow up sessions and quests when finished, interactively prompting the user.
-- Prefer a quest over a GitHub issue for work needing durable scope.
-- Try to do stuff asynchronously. ex. ask about follow-ups while checks run.
-- If the core problem is addressed, ship it instead of spinning your wheels on meaningless revisions.
 
 # Development
 
-PRs target `main`. Before starting, `git fetch origin` and set the upstream to the base branch.
-`git stash` is one stack shared by every worktree; set work aside with a commit instead.
-Use the Nix dev shell (direnv, or `nix develop --command just ...`) so tooling matches CI.
+PRs target `main`.
 Run `just fix` before committing. `just check` alone is not verification: look at the change in the dev server (`just dev`, `just dev-pub`, or `just dev-watch`).
 Hand-drawn art ships as SVG: `just trace` the drawn PNG, compare the two, then commit only the SVG.
-Quests: before starting work, run `quest guide` and follow it. The `quest` binary comes from the kixelated/quest flake input and serves the quest skills; change them upstream and bump the input.
+
+Quests: before any work, run `quest context` and follow it.
+The `quest` binary comes from the moq-dev/quest flake input and serves the quest skills; change them upstream and bump the input.

flake.nix

@@ -8,7 +8,7 @@
     # The quest CLI, which also serves the quest guide and skills the stubs in
     # .claude/skills call. Bump the rev to upgrade them.
     quest = {
-      url = "github:kixelated/quest/ed657ba9362a941b3be9bbea55120a3c5a90374c";
+      url = "github:moq-dev/quest/4be350816f2a5c1157f799773ee1594f199fd9a7";
       inputs.nixpkgs.follows = "nixpkgs";
       inputs.flake-utils.follows = "flake-utils";
     };