/execute-scenario

--- argument-hint: [ST-01 or all, @path/to/file.feature (use * for wildcard), ..., --record (optional)] description: Execute BDD test scenarios in a .feature file using browser automation. Use --record to generate a Playwright .spec.js file. ---

intai@intai

GitHub

From plugin

story-flow

126 skills7 agents6 commands

Install

$ npx -y skills add Intai/story-flow --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/execute-scenario

Context preview

What this command does when you run it.

--- argument-hint: [ST-01 or all, @path/to/file.feature (use * for wildcard), ..., --record (optional)] description: Execute BDD test scenarios in a .feature file using browser automation. Use --record to generate a Playwright .spec.js file. ---

Command definition

execute-scenario.md

argument-hint: [ST-01 or all, @path/to/file.feature (use * for wildcard), ..., --record (optional)]
description: Execute BDD test scenarios in a .feature file using browser automation. Use --record to generate a Playwright .spec.js file.

Load BOTH skills in this order using the Skill tool: 1. First: `story-flow:execute-bdd-scenario` (plugin - general BDD framework) 2. Then: `execute-bdd-scenario` (project-level - overrides/extends the plugin) 3. Confirm both skills are loaded before continuing with the execution.

Execute BDD scenario $1 in $2 $3 $4 $5 $6.

Read it on GitHub ↗

Ships withstory-flow

🤖🧠 Agentic development workflow for AI–HI (Human Intelligence) collaboration

Get the whole plugin, auto-invoked

Stats

JavaScript React React Native Vue Angular

+7 tags

Bash Git Playwright Markdown Anthropic MCP Jira

Stars

Views

Forks