Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Deterministic Workflows

One Command Surface

Local and CI Parity

Devflow provides stable commands and profile-driven orchestration for building, testing, and validating software across stacks.

What Devflow Solves

  • Consistent command contract (setup, fmt, lint, build, test, check, release, ci).

  • Selector-based precision (test:unit, check:pr, ci:generate).

  • Config-first policy (targets.*) with deterministic CI generation.

Who It Is For

  • Teams maintaining one or many repositories with inconsistent local/CI workflows.

  • Engineers who want predictable quality gates without custom per-repo script sprawl.

  • Contributors extending workflow behavior through explicit extension capabilities.

Mission and Objectives

Mission: make software delivery workflows consistent, repeatable, and easy to reason about.

Objectives:

  • define one canonical command surface across stacks

  • keep local and CI behavior aligned from the same config contract

  • make workflow policy explicit and versionable (devflow.toml)

  • enable safe extensibility through capability-checked extensions

Documentation Paths