cells-spec

Generate Given/When/Then behavioral specifications from change proposals.

Updated Aug 27, 2026

Search Tags:#specification #bdd #openspec #delta #given-when-then #engram #cells

Ready to run

npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cells-spec
Source: https://github.com/PixelDroid19/cells-agents/tree/main/skills/cells-spec
Command: npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing precise behavioral specifications for changes is time‑consuming and error‑prone. This Skill automates the creation of Given/When/Then BDD scenarios from change proposals, ensuring consistent, testable requirements.

Core Features & Use Cases

Automated Spec Generation: Transforms a proposal artifact into delta or full specifications with RFC 2119 language.
Multi‑Mode Persistence: Supports engram, openspec, hybrid, or none storage backends.
Domain‑Aware Delta Specs: Detects affected domains and writes only the changed sections, preserving existing specs.
Use Case: When a developer needs specs for a new feature or modification, they invoke this Skill to produce ready‑to‑test BDD documents.

Quick Start

Ask the assistant to write specs for the change named “checkout‑flow” using the default storage mode.

Frequently Asked Questions about cells-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate BDD specifications from a change proposal?▼

Generate BDD specifications by processing a change proposal artifact to produce Given/When/Then scenarios with RFC 2119 compliant requirements. The output provides ready-to-test behavioral documents for downstream design or testing workflows.

What is delta handling in behavioral specifications?▼

Delta handling in behavioral specifications detects affected domains to write only the changed sections. This approach preserves existing specs while generating new Given/When/Then scenarios strictly for the modified behaviors.

How do I persist BDD specs using openspec or engram modes?▼

Persist BDD specs by selecting engram, openspec, hybrid, or none storage modes during generation. These modes handle optional artifact storage to save the behavioral specifications for downstream design or testing processes.

Can I write Given/When/Then scenarios for a specific domain without overwriting existing specs?▼

Yes, domain-aware delta specs detect affected domains and write only the changed sections. This ensures writing Given/When/Then scenarios for a specific domain occurs without overwriting or losing existing specifications.

Does BDD spec generation require RFC 2119 language for requirements?▼

BDD spec generation enforces RFC 2119 compliant language for all requirements by default. This ensures behavioral specifications generated from change proposals remain precise, consistent, and fully testable.

What's the best way to automate writing testable requirements for new features?▼

Automate writing testable requirements by transforming change proposal artifacts into Given/When/Then BDD scenarios. This approach ensures consistent, precise specifications while significantly reducing the manual effort and errors of writing them by hand.