orchestra-gherkin

Included with Lifetime

$97 forever

Generate Gherkin scenarios from an orchestra PRD or spec — produces Feature/Scenario blocks in fenced gherkin markdown.

Writing & Docs

What this skill does


# Orchestra Gherkin

Generate Gherkin scenarios from an orchestra work item. Reads either a PRD or spec and produces a `gherkin.md` file alongside it.

## Variables

SOURCE: $ARGUMENTS

## Workflow

### Step 1: Locate the source

If `$ARGUMENTS` is a file path, read it directly.

If `$ARGUMENTS` is a work item name, look for it in `.orchestra/work/`:
```
.orchestra/work/<name>/prd.md
.orchestra/work/<name>/spec.md
```

Prefer `spec.md` if both exist — it has more concrete implementation detail. If only `prd.md` exists, use that.

If no path or name is provided, STOP and ask the user to provide one.

### Step 2: Determine source type

**From a PRD** — extract:
- Problem statement → Feature description
- User goals → high-level scenarios (happy path + edge cases)
- Success criteria → Then clauses
- Scope / out of scope → tag with `@wip` or `@out-of-scope`

**From a spec** — extract:
- Deliverables → Feature description
- Steps / implementation tasks → Scenario steps
- Acceptance criteria → Then clauses
- Risks → negative/error scenarios

### Step 3: Generate Gherkin

Write the output file in the same directory as the source file:
- If source is `spec.md` → write `gherkin-spec.md`
- If source is `prd.md` → write `gherkin-prd.md`

Output format:

````markdown
# Gherkin Scenarios: <Feature Name>

> Source: <relative path to PRD or spec>
> Generated: <date>

```gherkin
Feature: <feature name from PRD/spec title>
  <one-line description of the feature>

  Background:
    Given <any shared preconditions>

  Scenario: <happy path name>
    Given <initial state>
    When <user action or system event>
    Then <expected outcome>
    And <additional assertion>

  Scenario: <alternate path>
    Given <initial state>
    When <different action>
    Then <different outcome>

  Scenario: <error / edge case>
    Given <precondition>
    When <action that triggers the edge case>
    Then <error or fallback outcome>
```
````

### Step 4: Rules

- Every scenario must have at least one `Given`, one `When`, one `Then`
- Use `And` to chain — never repeat `Given`/`When`/`Then` back to back
- Scenario names are sentence case, no punctuation
- Feature name matches the PRD/spec title exactly
- Include a `Background:` block only if 3+ scenarios share the same precondition
- Tag `@wip` on scenarios derived from items marked as out-of-scope or future
- Aim for 3–7 scenarios per feature — more than that, split into multiple features
- All output is wrapped in ` ```gherkin ` fenced blocks inside the markdown file

### Step 5: Report

Tell the user:
- Path to the generated `gherkin-spec.md` or `gherkin-prd.md`
- How many scenarios were generated
- Any acceptance criteria from the source that couldn't be mapped to a scenario (and why)

Files: 3

Size: 6.1 KB

Complexity: 16/100

Category: Writing & Docs

Source: https://github.com/mpazaryna/agentic-factory/tree/main/skills/orchestra-gherkin

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts