bpmn-workflow_skill

Overview

This skill generates and maintains BPMN 2.0 process diagrams from feature specifications and links them to Gherkin scenarios for end-to-end traceability. It automates creation of feature-level BPMN files, manifests that map Gherkin to BPMN elements, and updates a system-wide diagram to reflect feature pools. The output supports documentation, engineering handoffs, and QA validation.

How this skill works

The skill inspects project feature files and Ask-mode artifacts (wireframes, user flows, API specs) to parse or generate Gherkin scenarios. It calls a BPMN generator to produce feature .bpmn files, creates a manifest that links BPMN elements to scenario IDs, and composes a master system.bpmn by merging features. Validation steps check IDs, step keywords, and BPMN validity.

When to use it

• After feature exploration (Ask mode) to visualize flows
• When documenting processes for stakeholders or audits
• Before planning work to ensure scenarios are covered
• When updating features with new scenarios or edge cases
• To generate traceability between tests (Gherkin) and process models

Best practices

• Run Ask mode first: wireframes and user flows yield richer scenarios
• Keep scenario IDs unique and consistent across files
• Follow Gherkin naming conventions: happy, validation, error, edge
• Include API endpoints as scenarios for integration steps
• Re-run link and compose steps after modifying scenarios

Example use cases

• Create BPMN for an invoice creation feature with happy and error paths
• Document authentication and workspace switching in the master diagram
• Map validation and edge-case Gherkin scenarios to BPMN user tasks
• Regenerate system.bpmn after adding or removing features
• Validate generated BPMN and fix broken manifest links before QA