agentmods.dev

spec-to-board

spec-to-board is a skill for Claude Code from UrRhb/agentflow. It costs 37 tokens per session (1,292 once invoked), scanned C, a copy of spec-to-board, MIT.

A procedure that turns a product specification into a Kanban board—a board of work items grouped by progress—with small tasks, dependencies, and acceptance criteria.

In plain words
What is it for?
Use it to read or create a SPEC.md, inspect project conventions and files, set up a project, and create tasks in Asana or another supported board system.
Why use it?
It breaks a broad specification into trackable work and adapts the board setup to the project-management tool that is available.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the agentflow plugin — 6 skills, 4 agents, 1 MCP server shipped together

not rated 5repo 6mo ago C scan 37 tokens copy · 100% MIT

Good fit Use it to read or create a SPEC.md, inspect project conventions and files, set up a project, and create tasks in Asana or another supported board system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/urrhb/agentflow/spec-to-board
View source ↗ UrRhb/agentflow
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 UrRhb/agentflow --skill spec-to-board
Clone the repo
git clone --depth 1 https://github.com/UrRhb/agentflow

Made for: Claude Code.

Or install agentflow, the plugin that ships this one along with the rest of its 6 skills, 4 agents, 1 MCP server.

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 spec-to-board

README.md
[![agentmods](https://agentmods.dev/badge/skills/urrhb/agentflow/spec-to-board/github.svg)](https://agentmods.dev/skills/urrhb/agentflow/spec-to-board)
Your own site
<a href="https://agentmods.dev/skills/urrhb/agentflow/spec-to-board"><img src="https://agentmods.dev/badge/skills/urrhb/agentflow/spec-to-board/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 spec-to-board

Your own site · 80×15
<a href="https://agentmods.dev/skills/urrhb/agentflow/spec-to-board"><img src="https://agentmods.dev/badge/skills/urrhb/agentflow/spec-to-board.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,292 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00037 $0.01292
Opus 5.5 $0.00015 $0.00517
Sonnet 5.5 $0.00007 $0.00258
Haiku 4.5 $0.00004 $0.00129

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

Security

Grade C, and why

spec-to-board scanned grade C with 2 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

6. **Safety check**: All verification commands use only safe commands (npm, npx, node, curl localhost). No external URLs, no `rm -rf`, no `eval`, no `sudo`.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

6. **Safety check**: All verification commands use only safe commands (npm, npx, node, curl localhost). No external URLs, no `rm -rf`, no `eval`, no `sudo`.
Origin

This is a copy

100% identical to spec-to-board — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugin/skills/spec-to-board/SKILL.md · 173 lines

How it starts

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

/spec-to-board

Convert a product spec into a fully structured Kanban project board for the AgentFlow pipeline.

PM Tool Detection

This skill works with any supported PM tool. It detects which MCP is available:

  • If Asana MCP connected: use Asana operations
  • If GitHub Projects MCP connected: use GitHub Projects operations (future)
  • If none: report error and suggest configuring MCP

The skill uses adapter-neutral language. See core/adapters/interface.md for mapping.

Prerequisites

Before running, you need:

  1. A SPEC.md file (or a product idea to brainstorm into one)
  2. Access to your PM tool's MCP integration (e.g., Asana MCP)
  3. The AgentFlow conventions: read conventions.md

Process

Phase 1: Spec Acquisition

If a SPEC.md path is provided as argument, read it.

If no argument provided, ask the user:

  • "What product/feature are you building?"
  • Help create a SPEC.md
  • Save to a docs/specs/ directory

Phase 2: Project Setup

  1. Determine project code: Check conventions.md for existing codes. If new project, ask user for 3-letter code.

  2. Read the project's file structure:

    Glob: **/*.ts, **/*.tsx, **/*.js pattern in the project directory

    This gives predicted files context for decomposition.

  3. Read package.json: Get current dependencies (needed for research trigger evaluation).

  4. Select model cost profile: Ask the user: "Which Claude model will workers use? (sonnet/opus)" This sets the cost profile in conventions.md (affects cost ceilings and guardrails).

Phase 3: Decompose

Read the decomposition prompt: prompts/decompose.md

For each phase/section in the SPEC.md:

  1. Break into atomic tasks following the decomposition rules
  2. Map dependencies between tasks
  3. Evaluate research triggers per task
  4. Detect and resolve shared-file conflicts

Phase 4: Validate

Run the decomposition validator (from decompose.md) BEFORE creating anything in the PM tool:

  1. Rubric check: All 9 fields present per task
  2. Topological sort: No circular dependencies
  3. File conflict check: Parallel tasks don't share files
  4. Atomicity check: No task modifies > 5 files
  5. Verification command check: All commands are valid bash
  6. Safety check: All verification commands use only safe commands (npm, npx, node, curl localhost). No external URLs, no rm -rf, no eval, no sudo.

Read the full file on GitHub · 173 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. 1mo ago First seen · 173 lines · 37 tokens per session scan C 3d045c444ccf

Subscribe to this mod's changes

spec-to-board is a skill published in the GitHub repository UrRhb/agentflow (5 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 1,292 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). It is 100% identical to spec-to-board, differing in 0 lines, and is treated as a copy.

PlanningProject management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens