anchors flow

Operate the work flows (the puzzle of actions and results).

A FLOW is work driven by shape rather than by memory.

An ACTION (flows/actions/*.action.md) declares what it does and which RESULTS it
offers. A FLOW (flows/*.flow.md) fits actions together and says where each result
goes. What used to be a rule to remember ("NEVER close with a blocking gate red")
becomes the absence of a fitting: the BARRED result has no link to `done`.

Uso

anchors flow

Subcomandos

anchors flow build

Scan flows/ and write the flow graph into the map.

Uso

anchors flow build [flags]

Flags

Flag	Padrão	O que faz
--root	.	project root

anchors flow next

The VALID exits of a step — the command that drives.

Answers "from here, where can I go", instead of listing everything and
asking someone to choose. It is what separates having a flow from having one more
document.

Uso

anchors flow next <step> [flags]

Flags

Flag	Padrão	O que faz
--root	.	project root

anchors flow show

Draw the flow — assembled at RUNTIME from the graph.

Draws the flow from the graph, never from a stored diagram.

A versioned diagram ages against the flow it describes, and the repository already
measured what that costs (see the docs-fresh gate). Here the drawing is derived,
so it cannot diverge.

Uso

anchors flow show [flow] [flags]

Flags

Flag	Padrão	O que faz
--direction	TD	diagram direction: TD (top-down, tree-like) or LR (left to right)
--mermaid		emit the diagram as mermaid (boxes and arrows, for rendering)
--root	.	project root

A fila de trabalho — família

Comandos da mesma família — o que distingue cada um:

Comando	O que faz
anchors next	Pull and claim the next item from the queue (the worker calls this)
anchors queue	List live tasks (the work the watcher queued)
anchors work	Emit the work prompt of a stage (spec|code|feature|test|review) for a target
anchors done	Close claimed task(s) (moves to the .anchors/done/ history)
anchors drop	Discard a task from the queue without completing it (removes; does not archive)
anchors reclaim	Return to the queue the tasks stuck in claimed (dead worker)
anchors deliver	Record the delivery of a stage — the review trigger
anchors decided	Release the card escalate --for-user stopped, once the decision is made
anchors discard	Take off the board the card that no longer makes sense, without deleting it
anchors unblock	Open the work card that unblocks a card stuck in needs-user
anchors escalate	Open the issue for a change needed in the plan or the spec
anchors report-bug	Report a bug in Anchors itself at github.com/co2-lab/anchors
anchors synthesize	Two PRs conflicting in CONTENT become a synthesis card
anchors watch	The background watcher: sees changes and QUEUES work
anchors monitor	Watch the project’s long processes: one line when one starts, stalls, dies or ends
anchors flow	Operate the work flows (the puzzle of actions and results)
anchors board	The project board — published by the pipeline, or served live

---

---

---

---

---

O Anchors permite desenvolvimento assistido por IA contínuo e ordenado através de uma fila reativa de tarefas.

---

1. O Ciclo do Watcher e da Fila

1. anchors watch: Roda em background. Quando um arquivo é salvo (ex: order.spec.md), o watcher percebe o que falta e enfileira a próxima ação (criar-feature, implementar-codigo, rodar-testes).
2. anchors queue: Lista as tarefas pendentes na fila.
3. anchors next: O agente de IA chama este comando para puxar o próximo card sem depender de prompting manual.
4. anchors work <alvo>: Emite o prompt contextual com as instruções exatas daquela etapa.
5. anchors deliver: O agente registra a entrega; o Anchors valida o resultado com gates.
6. anchors done <id>: Arquiva o card concluído no histórico.

---

2. Tratando Bloqueios e Escalonamento

• anchors escalate: Se a IA encontra uma ambiguidade na regra, ela estaciona o card em needs-user e abre uma issue.
• anchors unblock: Quando o desenvolvedor responde a dúvida, este comando destrava o card.
• anchors decided <card>: Retoma o fluxo com a decisão humana registrada.