agentmods.dev

spec-flow

spec-flow is a skill for Claude Code, Codex from alexei-led/cc-thingz. It costs 71 tokens per session (1,178 once invoked), scanned A, original, MIT.

A lightweight workflow for planning and carrying out software changes one small, checkable task at a time, using Markdown files to track requirements and progress.

In plain words
What is it for?
Use it for spec-driven development: plan a task, implement it, record progress, and close or resume the work through the bundled command-line helper.
Why use it?
It prevents a large change from becoming an unclear list of unfinished work. Checkpoints make it easier to stop and resume without losing the current state.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 35repo 1mo ago A scan SkillSpector: pass 71 tokens original MIT

Good fit Use it for spec-driven development: plan a task, implement it, record progress, and close or resume the work through the bundled command-line helper.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alexei-led/cc-thingz/spec-flow
View source ↗ alexei-led/cc-thingz
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 alexei-led/cc-thingz --skill spec-flow
Clone the repo
git clone --depth 1 https://github.com/alexei-led/cc-thingz

Made for: Claude Code, Codex.

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-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/alexei-led/cc-thingz/spec-flow.svg)](https://agentmods.dev/skills/alexei-led/cc-thingz/spec-flow)
Your own site
<a href="https://agentmods.dev/skills/alexei-led/cc-thingz/spec-flow"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/spec-flow.svg" alt="Measured on agentmods" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,178 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00071 $0.01178
Opus 5 $0.00036 $0.00589
Sonnet 5 $0.00014 $0.00236
Haiku 4.5 $0.00007 $0.00118

Measured 8d ago against content hash 10f71a7d744d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

spec-flow 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/specctl.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

src/skills/spec-flow/SKILL.md · 161 lines

How it starts

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

Spec flow

Lightweight spec loop for controlled task-by-task work.

Loop: plan one slice → execute one task → checkpoint or close → repeat.

specctl owns state. Do not edit task status or .spec/SESSION.yaml by hand.

Read first

  • references/method.md for artifact shapes, planning rules, task quality, and mini-interview guidance.
  • references/specctl-commands.md for CLI commands.

State model

  • .spec/tasks/TASK-*.md — executable vertical slices. Required for work.
  • .spec/epics/EPIC-*.md — optional group for multi-task plans.
  • .spec/reqs/REQ-*.md — optional WHY/WHAT context for ambiguous work.
  • .spec/SESSION.yaml — active task, step, base commit.
  • .spec/PROGRESS.md — append-only activity log.

Task states: todo, in-progress, done.

Common flows

New project:

scripts/specctl init

Then plan the first executable slice. Do not build a full backlog unless the user asks.

Existing project:

  1. Inspect current code and project instructions.
  2. Create the smallest task that can be verified.
  3. Link optional REQ/EPIC context only when it reduces ambiguity.

Stop and resume:

scripts/specctl checkpoint --message "<where to resume>"
scripts/specctl session handoff

Iterate:

scripts/specctl ready
scripts/specctl start TASK-<id>
# implement + verify
scripts/specctl done TASK-<id> --summary "..." --tests "..."

Modes

Orient

Use when the user asks for status, next task, resume, health, or what to do next.

scripts/specctl status
scripts/specctl ready
scripts/specctl session handoff
scripts/specctl validate

Report active session, next ready task, validation issues, and the smallest next action.

Plan

Use when the user has an idea, requirement, bug, or project gap and wants an executable plan.

  1. Run scripts/specctl init.
  2. Check status/session before changing files.
  3. Ask 3-5 questions only if the slice is unclear.
  4. Optionally scan the codebase for relevant files and patterns.
  5. Draft the smallest useful artifact set:
    • one clear slice → one TASK-*
    • several slices → one EPIC-* plus tasks
    • unclear WHY/WHAT → one REQ-* first
  6. Show the proposed plan and ask before writing.
  7. Write with scripts/specctl new task <slug> when possible, then edit details.
  8. Run scripts/specctl validate and scripts/specctl ready.

Read the full file on GitHub · 161 lines

Files

What ships with it

5 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. 8d ago First seen · 161 lines · 71 tokens per session scan A 10f71a7d744d

Subscribe to this mod's changes

spec-flow is a skill published in the GitHub repository alexei-led/cc-thingz (35 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,178 once invoked, about $0.0004 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-30.

Claude CodePlanningProject managementagent-skillsagentbundlerai-codingclaude-code-marketplaceclaude-code-plugin
Related

Other skills, from other repositories

predictable-revenue

Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B…

wondelai/skills · 152 tokens

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…

wondelai/skills · 147 tokens

team-topologies

Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…

wondelai/skills · 155 tokens

glab

Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.

NikiforovAll/claude-code-rules · 59 tokens

execute-round

Use when a planned round handoff exists and needs to be implemented end-to-end via the 4-commit chain (entry-admin → BA design → dev body with inline CR + SE → state refresh + self-audit). Dispatches ba-designer / developer / cr-reviewer / se-contract sequentially.

Arch1eSUN/Arcgentic · 65 tokens

status

Render the feature × stage integrity matrix — every feature vs every Iron Law stage with pass/skip/fail markers. Use when the user wants a project-wide status board, a release-readiness view, or to spot which features are still behind which stage. Activate only when the connected project contains spec.yaml or the user…

qwerfunch/cladding · 76 tokens