requirements
Write BDD requirements in Gherkin format. Guides the user through the process.
What this skill does
# /requirements
Write new BDD requirements in Gherkin format.
## Workflow
### 0. Read Conventions
**First:** Read [bdd-guide.md](bdd-guide.md) to understand:
- BDD best practices
- Folder structure (Domain → Subdomain → Capability)
- Feature ID format (`@DOM-SUB-CAP-NNN`)
- Tags (priority, status)
- Actors
### 1. Read Domain Knowledge
**Before writing requirements**, search for and read existing domain documentation:
1. Look for entity definitions in `docs/domains/*/entities/` or similar paths
2. Read the `_overview.md` if it exists
3. Read entity files relevant to the feature being specified
4. Understand existing attributes, relationships, and business rules
This ensures requirements align with the established domain model and use correct terminology.
### 2. Understand the Need
Ask the user:
- What should the functionality do?
- Who are the actors?
- What terms/expressions should be used?
### 3. Define Scenarios
For each scenario, ask about:
- Precondition (Given)
- Action (When)
- Expected result (Then)
**NEVER assume error messages or business logic - ask!**
### 4. Generate Feature File
**Location:** Follow the folder structure in bdd-guide.md:
```
requirements/[NN] [Domain]/[NN] [Subdomain]/[NN] [Capability]/feature-name.feature
```
**Format:**
```gherkin
@[ID] @[priority]
Feature: [ID] [Name]
As a [actor]
I want to [action]
So that [value].
# OPEN QUESTIONS:
# - [Any uncertainties are documented here]
Background:
Given [common precondition]
Rule: [Business rule]
Scenario: [Descriptive name]
Given [precondition]
When [action]
Then [expected result]
```
**When uncertain:** Document with `# OPEN QUESTIONS:` right after the feature description (after "So that...").
### 5. Update Overview
Run the markdown generator to update `requirements/requirements-overview.md`:
```bash
cd requirements-parser && npm run generate-overview
```
This scans all `.feature` files and generates an updated overview with ID, feature name, tags, and statistics.
## Resources
- [bdd-guide.md](bdd-guide.md) - BDD best practices and project conventions
- [examples/gherkin-example.feature](examples/gherkin-example.feature) - Complete example
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.