{"enrichment":{"faq":[{"a":"doc-bdd translates EARS requirements into Layer 4 acceptance scenarios using structured YAML format. Each scenario includes Given-When-Then phases that map directly to your EARS acceptance criteria. Start with a completed EARS document, then use doc-bdd to generate executable test scenarios with element-level trace links back to the source EARS requirement and forward to your SPEC sections.","q":"How do I create BDD scenarios from EARS requirements?"},{"a":"doc-bdd uses structured YAML (not Gherkin) to author acceptance scenarios. Each scenario contains Given-When-Then phases organized as YAML blocks, making them both human-readable and machine-parseable. This format bridges EARS requirements and executable tests while maintaining full traceability through upstream/downstream trace links at the element level.","q":"What format does doc-bdd use for acceptance test scenarios?"},{"a":"Yes. doc-bdd converts EARS acceptance criteria into Layer 4 BDD scenarios with Given-When-Then structure. It maps each EARS element to one or more scenario categories (success, error, recovery, parameterized, optional) with assigned priorities, then generates QA-staging acceptance test suites ready for execution while preserving requirement traceability.","q":"Can doc-bdd convert EARS to behavior driven development?"},{"a":"doc-bdd organizes acceptance scenarios into five categories: success (happy path), error (failure handling), recovery (resilience), parameterized (data-driven variants), and optional (conditional flows). Each category receives a priority assignment to guide QA staging and test execution order.","q":"What scenario categories does doc-bdd define?"},{"a":"Use doc-bdd after your EARS requirements are complete and before you begin ADR/SPEC authoring. It serves as the bridge between requirements and specification by generating Layer 4 acceptance scenarios with full trace links. For batch generation across multiple documents, the autopilot skill handles orchestration.","q":"When should I use doc-bdd in my documentation workflow?"},{"a":"Yes. doc-bdd generates acceptance scenarios with element-level traceability, linking each scenario upstream to its source EARS requirement and downstream to relevant SPEC sections. This dual-direction trace mapping ensures your acceptance tests remain synchronized with both upstream requirements and downstream specifications throughout the documentation lifecycle.","q":"Does doc-bdd provide traceability between requirements and tests?"}],"shadow_tags":["acceptance-criteria","scenario-authoring","test-specification","requirements-bridge","yaml-structured","qa-validation","traceability-mapping","behavior-specification"],"summary_rewrite":"doc-bdd translates EARS requirements into Layer 4 acceptance scenarios using structured YAML (not Gherkin), each with Given-When-Then phases, element-level trace links to upstream EARS, and forward mapping to SPEC sections. Use this after EARS is complete and before ADR/SPEC authoring; for batch generation across multiple documents, the autopilot skill handles orchestration."},"files":[{"bytes":10921,"path":"platforms/claude-code-plugin/skills/doc-bdd/SKILL.md","sha256":"e5b26b9462cde7d370d3ebb9cf430cef788d9494ead73cbea2d9f73181bc4d17","url":"https://skillfed.io/files/vladm3105/aidoc-flow-framework/doc-bdd/d5813811/SKILL.md"}],"id":"vladm3105/aidoc-flow-framework/doc-bdd","links":{"html":"https://skillfed.io/vladm3105/aidoc-flow-framework/doc-bdd","md":"https://skillfed.io/vladm3105/aidoc-flow-framework/doc-bdd.md","repo":"https://github.com/vladm3105/aidoc-flow-framework"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":3,"language":"Python","last_updated":"2026-07-27","license":"MIT","name":"doc-bdd","publisher":"vladm3105","stars":16},"relations":{"categories":["requirements-engineering","bdd-testing","documentation-automation"],"similar":[{"id":"vladm3105/aidoc-flow-framework/doc-bdd-autopilot"},{"id":"vladm3105/aidoc-flow-framework/doc-bdd-fixer"},{"id":"vladm3105/aidoc-flow-framework/doc-bdd-audit"},{"id":"vladm3105/aidoc-flow-framework/doc-ears"},{"id":"vladm3105/aidoc-flow-framework/doc-tdd"},{"id":"vladm3105/aidoc-flow-framework/doc-adr"},{"id":"vladm3105/aidoc-flow-framework/doc-spec"},{"id":"vladm3105/aidoc-flow-framework/doc-flow"},{"id":"vladm3105/aidoc-flow-framework/doc-prd"},{"id":"vladm3105/aidoc-flow-framework/sdd-orchestrator"}]},"slug":{"owner":"vladm3105","repo":"aidoc-flow-framework","skill":"doc-bdd"},"version":"d5813811"}