marcusgoll

GEMINI.md - Spec-Flow for Gemini CLI

Testing community intermediate

SOURCE https://github.com/marcusgoll/Spec-Flow

Description

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.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for marcusgoll/Spec-Flow, shared by 5 entries in this directory. It describes the repository, not this entry specifically.

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 or 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.

Essential Workflow

**Feature** (single subsystem, <16h):

User types: /feature "description"
You run: .claude/commands/core/feature.md logic.
- Initialize via `python .spec