메뉴
Gherkin/BDD specification expert for writing behavioral scenarios, acceptance criteria, and applying structured specifications to improve code generation quality
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | gherkin-expert |
| version | 1.0.0 |
| description | Gherkin/BDD specification expert for writing behavioral scenarios, acceptance criteria, and applying structured specifications to improve code generation quality |
| activation_keywords | ["Gherkin","BDD","behavior-driven","Given When Then","Given/When/Then","Feature:","Scenario:","Scenario Outline:","acceptance criteria","behavioral specification","feature file","cucumber","SpecFlow"] |
| agent | amplihack:specialized:gherkin-expert |
Provides expert-level Gherkin/BDD specification assistance for writing behavioral scenarios that clarify acceptance criteria and improve downstream code generation quality.
This skill delegates to the gherkin-expert agent which has knowledge of:
Gherkin is a tool, not a rule. Use judgment:
Good fit:
English is fine:
# Write scenarios for a feature
/gherkin-expert Write Gherkin scenarios for our user authentication flow
# Review existing scenarios
/gherkin-expert Review these acceptance criteria for completeness
# Translate requirements to BDD
/gherkin-expert Convert these business rules into Given/When/Then scenarios
# Decide if Gherkin is appropriate
/gherkin-expert Should I write Gherkin scenarios for this retry cascade feature?
# Improve scenarios
/gherkin-expert These scenarios feel too implementation-focused, help me make them declarative
experiments/hive_mind/gherkin_v2_recipe_executor/Auto-generates code flow diagrams from multi-language module analysis. Detects when architecture diagrams become stale (code changed, diagram didn't). Supports Python, TypeScript/JavaScript, Rust, and Go out of the box. Use when: creating new modules, reviewing PRs for architecture impact, or checking diagram freshness across polyglot repositories. Generates mermaid diagrams showing imports, dependencies, and module relationships.
Execute multiple independent development tasks in parallel using subprocess isolation. Each task runs in a clean /tmp clone with Recipe Runner code-enforced workflow execution. Proven pattern: 4/5 PRs created successfully in first production use.
Interactive teaching agent for the goal-seeking agent generator and eval system. Provides a structured 14-lesson curriculum covering agent generation, SDK selection, multi-agent architecture, progressive evaluation (L1-L12), retrieval strategies, intent classification, math code generation, self-improvement loops with patch proposer and reviewer voting, and memory export/import.
Development workflow for features, bugs, refactoring. Normally executed as a sub-recipe by dev-orchestrator/smart-orchestrator. Supports direct invocation via recipe runner for standalone use.
Default task orchestrator for all development and investigation work. Classifies tasks, decomposes into parallel workstreams if appropriate, and routes execution through the recipe runner. Replaces ultrathink-orchestrator.
Writing clear, discoverable software documentation following the Eight Rules and Diataxis framework. Use when creating README files, API docs, tutorials, how-to guides, or any project documentation. Automatically enforces docs/ location, linking requirements, and runnable examples.