Capability · Control layer

Markdown SOPs that cascade through products, goals, projects, and tasks.

Workflows encode how your team actually does work. Authored in markdown, matched to entities by label and pattern, injected into prompts at the right discovery level. Drift detection catches when agents deviate; playbook graduation auto-proposes a workflow after five related ad-hoc memories.

Markdown
Source of truth
Cascades
Product → task
5+ memories
Auto-graduation trigger
3 modes
Discovery / lead / participant
packwolf.app · Workflows
Live screenshot
Workflows screenshot
The workflow editor. Author in markdown, version every change, see which products and tasks reference each workflow.
What it actually does

The parts that make this work.

Plain markdown, no DSL.

Workflows are markdown files. Operators read them, edit them, version them. Engineers don't have to learn a workflow DSL, neither do their PMs.

Cascade matching is automatic.

A product's workflow spawns a goal workflow when goals are created. Goal workflows spawn project workflows. Project workflows spawn task workflows. Institutional procedure flows through the hierarchy.

Three context modes.

Discovery ("these workflows exist"), lead ("you're driving this one"), participant ("someone else is driving, here's your part"). Agents see only the relevant slice.

Drift detection catches deviation.

When agents repeatedly deviate from a documented step, the system flags the drift and proposes either updating the workflow or coaching the agent.

Playbook graduation.

After five related ad-hoc playbook memories, the system proposes a formal workflow. Repeated emergent behavior becomes codified procedure, operator-approved, of course.

Versioned + revertable.

Every workflow edit creates a new version. Revert restores any prior. The DB caches parsed workflows; the markdown is the source of truth.

How it works

The path through workflows.

  1. 01

    An operator authors the SOP.

    Markdown file, plain English. Steps with optional frontmatter for required tools, skills, approvals, and timeouts.

  2. 02

    Pattern matching attaches it.

    Workflows match products, goals, projects, and tasks by label or title pattern. Matches happen at runtime, not at author time.

  3. 03

    Context mode picks the slice.

    Lead agents see the full procedure. Participants see only the steps they're responsible for. Discovery shows just titles.

  4. 04

    Workflow injects into the prompt.

    At the right context mode, the matched workflow's relevant steps inject into the system prompt. The agent acts with full procedural awareness.

  5. 05

    Drift detection runs in background.

    If agents repeatedly skip step three or substitute step four, the maintenance scheduler logs the drift and proposes a refinement.

  6. 06

    Playbook graduation proposes new workflows.

    Five related ad-hoc memories from the same agent group → a workflow proposal lands in the operator's approval queue.

markdownA workflow in plain markdown, what operators actually write
# Weekly competitive intel cycle

Match: products labelled "research"
Required tools: web_search, file_write
Required skills: deep-research

## Step 1 — Pull the news
Search the last seven days for product launches, funding events, and
major hiring moves at our top five tracked competitors.

## Step 2 — Triangulate
For each finding, find at least two independent sources. If you can't
find two, mark it "unconfirmed" and continue.

## Step 3 — Brief
One page max. Lead with what changed, not what's the same. End with
"watch list" — three things to verify next week.

Approvals: peer review before publish.
Common questions

Things engineers actually ask.

Markdown is what your team already writes for SOPs. Engineers can review it. PMs can edit it. Git tracks history. Visual builders look great in demos but become illegible at the scale of dozens of running workflows.

Related capabilities
CapabilityHeartbeatsCapabilityTask managementCapabilityApprovals
Source: docs/WORKFLOWS.md

See it in your workspace.

Closed-beta cohorts are small. Tell us what you'd want this capability to handle for your team.

Request beta access