Get Started
DocsTrack 2pipeline
/llms.txt
Core Workflow5 min readbrevio-core v0.11.1

The 5-Step Single-Task Pipeline (connect → plan → build → qa → pr)

Plain-English Summary (For Anyone)

A local, single-task workflow that ends in a checked pull request body

brevio-core task runs five commands in order on your machine: connect (detect the stack and write starter specs), plan (write a task plan from a repository map), build (prepare the task and apply deterministic fixes), qa (run the pre-PR gates and count findings) and pr (write the pull request body). It makes no model call.

Why this matters:
Each stage writes a file you can read, so you can see what the next stage was given.
The qa stage compares your task's diff with the base, so old findings are not blamed on the task.
You can run the stages one at a time, or all at once with brevio-core task.
When to use:Use `brevio-core task '<task description>'` to run the whole workflow for one task, or run the stages one by one.
Technical Contract (For Engineers)
Line-level rules
CLI Invocation Signature:
brevio-core task '<task description>' [--root ROOT] [--no-fix] [--diff BASE] [--json]
Latency / Execution
Not measured for 0.11.1
Token Cost
No model call. No API key.
Exit Codes
0 = success; 1 = findings; 2 = usage error
Artifacts & Files Generated:
.brevio/task_plan.json.brevio/TASK_PLAN.md.brevio/qa_report.json.brevio/PR_BODY.md
Visual Execution Pipeline
5-Stage Progressive Flow
01--dry-run first
Connect
Detect the stack and coding clients, write CLAUDE.md, CONSTITUTION.md and roadmap.json
02Local
Plan
Write .brevio/task_plan.json and TASK_PLAN.md from a PageRank repository map
03Fixers
Build
Prepare the task and apply the deterministic fixes (--no-fix to skip)
04--all for repo
QA
Run the single-task pre-PR gates and count findings of the task's diff
05Markdown
PR
Write .brevio/PR_BODY.md from what the gates found

Why Work on One Task at a Time

In Plain English:A coding agent that edits many files at once is hard to review. brevio-core keeps the workflow to one task, with a file written at each stage.
The five commands are plain steps of one local workflow: connect, plan, build, qa and pr. They run in the folder you start them in, and they write under `.brevio/`. `brevio-core task` runs all five. Since 0.10.0, `check`, `qa` and `pr` compare with the base that `scan --diff` uses (origin/main, else main, else HEAD), not with HEAD, and `qa` and `pr` count the task's own changes (`--all` counts the whole repository).

01 Connect: Stack Detection & Starter Specs

In Plain English:brevio-core looks at your repository to see what language and coding clients you use, and says what it would write before it writes anything.
`brevio-core connect` detects Python, TypeScript and Node code and the coding clients on the machine, and writes `CLAUDE.md`, `CONSTITUTION.md` and `roadmap.json`. `--dry-run` lists the files it would write and writes nothing. At a terminal it asks before writing; `--yes` writes without asking and `--force` overwrites existing spec files.

02 Plan: A Task Plan from the Repository Map

In Plain English:Breaks your request down into a plan file before any code is changed.
`brevio-core plan '<task>'` builds a Personalized PageRank repository map (`--budget`, default 2000 tokens) and writes `.brevio/task_plan.json` and `.brevio/TASK_PLAN.md`. It makes no model call.

03 Build: Task Preparation & Deterministic Fixes

In Plain English:Prepares the task and applies the fixes that have exactly one correct rewrite.
`brevio-core build` executes the build preparation for the task and applies the deterministic fixes of the rules that have one (R5.4, R9.2, R10.1 and R18.2 in 0.11.1). `--no-fix` leaves the files as they are. Findings without a fixer are reported for a person or your coding agent to fix.

04 QA: Pre-PR Gate Verification

In Plain English:Counts the findings of your task's diff and says what to do next.
`brevio-core qa` runs the single-task pre-PR gates and counts the findings of the task's diff (`--all` counts the whole repository). Findings are printed up to a limit, and the full list is written to `.brevio/qa_report.json`. For the repository-wide flight check use `brevio-core check`: rules, test custody, test imports, conflict markers and complexity. Browser tests are not part of brevio-core.

05 PR: The Pull Request Body

In Plain English:Writes the text of a pull request from what the gates found.
`brevio-core pr` runs the QA gates and writes `.brevio/PR_BODY.md` from what they found. It writes the body from files on disk and does not open the pull request.
Running the Complete Task Workflow
Fixed (After)Exit 0
brevio-core task "Add idempotency key check to POST /api/v1/charges"
Terminal Output:
brevio-core connect --dry-run
brevio-core plan "Add idempotency key check to POST /api/v1/charges"
brevio-core build
brevio-core qa
brevio-core pr "Add idempotency key check"
# Files written: .brevio/task_plan.json, .brevio/TASK_PLAN.md, .brevio/qa_report.json, .brevio/PR_BODY.md

Interactive Rule Explorer

Explore the brevio-core rules and load their examples into the panel on the right.

129 / 129 rules