Do I need to write code or Playwright tests?

No. Only create detailed BDD scenarios in .feature files; no test code should be implemented at this stage.

Should each feature have its own feature file?

Yes, keep scenarios scoped to a single feature and create separate files per feature.

What if requirements change?

Update the .feature file with revised Given/When/Then scenarios to maintain alignment.

Plan BDD scenarios

npx machina-cli add skill Intai/story-flow/plan-bdd-scenarios --openclaw

Files (1)

SKILL.md

380 B

Plan BDD scenarios

Instructions

While planning test scenarios, create ONLY detailed BDD scenarios in .feature files. Do not implement Playwright test code.

Example Inputs

Plan test scenarios according to @path/to/file-story.md
Plan BDD scenarios in @path/to/file.feature

Source

git clone https://github.com/Intai/story-flow/blob/main/plugins/story-flow/skills/plan-bdd-scenarios/SKILL.mdView on GitHub

Overview

This skill helps you plan detailed BDD scenarios in .feature files rather than writing test code. It ensures that acceptance criteria are captured as readable scenarios for collaboration with product and QA, before any implementation begins. Focusing on behavior-first planning improves traceability and test coverage.

How This Skill Works

You draft Given-When-Then style scenarios inside dedicated .feature files, ensuring no Playwright or code is included. The output is a collection of ready-to-implement BDD scenarios that stakeholders can review, keeping planning isolated from implementation work.

When to Use It

Before implementing a feature, draft detailed BDD scenarios in a dedicated .feature file to capture expected behavior.
When collaborating with product and QA, use BDD scenarios to align on acceptance criteria.
During feature discovery, plan edge cases and happy-path scenarios as concrete Given/When/Then examples.
When refactoring, review existing stories and replace vague acceptance criteria with explicit BDD scenarios.
To kick off test planning, create scenario outlines with examples to cover data variations.

Quick Start

Step 1: Identify the feature and its user goals.
Step 2: Write Given-When-Then scenarios in a new .feature file, without code.
Step 3: Share with stakeholders for feedback and map to acceptance criteria.

Best Practices

Keep scenarios in standalone .feature files per feature.
Use clear, business-facing Given-When-Then language.
Describe only behavior; avoid implementation details.
Include concrete examples and edge cases.
Review with stakeholders and map each scenario to acceptance criteria.

Example Use Cases

Login.feature: successful login, invalid credentials, locked account
Cart.feature: add item, update quantity, remove item, empty cart
Checkout.feature: enter shipping, select payment, confirm order
PasswordReset.feature: request link, invalid email, reset success
Profile.feature: change email, change password, privacy settings

Frequently Asked Questions

Add this skill to your agents