agentmods.dev

implementing-tasks

implementing-tasks is a skill for Claude Code from prime-radiant-inc/iterative-development. It costs 45 tokens per session (1,108 once invoked), scanned A, original, Apache-2.0.

A task-execution workflow that assigns each small development task to an implementation agent and checks the result against the specification and code-quality rules. TDD, or test-driven development, means writing a failing test before the code that makes it pass.

In plain words
What is it for?
Use it inside an active development iteration to implement a batch of TDD-sized tasks. It maps requirements to tests or other evidence, performs specification and quality reviews, and reports completion for each task.
Why use it?
It reduces the chance that a task is implemented without covering its required behavior or without review. Failed checks lead to a fix cycle before the task is marked complete.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the iterative-development plugin — 6 skills shipped together

not rated 183repo +1 5mo ago A scan 45 tokens original Apache-2.0

Good fit Use it inside an active development iteration to implement a batch of TDD-sized tasks. It maps requirements to tests or other evidence, performs specification and quality reviews, and reports completion for each task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/prime-radiant-inc/iterative-development/implementing-tasks
View source ↗ prime-radiant-inc/iterative-development
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.

Any agent
npx skills add prime-radiant-inc/iterative-development --skill implementing-tasks
Clone the repo
git clone --depth 1 https://github.com/prime-radiant-inc/iterative-development

Made for: Claude Code.

Or install iterative-development, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for implementing-tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/prime-radiant-inc/iterative-development/implementing-tasks/github.svg)](https://agentmods.dev/skills/prime-radiant-inc/iterative-development/implementing-tasks)
Your own site
<a href="https://agentmods.dev/skills/prime-radiant-inc/iterative-development/implementing-tasks"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/iterative-development/implementing-tasks/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for implementing-tasks

Your own site · 80×15
<a href="https://agentmods.dev/skills/prime-radiant-inc/iterative-development/implementing-tasks"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/iterative-development/implementing-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,108 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00045 $0.01108
Opus 5.5 $0.00018 $0.00443
Sonnet 5.5 $0.00009 $0.00222
Haiku 4.5 $0.00005 $0.00111

Measured 2mo ago against content hash 708537255c4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implementing-tasks 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 2mo ago.

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.

skills/implementing-tasks/SKILL.md · 112 lines

How it starts

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

Implementing Tasks

Overview

Takes an in-memory batch of TDD-sized tasks and executes each through: implementer subagent (TDD) → PAR spec-compliance review → fix loop → PAR code-quality review with boxing-in check → fix loop → mark complete. This is a fork of superpowers:subagent-driven-development with the plan-file reading phase stripped and the final end-of-plan reviewer removed.

When to Use

Invoked by running-an-iteration with a list of tasks. Tasks are passed in memory, not via a file.

Per-Task Cycle

For each task in the provided list:

1. Dispatch implementer

Using the template in implementer-subagent-prompt.md, dispatch a single implementer subagent with:

  • The full task description and context
  • The proof obligations for each observable AC in the task's stories
  • The list of existing scenarios that may be impacted

The implementer MUST complete a pre-flight mapping (AC → proof seam → scenario) before writing code. If the implementer skips the pre-flight, re-dispatch with explicit instructions to complete it first.

2. Handle implementer status

  • DONE: proceed to spec-compliance review (step 3). Verify the implementer's report includes pre-flight mapping and scenario updates.
  • DONE_WITH_CONCERNS: read the concerns. If about correctness/scope, address before review. If observations, note and proceed.
  • NEEDS_CONTEXT: provide the missing context and re-dispatch
  • BLOCKED: assess: context problem → re-dispatch with context; too hard → re-dispatch with more capable model; task too large → break into smaller pieces; plan wrong → escalate to caller

3. PAR spec-compliance review (Stage 1)

Following skills/shared/parallel-adversarial-review.md:

  1. Build spec-compliance prompt using spec-compliance-reviewer-prompt.md
    • Include the proof obligations and the implementer's evidence claims
  2. Wrap in PAR competitive framing from skills/shared/par-reviewer-wrapper.md
  3. Dispatch TWO spec-compliance reviewers in parallel
  4. Aggregate findings (PAR rules: union of findings, severity = take worst)
  5. If ❌ issues found:
    • Send aggregated issues back to the implementer subagent (same subagent, via continuation message)
    • Implementer fixes
    • Re-dispatch fresh PAR spec-compliance pair
    • Repeat until ✅ spec compliant with adequate evidence
  6. Only proceed to Stage 2 after Stage 1 is ✅

Read the full file on GitHub · 112 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 112 lines · 45 tokens per session scan A 708537255c4e

Subscribe to this mod's changes

implementing-tasks is a skill published in the GitHub repository prime-radiant-inc/iterative-development (183 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,108 once invoked, about $0.0002 per session on Opus 5.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-30.

Autonomous AgentsClaude CodePlanningTDDTestingai-agentsclaude-code-pluginmethodology
Related

implementing-tasks compared with skills from other repositories

implementing-tasks next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
implementing-tasksprime-radiant-inc/iterative-developmentSkill1835mo agoApache-2.0A45Claude Code
mutation-testingvmobifystudio/app-dev-teamSkill54d agoMITA83Claude Code
sparc-methodologyruvnet/RuViewSkill103kyesterdayMITA29Claude Code
buildingromiluz13/cc10xSkill16616d agoMITA43Claude Code
tdd-workflowmakifbaysal/tasktrooperSkill12016d agoApache-2.0A38Claude Code, Codex
V3 Security Overhaulruvnet/rufloSkill81kyesterdayMITA52Claude Code
tdd-cyclemodimihir07/agentic-osSkill21715d agoMITA14Claude Code, Codex