supertaskr-seat

Orchestrates dispatch, blind verification, verdict, and merge of task cards in Supertaskr projects.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/juhosarvanco/supertaskr --skill supertaskr-seat-juhosarvanco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supertaskr-seat
Source: https://github.com/juhosarvanco/supertaskr/tree/main/method/skills/supertaskr-seat
Command: npx skills add https://github.com/juhosarvanco/supertaskr --skill supertaskr-seat-juhosarvanco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Coordinating parallel AI agents on one repository without collisions, unverified merges, or lost context is hard. This Skill encodes the architect's seat for a Supertaskr project: it derives what work is startable, dispatches lanes through a single eight-step arm, enforces blind two-spawn verification, and governs the verdict, merge, checkpoint, and push so every landing leaves the same auditable files. ## Core Features & Use Cases - Derived dispatch view: Computes live lanes and startable cards from git worktrees and the board before stamping, never from stale status fields. - One-arm dispatch: Runs the eight-step dispatch arm (stamp, cut lane, preflight, fence manifest, bench, brief, port derivation) that refuses at the first failing step, with a --dry-run plan mode. - Blind verification protocol: Spawns the verifier in two phases where the attack plan is written before the diff exists, with hashed attack sets cited in the verdict. - Self-checking tooling: Ships golden-check.mjs and host-command-check.mjs, zero-dependency Node scripts that compare landed artifacts field-by-field against a golden contract and verify every command is transcribed from project conventions. - Use Case: You ask what to work on next in a Supertaskr repo; the skill derives the dispatch view, triages suggestions, audits the card's claims, dispatches the lane, and lands it with a verdict. ## Quick Start Open a Supertaskr project and ask the agent to dispatch the next startable card using the supertaskr-seat skill.

Frequently Asked Questions about supertaskr-seat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dispatch a task card to a parallel agent lane?

Run the dispatch arm, which performs eight ordered steps: stamp the card on the integration branch, cut the lane worktree, re-derive the card's claims, expand the fence manifest, cut the verifier bench, assemble the brief, and derive the port. It refuses at the first failing step and supports --dry-run.

How does blind verification of AI-generated code work?

The verifier runs as two separate spawns: phase 1 writes an attack plan from the card at the base ref before any diff exists, and phase 2 evaluates the lane's tip. The attack set is saved and hashed, and the verdict cites that digest; a mismatched digest refuses the verdict.

Can multiple AI agents work on one git repository without conflicts?

Yes, when each card declares the files it touches and every lane gets its own branch, worktree, and write fence. Two lanes run concurrently only when their expanded write sets are proved disjoint, and the fence manifest is checked against the card's touches line.

What projects can use the supertaskr-seat skill?

Only Supertaskr projects, detected by the presence of docs/STATE.md and a method/ directory. The skill works in both Claude and Codex harnesses by placing the pack directory under .claude/skills/ or .codex/skills/, and adopting projects rewrite only the host-commands.md reference.

When is the quick path not allowed for small changes?

The quick path is refused when the card's subject is a guard, such as a hook, gate, lint, or permission check, because guard-class cards require independent review. Every merge still requires a card and a verdict; the quick path only makes the card cheaper.