What is Spec-Flow GEMINI.md?

A set of instructions for using Spec-Flow with the Gemini command-line tool. Spec-Flow is a workflow kit that turns product ideas into written specifications, plans, implementation work, and releases.

Use it to interpret Spec-Flow slash commands and guide software features or larger projects from initial idea through deployment.

It gives the agent a defined process and command map, so feature work follows the same stages and quality checks each time.

How marcusgoll/Spec-Flow configures Gemini CLI

Reuse

Borrowing it

Nothing to install: this file belongs to marcusgoll/Spec-Flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/marcusgoll/Spec-Flow/main/GEMINI.md

Clone the repo

git clone --depth 1 https://github.com/marcusgoll/Spec-Flow

Made for: Gemini CLI.

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/instructions/marcusgoll/spec-flow/gemini-md/github.svg)](https://agentmods.dev/instructions/marcusgoll/spec-flow/gemini-md)

Your own site

<a href="https://agentmods.dev/instructions/marcusgoll/spec-flow/gemini-md"><img src="https://agentmods.dev/badge/instructions/marcusgoll/spec-flow/gemini-md/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/instructions/marcusgoll/spec-flow/gemini-md"><img src="https://agentmods.dev/badge/instructions/marcusgoll/spec-flow/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,377 This file is loaded in full into every session.

When invoked 1,377 The same file — it is already loaded in full.

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.01377	$0.01377
Opus 5.5	$0.00551	$0.00551
Sonnet 5.5	$0.00275	$0.00275
Haiku 4.5	$0.00138	$0.00138

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

Security

Grade A, and why

Spec-Flow GEMINI.md 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.

GEMINI.md · 107 lines

How it starts

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

GEMINI.md - Spec-Flow for Gemini CLI

Spec-Flow Workflow Kit: Transform product ideas into production releases via spec-driven development. This extension ports the Claude Code Spec-Flow workflow to Gemini CLI.

WHAT This Is

Spec-Flow is a workflow toolkit that automates the entire software development lifecycle. It guides features and epics from specification through planning, implementation, and deployment with built-in quality gates.

YOUR ROLE

You are the Spec-Flow Orchestrator. You must help the user execute the Spec-Flow workflow by interpreting "Slash Commands" and executing the underlying logic defined in the .claude/ directory.

HOW To Use It (For the Model)

When the user provides a command (e.g., "/feature", "/plan"), you must:

Identify the Command: Look up the command in the "Command Map" below.
Read the Definition: Read the corresponding markdown file in .claude/commands/.
Execute Instructions: Follow the <process> or <workflow> defined in that file.
- SlashCommand(/cmd): If the file instructs you to use a SlashCommand (e.g., /spec), you must recursively look up that command in the map, read its definition file, and execute its instructions. Do not output the text "/spec" to the user; instead, perform the spec phase.
- Bash(...): Use the run_shell_command tool to execute the specified command.
- Read(...): Use the read_file tool.
- TodoWrite(...): Use the write_todos tool to track progress.

Command Map

Command	Definition File	Description
`/feature`	`.claude/commands/core/feature.md`	Start/Manage a feature workflow.
`/epic`	`.claude/commands/core/epic.md`	Start/Manage an epic workflow.
`/spec`	`.claude/commands/phases/spec.md`	Specification Phase.
`/clarify`	`.claude/commands/phases/clarify.md`	Clarification Phase.
`/plan`	`.claude/commands/phases/plan.md`	Planning Phase.
`/tasks`	`.claude/commands/phases/tasks.md`	Task Breakdown Phase.
`/phases:validate`	`.claude/commands/phases/validate.md`	Cross-artifact analysis.
`/implement`	`.claude/commands/phases/implement.md`	Implementation Phase.
`/optimize`	`.claude/commands/phases/optimize.md`	Optimization Phase.
`/ship`	`.claude/commands/deployment/ship.md`	Deployment (Auto-detect).
`/ship-staging`	`.claude/commands/deployment/ship-staging.md`	Deploy to Staging.
`/ship-prod`	`.claude/commands/deployment/ship-prod.md`	Deploy to Production.
`/finalize`	`.claude/commands/phases/finalize.md`	Finalize workflow.
`/init`	`.claude/commands/core/init.md`	Initialize Spec-Flow in a project.
`/help`	`.claude/commands/core/help.md`	Context-aware guidance.

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

2mo ago First seen · 107 lines · 1,377 tokens per session scan A eafb5e891520

Subscribe to this mod's changes

Spec-Flow GEMINI.md is an instructions file published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 1mo ago), licensed MIT. It adds 1,377 tokens to every session, about $0.0055 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-09-03.

Planning Project management ai-agents ai-assisted-development ai-workflows automation bash claude

Spec-Flow GEMINI.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Spec-Flow GEMINI.mdmarcusgoll/Spec-Flow	Instructions file	96	1mo ago	MIT	A	1,377	Gemini CLI
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

Spec-Flow: Instructions file for Gemini CLI