القائمة
Use when writing or reviewing Gherkin scenarios, especially after discovering examples or edge cases that reveal a business rule
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | bdd-formulation |
| description | Use when writing or reviewing Gherkin scenarios, especially after discovering examples or edge cases that reveal a business rule |
Formulation is the craft of writing Gherkin that serves as living documentation. Good scenarios are concrete examples of business rules, not test scripts.
When examples reveal a rule, make the rule visible in the feature file: group related scenarios under a rule heading that states the rule they illustrate.
In Memba, use the native Gherkin Rule: keyword for rule headings.
Both the browser Cucumber runner and the Elixir/domain Cucumber parser
support it now, so commented rule headings are no longer needed.
Rule: Manual blockers replace the existing manual blocker
Scenario: Adding another manual blocker updates the reason
Given I add the yak "deploy"
And I add manual blocker to "deploy" with reason "waiting on vendor"
When I add manual blocker to "deploy" with reason "waiting on review"
Then the JSON yak "deploy" should have exactly one manual blocker with reason "waiting on review"
From Seb Rose, scenarios should be:
Rule: headings for business/domain rules, not implementation mechanisms.Rule: section.Rule: groups over one long pile of loosely related scenarios.When a scenario feels long, do not shorten it mechanically. First ask what makes it long.
When Alice signs in with their email address when sign-in mechanics are not the rule under test.Rule: sections be clearer if its rules were extracted?Interview Matt about the next product/dev iteration, turn the discussion into a focused iteration plan, publish planning artifacts, validate the plan, and ask whether this LLM session should launch the Fabro implementation-and-review delivery workflow. Use when planning the next iteration, shaping work before implementation, or preparing a plan for delivery.
Delegate self-contained research, review, planning, debugging, or implementation subtasks to a Pi subagent running the openai-codex/gpt-5.5 model. Use when the user asks for Pi, GPT-5.5, a subagent, independent analysis, parallel investigation, or a second coding-agent opinion.
Offer to capture and, when accepted, write a docs/kaizen observation when we notice friction, imperfections, waste, opacity, brittleness, or failure in the pipeline/factory/workflows/tooling used to create the product. Use for workflow/tooling problems, not ordinary product bugs.
Read, audit, and safely manipulate Resend email configuration and message data through the Resend API. Use when inspecting domains, API keys, audiences, contacts, broadcasts, emails, webhooks, or making explicit Resend changes with an API key from the environment.
Read, audit, and safely manipulate Postmark configuration and message data through the Postmark API. Use when inspecting servers, streams, senders, domains, templates, messages, webhooks, suppressions, or making explicit Postmark changes with API tokens from the environment.
Read, audit, and safely manipulate DNSimple DNS configuration through the DNSimple API. Use when inspecting domains, zones, DNS records, or making explicit DNS changes with a DNSimple API token from the environment.