rigortype/rigor/rigor-queue-survey

Claude Code and agent skill by rigortype/rigor

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Collect rigor-survey coverage holes and work them sequentially in an interactive pi session (/queue-survey). USE FOR: 「カバレッジの穴を収集」, 「順次着手」, survey coverage queue, fill survey holes, spawn rigor-lane subagents with disjoint survey targets. DO NOT USE FOR: parallel measurement on a shared survey checkout, release pre-clear (use rigor-queue-release), or cutting a gem release.

Install

npx vskill@latest install rigortype/rigor/rigor-queue-survey

SKILL.md

Rigor queue — survey coverage

Orchestrator-led, multi-turn, in-session queue. Primary entry: user runs pi in the Rigor repo (packages in .pi/settings.json) then /queue-survey or /skill:rigor-queue-survey. Same project session continues with pi -c.

Not a one-shot architect→lane.

See also: `../../roles/orchestrator.md`, `../../contracts/README.md` (QueueTurn), project agents under .pi/agents/ (rigor-lane, rigor-reviewer).

Requires project package npm:pi-subagents (listed in .pi/settings.json).

Hard rules (always)

  • Survey targets under measurement need disjoint checkouts; never share a

measuring target across agents. Encode this in every spawn / LaneInput.

  • Managed worktree of *rigor* ≠ survey exclusivity. A pi-subagents managed

worktree isolates the rigor implementation checkout only. It does not satisfy exclusivity of survey measurement trees such as ~/repo/ruby/rigor-survey/<project> (or /Users/megurine/repo/ruby/rigor-survey/<project>). Each measuring agent still needs its own disjoint survey target checkout; put that path in every LaneInput / spawn task.

  • Default survey root: ~/repo/ruby/rigor-survey (or

/Users/megurine/repo/ruby/rigor-survey). Ask if unclear; accept a path from the user.

  • Prefer filing or linking Issues for holes (ADR-98), then sequential着手.
  • Lanes: push head SHA and stop; this parent owns CI. No parallel host

make verify.

  • GitHub API: sparse CI polls (gh pr view --json statusCheckRollup), ≤1/min/PR.
  • Managed worktree fanout needs a clean source rigor checkout. Do not

auto-merge worktree patches without a human.

Turn protocol (in this same session)

Every turn:

  1. Restate queue goal + constraints (survey root; disjoint survey target

rule — separate from rigor managed worktrees).

  1. Show ranked backlog of coverage holes with evidence (survey paths,

gh issue links). Prefer Issues over ad-hoc path lists when possible.

  1. Propose exactly one next unit of work (unless parallel spawn requested).
  2. Wait for user: next / do #N / skip / stop

(JA: 次 / やる #N / スキップ / 止めて / ストップ). Also accept spawn / spawn N / 全部やれ / parallel.

  1. On go — prefer pi-subagents spawn (include disjoint survey target path

in every LaneInput). Managed worktree: true applies to the rigor repo only; still assign unique survey checkouts.

Caveat: use workflowScript + runs.run / runs.all for worktree: true (documented path). Direct { agent, task, worktree: true } is not the documented isolation path.

Single:

``text subagent({ async: true, worktree: true, workflowScript: return runs.run("lane", { agent: "rigor-lane", task: args.task, worktree: true }) , args: { task: "<LaneInput including disjoint survey target path>" } }) ``

Parallel (spawn N / 全部やれ / parallel):

``text subagent({ async: true, worktree: true, workflowScript: return runs.all([ { key: "h1", agent: "rigor-lane", task: args.t1, worktree: true }, { key: "h2", agent: "rigor-lane", task: args.t2, worktree: true } ]) , args: { t1: "<LaneInput + survey checkout A>", t2: "<LaneInput + survey checkout B>" } }) ``

Fallback if pi-subagents unavailable: LaneInput + ./agents/pi-harness/scripts/run-role.sh lane with disjoint targets.

  1. After children return: collect head SHAs / handoff manifests; parent

owns sparse CI polls; children must not CI-watch. Refresh queue, print Queue: N remaining | Next candidate: … | say next/stop.

  1. Stay in this session — no wrapper restart. Resume with pi -c then

/queue-survey if needed.

When to call architect / lane vs stay here

Stay in this sessionHand off
Collecting holes, ranking, proposing next unitArchitect: when a hole needs a fixed LaneInput
Filing/linking Issues for holesLane: prefer subagent → rigor-lane + rigor worktree and disjoint survey checkout; fallback run-role.sh lane
Waiting on next/skip/stop / spawnParallel measuring agents: unique survey targets always

Finish phrases

  • After proposing: wait for user.
  • Empty / stop: Survey holes cleared for now or

Queue paused — resume with pi -c then /queue-survey

  • Blocked: Blocked — need human

Non-goals

  • Not sharing one measuring survey target across agents
  • Not treating a rigor managed worktree as a substitute for survey exclusivity
  • Not parallel host make verify or long CI sleep loops
  • Not a one-shot architect→lane without the wait step
  • Not inventing a backlog outside Issues when an Issue can be filed (ADR-98)
  • Not auto-merging managed worktree patches without a human

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/rigortype/rigor/rigor-queue-survey/badge)](https://verified-skill.com/skills/rigortype/rigor/rigor-queue-survey)

Something wrong with this skill or its page? Tell us.