Dev · AgentFlow CLI
Lancer l'implémentation d'une feature ou tâche
CLI path: agentflow dev
When to use
Workflow commands advance tracked features across spec → plan → implementation → verification → reporting guardrails before opening a merge request.
Original CLI synopsis: Lancer l'implémentation d'une feature ou tâche
Usage
agentflow dev [flags]Options
| Flag | Scope | Default | Description |
|---|---|---|---|
--agent | Local | cursor | Agent d'implémentation |
--dry-run | Inherited | false | Simuler les exécutions sans lancer d'agent ni commandes externes |
--force | Local | false | Relancer une étape déjà réussie |
--task | Local | (empty) | ID de tâche à implémenter |
Examples
agentflow devWire richer samples through cobra.Command.Example when the happy path warrants copy/paste-friendly automation beyond this scaffold.
What happens internally
- Validates CLI arity, honours the global --dry-run switch, resolves repository metadata, hydrates SQLite-backed bookkeeping, then calls façade orchestration wrappers for the requested lifecycle stage.
- Persists deterministic run identifiers so status and resume can continue automation deterministically afterward.
Failure modes
- Cobra rejects unknown flags or arity mismatches before any repository side effects occur.
- AgentFlow cannot resolve scaffolding when the command is invoked outside an initialised checkout.
- Delegated subprocesses (git, MCP hosts, editor agents, etc.) can exit non-zero and bubble errors verbatim.