skills.rest
brian-wijaya
brian-wijayaCOMMUNITY
Explore all skills by this author →
GitHub

workflow-trace

Generate a two-paragraph Bidirectional Interaction Trace from a user workflow sequence.

Updated Aug 23, 2026
Search Tags:#workflow#documentation#trace#interaction#commands#BIT#state-transition
One-click install
npx skills add https://github.com/brian-wijaya/dotfiles --skill workflow-trace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-trace
Source: https://github.com/brian-wijaya/dotfiles/tree/main/.claude/skills/workflow-trace
Command: npx skills add https://github.com/brian-wijaya/dotfiles --skill workflow-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts user workflows into a compact Bidirectional Interaction Trace (BIT), enabling precise documentation, analysis, and comparison of procedures.

Core Features & Use Cases

  • Generate a two-paragraph BIT for any interactive workflow.
  • Produce deterministic state transitions suitable for documentation, auditing, and onboarding.
  • Use cases include workflow optimization, process understanding, and rapid scenario comparison.

Quick Start

Provide a workflow input as a continuous stream of actions; the skill returns a two-paragraph BIT.

Frequently Asked Questions about workflow-trace

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

FAQPage Schema
How do I document a workflow as a machine-readable interaction trace?▼

To document a workflow as an interaction trace, provide a continuous stream of actions to generate a Bidirectional Interaction Trace (BIT). The output is a strict two-paragraph format separating user input from program output for analysis.

What is a Bidirectional Interaction Trace (BIT) for workflow documentation?▼

A Bidirectional Interaction Trace (BIT) is a compact, lossless representation of user-system interactions. It formats workflows into two paragraphs: the first contains only user input, and the second describes visible state changes from program output.

How do I generate a state transition trace for process auditing?▼

To generate a deterministic state transition trace for process auditing, input your workflow sequence. The system produces a two-paragraph BIT mapping user actions to visible program state changes suitable for comparison.

Can I use this to create lossless documentation for user-system interactions?▼

Yes, you can create lossless documentation for user-system interactions. The skill converts any workflow sequence into a compact BIT, ensuring precise documentation without losing visible state transition details.

What is the best way to convert a sequence of commands into a compact trace?▼

The best way to convert commands into a compact trace is to provide the workflow as a continuous stream of actions. The skill returns a deterministic two-paragraph BIT separating user inputs from program outputs.

Does this workflow trace format separate user input from program output?▼

Yes, the workflow trace format strictly separates user input from program output. The first paragraph contains only user input, while the second paragraph contains only program output describing visible state changes.

Related Skills

Explore More Software Engineering Skills→
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
zhongadamwangzhongadamwang

change-impact-analysis

Trace change propagation across EDPS process hierarchies and output impact JSON.

Community
Intermediate
jmolzjmolz

source-command-handoff

Generate a HANDOFF.md file documenting session state for the next agent.

Community
Advanced
jaimedhenriquesjaimedhenriques

excalidraw-diagram-generator

Generate Excalidraw diagrams from natural language descriptions.

Community
Advanced