specflow-use

Featured

To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.

AI & Automation 344 stars 75 forks Updated 1 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 88/100

Stars 20%
85
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# SpecFlow Use This skill helps you drive **Grid Dynamics SpecFlow** from a local workspace via **SpecFlow MCP**. Rosetta stays local; SpecFlow runs everything remotely. The skill loads project context from `gain.json` and guides the user through SpecFlow MCP tool usage. SpecFlow MCP is the only user interface to SpecFlow: you order work and download outputs. You do not connect to or operate on the remote workspaces directly. ## Quick Start When the user mentions SpecFlow or works in a SpecFlow-enabled project: 1. **Detect** `gain.json` at the workspace root (and up to 2 parents). If missing, SpecFlow MCP will create it on the first tool call (together with `specflow_session.json`). 2. **Load** and summarize the project context. 3. **Guide** the user to the right phase using `references/specflow-mcp-tools.md`. ## Step 1: Detect gain.json Check for `gain.json` at the current workspace root. If not found, check parent directories up to 2 levels. If still missing, tell the user this workspace is not yet initialized for SpecFlow — the first SpecFlow MCP tool call will create both `gain.json` and `specflow_session.json`. ## Step 2: Parse and Display Context When `gain.json` is found, present a compact summary: ``` ## SpecFlow Project Context **Description**: [gain.json.description] **Services**: specflow — [gain.json.servicesDescription.specflow] rosetta — [gain.json.servicesDescription.rosetta] **Supported Coding Agents**: [gain.json.codingAgents] **Versi...

Details

Author
griddynamics
Repository
griddynamics/rosetta
Created
7 months ago
Last Updated
1 weeks ago
Language
TypeScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

openapi-to-mcp

Build and deploy an MCP server from an OpenAPI / Swagger spec using the mcp-use TypeScript SDK. Use this skill whenever the user wants to "turn this OpenAPI spec into an MCP server", "make this API usable from Claude/ChatGPT", "wrap this Swagger doc as MCP tools", "expose this REST API to an LLM", "generate MCP tools from a spec", or pastes/attaches an `openapi.yaml`, `openapi.json`, or `swagger.json` and asks for a Claude-compatible version. Trigger even if the user doesn't say "MCP" — if they describe an existing HTTP API (REST endpoints, an internal service, a third-party API they have a key for) and want an LLM to call it, this is the right skill. Covers spec ingestion (file path, URL, or pasted), operation-to-tool mapping, auth wiring (apiKey, bearer, basic, OAuth bearer), scaffolding with `create-mcp-use-app`, tool generation with proper zod schemas, live testing in the mcp-use inspector, and deploying to Manufact / mcp-use cloud.

10,603 Updated today
mcp-use
Testing & QA Listed

specflow-entry

Classify every incoming user request against the project's spec tree (developer specs in `.specflow/specs/`, business specs in `.specflow/specs-business/`, and `_overview.md` folder docs) and route it to the correct action before any work begins. This skill is the mandatory entry point for ALL user interactions in a Specflow-managed project (any project with a `.specflow/specs/` directory, with or without a parallel `.specflow/specs-business/`). PROACTIVELY use this skill whenever the user says anything in a project under spec management — bug reports, feature requests, behavior changes, stakeholder questions, "what does this group do?", outcome/journey/metric talk, or anything that might touch a developer spec, a business spec, or a folder overview. Also triggers on "add a feature", "fix this bug", "change this behavior", "what does X do", "what's the goal of X", "why do we have X", and on requests that may have drifted between business and developer layers (e.g., a dev change that invalidates the business d

2 Updated 1 months ago
pedropacheco95
AI & Automation Listed

spec-forge

Professional specification system for Codex. Use when the user asks to create, improve, review, audit, analyze, or propagate product/software documentation, including ideas, PRDs, SRS documents, technical designs, architecture/RFC docs, feature specs, test cases, documentation audits, document landscape analysis, and full idea-to-spec chains. Supports complex multi-skill orchestration: idea -> decompose -> tech-design + feature specs -> review, with optional PRD, SRS, test-cases, audit, analyze, and propagate workflows.

7 Updated 1 months ago
tercel