Skip to content

JSON format

JSON supports the same schema as YAML. Use it when a workflow is generated by another tool or when your team prefers strict JSON files.

Example

json
{
  "harness": "claude-cli",
  "model": "sonnet",
  "steps": [
    {
      "name": "inspect",
      "prompt": "Inspect @src/server/ and explain the main request flow."
    },
    {
      "name": "review",
      "resumeSession": true,
      "prompt": "List the two most important weaknesses in that flow."
    }
  ],
  "finalStep": {
    "prompt": "Summarize the recommended next action."
  }
}

When to choose JSON

  • another tool creates workflows for you
  • you want a format with stricter editing rules
  • you plan to validate or transform workflows in external tooling

Use the same workflow schema reference regardless of file format.

Source-available under the FlightPath Commercial License.