flows

Document Bottie workflows and audit specs against code for edge cases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Liquilab/Bottie --skill flows-liquilab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flows
Source: https://github.com/Liquilab/Bottie/tree/main/.claude/skills/flows
Command: npx skills add https://github.com/Liquilab/Bottie --skill flows-liquilab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps Bottie workflows to identify failure modes, handoff contracts, and edge cases, reducing debugging time and ensuring consistent behavior across workflows.

Core Features & Use Cases

  • Workflow catalog: documents primary, research, and operational workflows with triggers and frequencies.
  • Audit-ready: provides a framework to compare specs with code and surface discrepancies.
  • Edge-case planning: highlights uncovered edge cases to prevent bugs before release.

Quick Start

Map the primary Bottie workflows and run an audit to align specs with the code.

Frequently Asked Questions about flows

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

FAQPage Schema
How do I map trading bot workflows to detect edge cases and failure modes?

To map trading bot workflows for edge case detection, document primary, research, and operational triggers, then apply an audit framework to compare specs against code and highlight missing failure modes to prevent bugs before release.

What is workflow spec auditing and how does it surface code discrepancies?

Workflow spec auditing is the process of comparing documented workflow specifications against actual code execution. It surfaces discrepancies by enforcing a structured spec format and highlighting uncovered edge cases to ensure consistent behavior.

How do I identify missing edge cases in bot workflows before a release?

To identify missing edge cases before release, map your operational workflows and run an audit comparing the structured spec against the codebase. This highlights uncovered failure modes and missing handoff contracts.

Does workflow mapping support design reviews and development sprint audits?

Workflow mapping supports design reviews and development sprint audits by documenting primary workflows with triggers and frequencies. It verifies that operational workflows are spec-complete and aligned with code to ensure consistent behavior.

What is the best way to document workflow handoff contracts to reduce debugging time?

The best way to document workflow handoff contracts is to enforce a structured workflow spec format. This maps primary and operational workflows to identify failure modes and verify spec completeness against the code.