What problem does it solve?
Manually authoring new browser QA flow specifications is repetitive and error-prone, especially when every file must follow a consistent template with correctly formatted YAML frontmatter. This Skill scaffolds a new flow file in qa/browser-flows with the right structure, slug validation, and optional fields handled automatically.
Core Features & Use Cases
- Template-Based Scaffolding: Generates
qa/browser-flows/<id>.md from qa/browser-flows/_template.md with frontmatter populated from CLI-style arguments.
- Slug and Field Validation: Enforces URL-safe lowercase-dash IDs, requires
id, title, and resources, and prompts for missing values before writing.
- Optional Metadata Handling: Supports
parallel_safe, conflicts_with (always serialized as a YAML list), goal, preconditions, and cleanup sections.
- Use Case: A QA engineer needs a new flow verifying conversation rules. They run the command with
--id=conversation-rules-check --title="Conversation rules" --resources=conversation-rules --goal="Verify rules apply" and get a ready-to-edit spec file without touching the template manually.
Quick Start
Ask the assistant to create a new QA flow with id "login-check", title "Login flow", resources "auth", and a goal describing what the flow verifies.