flow

Design and operate state machine workflows with FLOW.md and WORK.md.

11|2|Updated Apr 7, 2022
One-click install
npx skills add https://github.com/nullhack/temple8 --skill flow-nullhack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow
Source: https://github.com/nullhack/temple8/tree/main/.opencode/skills/flow
Command: npx skills add https://github.com/nullhack/temple8 --skill flow-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a robust framework for designing and operating state machine workflows by providing a minimal two-file pattern (FLOW.md and WORK.md), enabling predictable execution and auditable transitions.

Core Features & Use Cases

  • Two-file pattern: FLOW.md defines the static rules for the workflow, while WORK.md tracks the active item and its transitions.
  • Deterministic and observable: transitions are driven by clearly defined guards, owners, and actions, making the workflow detectable from the filesystem.
  • Use cases: session initiation, creating a new workflow, and modifying an existing workflow to evolve processes over time.

Quick Start

Load FLOW.md and WORK.md to begin a new session and review the workflow rules.

Frequently Asked Questions about flow

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

FAQPage Schema
How do I manage deterministic state machine workflows across multiple sessions?

You can manage deterministic state machine workflows across sessions by applying a two-file pattern: a static FLOW.md for transition rules and guards, and a dynamic WORK.md to track active items and their state changes.

What is the best way to track work items and state transitions in an automated workflow?

The best way to track work items in an automated workflow is using a dynamic WORK.md file that records active items and transitions, driven by clearly defined guards and owners specified in a static rules file.

How do I design a finite state machine workflow that remains observable from the filesystem?

Design a finite state machine workflow by separating static transition rules into FLOW.md and active state tracking into WORK.md, making the workflow states and transitions fully observable and detectable directly from the filesystem.

Can I use markdown files to enforce session management rules and guard conditions?

Yes, you can enforce session management rules and guard conditions by defining them in a static FLOW.md file, which dictates deterministic transitions and session behaviors alongside a dynamic WORK.md file for tracking.

When should I use a two-file state machine pattern for workflow automation?

Use a two-file state machine pattern when you need predictable execution and auditable transitions for session management tasks requiring deterministic state changes, guards, and work-item tracking across multiple sessions.

How do I start a new session and review existing workflow rules?

To start a new session, load the FLOW.md and WORK.md files to review the established workflow rules, check the current active work item, and verify the required deterministic state transitions and guards.