draft-story
Generate a draft story markdown from a story tracker or a feature description
Retrofit BDD scenarios from an existing implementation
> /plugin marketplace add Intai/story-flow > /plugin install story-flow@story-flow
How it fires
How this command gets triggered: by you, by Claude, or both.
/retrofit-scenariosContext preview
What this command does when you run it.
Retrofit BDD scenarios from an existing implementation
argument-hint: [@path/to/file.feature, @path/to/source (use * for wildcard) or "feature description"] description: Retrofit BDD scenarios from an existing implementation
Use the qa-tester subagent and instruct it to load skills in this order using the Skill tool: 1. First: `story-flow:plan-bdd-scenarios` (plugin - general BDD planning protocol) 2. Then: `plan-bdd-scenarios` if it exists (project-level - overrides/extends the plugin) 3. Confirm which skills are loaded before continuing with BDD planning.
If source paths are provided ($2 onwards): Plan BDD scenarios in $1 from the implementation in $2 $3 $4 $5 $6. If a feature description is provided instead: Locate the implementation of $2 in the codebase; if it cannot be found or does not settle the behaviour, observe the running app or any other source available. Then plan BDD scenarios in $1 from it.
🤖🧠 Agentic development workflow for AI–HI (Human Intelligence) collaboration
Repo: Intai/story-flow
Generate a draft story markdown from a story tracker or a feature description
Learn story-flow concepts with interactive guidance for junior developers
Execute BDD test scenarios in a .feature file using browser automation. Use --record to generate a Playwright .spec.js file.