Lightweight skill for AI automation flows.
Set of commands to structure and drive the cycle of analysis, review, implementation and validation of a request or task.
Bash
curl -fsSL https://github.com/RivoLink/flow/raw/main/scripts/install.sh | bashPowerShell
irm https://github.com/RivoLink/flow/raw/main/scripts/install.ps1 | iexThe script will prompt interactively for the harness (Claude, Codex, or Gemini).
To pass options, download the script first then run it with arguments.
Bash
curl -fsSL https://github.com/RivoLink/flow/raw/main/scripts/install.sh -o flow.sh
bash flow.sh --claude --user --as-command --frPowerShell
irm https://github.com/RivoLink/flow/raw/main/scripts/install.ps1 -OutFile flow.ps1
./flow.ps1 -Claude -User -AsCommand -Fr| Flag | Description | Default |
|---|---|---|
claude | codex | gemini |
Target harness | Interactive prompt |
user | project |
Installation scope | project |
as-skill | as-command |
Installation mode | as-skill |
en | fr |
Language for .md files | en |
| Command | Description |
|---|---|
flow help |
Display available commands and workflow |
flow init |
Initialize the project working environment |
flow best-practices |
Add best practices to the project reference |
flow asking |
Create a request file from a prompt |
flow analysis |
Analyze a request without modifying code |
flow review |
Critical review of the analysis |
flow process |
Apply code modifications |
flow validate |
Critical review of code modifications |
flow re-process |
Fix code according to the validation report |
The cycle starts with asking and ends when validate returns Valid.
asking ──> analysis <──> review ──> process ──> validate <──> re-process
- Loop 1:
analysisandreviewuntil the analysis is consistent. - Loop 2:
validateandre-processuntil the status is "Valid".
Flow drives a task through a fixed cycle. Each step reads and writes files
under .flow/, so progress is always inspectable on disk.
Artifacts
.flow/asks/<slug>.txt: the reformulated request..flow/outs/<slug>-analysis.md: the analysis. AReview Reportsection and then aValidation Reportsection are appended in place over the cycle..flow/docs/best-practices.md: project conventions read byprocessandre-process.
Two feedback loops
- Loop 1 :
analysis↔review. Iterate until the analysis is coherent and every review question is answered. - Loop 2 :
validate↔re-process. Iterate until the validation status isValid.
Exit
The cycle ends when validate returns Valid.
Workflow commands first, then setup and meta.
- Purpose : Turn a free-form prompt into a clean request file.
- Input : Prompt text.
- Output :
.flow/asks/<slug>.txt.
- Purpose : Produce a detailed analysis of the request. No code change.
- Input :
.flow/asks/<slug>.txt. - Output :
.flow/outs/<slug>-analysis.md.
- Purpose : Critique the analysis for inconsistencies, questions and risks.
- Input : Analysis path.
- Output :
Review Reportsection appended to the analysis.
- Purpose : Apply code modifications by following the analysis.
- Input : Analysis path.
- Output : Source code modifications.
- Purpose : Critique the code modifications against the analysis.
- Input : Analysis path.
- Output :
Validation Reportsection appended to the analysis, with statusValidorNot valid.
- Purpose : Fix the points raised by the last validation report.
- Input : Analysis path with a
Validation Report. - Output : Source code fixes.
- Purpose : Initialize the project working environment.
- Input : None.
- Output :
.gitignoreentry and the.flow/directory tree.
- Purpose : Record project conventions used by
processandre-process. - Input : Comment text.
- Output : Appended to
.flow/docs/best-practices.md.
- Purpose : Print the command list and the workflow diagram.
- Input : None.
- Output : Console message.
Flow is available in English (en, default) and French (fr).