RapidSpec: Resolve Parallel

A task-runner command that reads a RapidSpec change's task list, works out which tasks depend on each other, and handles independent tasks at the same time.

In plain words
What is it for?
Use it to carry out unfinished tasks in a RapidSpec change, while respecting file, creation, and stated task dependencies.
Why use it?
It prevents tasks from running in the wrong order or interfering with each other when several tasks are ready. It also keeps the task list updated as work is finished.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/9j/rapidspec/resolve-parallel
Clone the repo
git clone --depth 1 https://github.com/9j/RapidSpec
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,963 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.02963
Opus 5 $0.00007 $0.01482
Sonnet 5 $0.00003 $0.00593
Haiku 4.5 $0.00001 $0.00296

Measured yesterday against content hash f34d1061cfc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

RapidSpec: Resolve Parallel scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/resolve-parallel.md · 449 lines

How it starts

The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resolve Tasks in Parallel

<command_purpose> Analyze uncompleted tasks in tasks.md, identify dependencies, and execute multiple tasks in parallel for maximum efficiency. Automatically handles task ordering based on dependencies. </command_purpose>

<change_id> #$ARGUMENTS </change_id>

<critical_requirement> MUST analyze task dependencies before execution. MUST execute independent tasks in parallel. MUST update tasks.md after each task completion. NEVER execute dependent tasks simultaneously. </critical_requirement>

Main Tasks

1. Read and Analyze Tasks (ALWAYS FIRST)

Immediate Actions:

  • Read rapidspec/changes/<change-id>/tasks.md
  • Identify uncompleted tasks (marked with - [ ])
  • Extract task descriptions, sections, and checkpoints
  • Count total uncompleted tasks

2. Dependency Analysis

Dependency Rules:

  1. File Dependencies

    • If Task A and Task B modify the same file → Sequential
    • If Task A creates file that Task B uses → Sequential (A before B)
  2. Logical Dependencies

    • If Task B description mentions Task A → Sequential (A before B)
    • If Task requires "after X" → Sequential
  3. Section Dependencies

    • Critical fixes (Section 0) → Run first
    • Implementation sections → Can often run in parallel
    • Testing/Validation → Usually run after implementation
  4. Database Dependencies

    • Migrations must run in order
    • Schema changes before queries using new schema

Dependency Detection:

Check each task for:

  • File references: src/app/api/route.ts
  • "After Task X.Y" mentions
  • "Depends on" explicit markers
  • Logical flow (migration → RLS → queries)

Read the full file on GitHub · 449 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 449 lines · 0 tokens per session scan A f34d1061cfc5

Subscribe to this mod's changes

RapidSpec: Resolve Parallel is a command published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 9mo ago), licensed MIT. It adds 14 tokens to every session and 2,963 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.