A workflow that turns a rough feature idea into a handoff document developers can use. It creates a feature request, checks its acceptance criteria, and adds technical guidance.

Writing user stories and acceptance criteria, reviewing those criteria for quality, outlining implementation and architecture considerations, and recording open questions.

It fills in missing context and catches unclear or untestable requirements before engineering starts.

fr-to-ready — Agent for Claude Code by felipecabargas/gambit

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.

Clone the repo

git clone --depth 1 https://github.com/felipecabargas/gambit

Made for: Claude Code.

Or install gambit, the plugin that ships this one along with the rest of its 13 skills, 4 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/felipecabargas/gambit/fr-to-ready/github.svg)](https://agentmods.dev/agents/felipecabargas/gambit/fr-to-ready)

Your own site

<a href="https://agentmods.dev/agents/felipecabargas/gambit/fr-to-ready"><img src="https://agentmods.dev/badge/agents/felipecabargas/gambit/fr-to-ready/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/felipecabargas/gambit/fr-to-ready"><img src="https://agentmods.dev/badge/agents/felipecabargas/gambit/fr-to-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 110 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,094 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.

Model	Per session	Once invoked
Fable 5.1	$0.00110	$0.01094
Opus 5.5	$0.00044	$0.00438
Sonnet 5.5	$0.00022	$0.00219
Haiku 4.5	$0.00011	$0.00109

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

Security

Grade A, and why

fr-to-ready 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 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.

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.

agents/fr-to-ready.md · 95 lines

How it starts

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

FR to Ready Agent

Overview

This agent is a three-skill chain that closes the gap between a raw feature idea and a dev-ready state. It runs write-feature-request, verify-acceptance-criteria, and write-technical-brief in sequence, producing a complete handoff package that engineering can act on without needing to chase down missing context.

The three components and what each produces:

write-feature-request — guides you through a structured conversation to produce a complete FR with problem statement, user stories, and acceptance criteria
verify-acceptance-criteria — evaluates every AC against five quality dimensions and rewrites failing criteria before they reach engineering
write-technical-brief — translates the verified FR into an engineering-facing document covering architecture considerations, implementation approach, and open questions

Chain

write-feature-request → verify-acceptance-criteria → write-technical-brief

How It Runs

Step 1 — Write the Feature Request

Run write-feature-request in full guided conversation mode. The skill asks clarifying questions, surfaces edge cases, and produces a complete FR with a problem statement, user stories, and a set of acceptance criteria.

Save output in the standard write-feature-request format.

Pause here: present the completed FR to the user for review. Ask: "Here is the Feature Request. Does this capture what you intend to build? Confirm to continue with AC verification, or provide corrections first."

Do not proceed to Step 2 until the user confirms.

Step 2 — Verify and Rewrite Acceptance Criteria

Pass all ACs from the FR into verify-acceptance-criteria. The skill evaluates each AC against five quality dimensions: testability, clarity, completeness, scope, and independence.

For any AC that fails verification, automatically produce a rewritten version. Present a diff to the user showing original and rewritten ACs side by side.

Ask: "Here are the AC rewrites. Do you approve these changes? You can accept all, reject individual rewrites, or provide your own edits."

Read the full file on GitHub · 95 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.

1mo ago First seen · 95 lines · 110 tokens per session scan A caa5ded726f8

Subscribe to this mod's changes

fr-to-ready is an agent published in the GitHub repository felipecabargas/gambit (2 stars, last pushed 4mo ago), licensed MIT. It adds 110 tokens to every session and 1,094 once invoked, about $0.0004 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-31.

Planning Project management agy-cli antigravity-cli antigravity-plugin claude-code-plugin claude-skills gemini-cli-extension

support-assistant

Use when: handling helpdesk tickets, technical support, or customer service conversations. Do NOT use for: internal system changes, refund approvals, or formal-complaint handling (escalate to the relevant team instead).

fusengine/agents · 48 tokens

project-manager

Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.

pranav8494/team-of-agents · 50 tokens

technical-business-analyst

Technical business analysis specialist. Invoke for implementation plans, user stories, requirements documents, functional specifications, scope definition, gap analysis, ADRs, RAID logs, and task decomposition. Returns structured documents with exact detail, no placeholders.

pranav8494/team-of-agents · 51 tokens

fr-to-ready