ForgeOne Flow
Observa cómo está cableado tu workspace de IA: agents · skills · tools · prompts (canal primario VS Code + Copilot; Cursor docs-ready), con un mapa interactivo. Opcionalmente gobierna el trabajo con stages, gates humanos y evidencia en .forgeone/.
| Capacidad |
Uso |
| Workspace Map — red Copilot/VSC (gancho) |
ForgeOne Flow: Open Workspace Map |
| Sidebar — AI workspace · Flow (optional) |
Activity Bar → ForgeOne Flow |
| Pipeline view — timeline gates (opt-in) |
ForgeOne Flow: Open Pipeline View |
| Ecosystem — salud multi-repo (bajo Flow) |
Sidebar · forgeone workflow status-all |
| CLI — workspace map/advice, status, record, metrics |
ver Instalación |
| Workspace proof — Advice digest para PR |
Map Copy digest / forgeone workspace advice --markdown |
MCP — el agente reporta contexto, verify y gates (by: agent:*) |
forgeone mcp serve |
El Map es un inventario en disco, no una traza en vivo del chat de Copilot/Cursor.
.forgeone/ es opcional — no hace falta Init para ver agents/skills/tools.
Idioma UI: Settings → forgeoneFlow.uiLocale (auto | en | es) — auto sigue el Display Language del IDE.
See the Map
Real fixture (examples/workspace) — Map → Advice → act (no Pipeline).
Canvas: Copilot surfaces wired with edges and warnings.
Advice: Create paired prompt and Open agent (tools) close Improve without leaving the Map.
Ideal overlay: ghost “expected paired prompt” before you Apply.
Instalación
VS Code: Extensions → ForgeOne Flow (publisher anghelll) · Marketplace.
Forge One family: Flow is part of the Forge One toolkit from the same publisher, alongside BDD Guardian (step binding / quality) and BDD Pilot (run/debug features). Flow observes the AI workspace map; Guardian and Pilot focus on BDD. BDD Jarvis is not published on the Marketplace yet.
Cursor: paths / Map filter / DEMO prove docs-ready · install vía Open VSX ⏸ (hold ops). Listing reservado: Open VSX — anghelll/forgeone-flow.
CLI:
npm install -g forgeone-flow
forgeone workspace map
forgeone workspace advice --markdown # portable proof for PRs (same as Map Copy digest)
# o, desde este repo (desarrollo):
npm install && npm run forgeone -- workspace map
Empezar
Ver el cableado (sin Init): Activity Bar → ForgeOne Flow → sección AI workspace → Open Workspace Map (o Command Palette). Prueba el fixture abriendo examples/workspace como carpeta.
Gobernanza (opcional): sección Flow (optional) → Init workflow → Record Gate.
Desde la CLI:
cd tu-repo
forgeone workspace map
forgeone workflow init # opcional
forgeone workflow status
Más detalle: demo · adopción · changelog.
Documentación del repo
Workflow state
Estado actual y gates pendientes en el repo.
forgeone workflow init
forgeone workflow init --spec-path path/to/spec.md
forgeone workflow new-slice --workflow-id my-slice
forgeone workflow status
forgeone workflow validate
| Archivo |
Rol |
schema/workflow-state-v1.schema.json |
Schema |
examples/workflow-state.example.json |
Ejemplo |
.forgeone/workflow-state.json |
Estado activo (gitignored) |
forgeone workflow status [--file <path>]forgeone workflow validate [path]
Events y gates
Historial append-only de gates y evidencia.
forgeone workflow record alineado-pasa-a-spec
forgeone workflow history --limit 5
| Archivo |
Rol |
schema/workflow-event-v1.schema.json |
Schema |
examples/events.example.jsonl |
Ejemplo |
.forgeone/events.jsonl |
Log activo (gitignored) |
forgeone workflow record <gate> [--phrase "..."] [--by name]forgeone workflow history [--limit N]
Hooks (opt-in)
npm run hook:install
npm run pre-commit:warn
npm run hook:uninstall
Pre-commit: avisa si hay gates pendientes o eventos desalineados; no bloquea el commit.
Post-commit: si el gate commit está pendiente, lo registra con el sha (by: post-commit-hook).
Workflow definitions
Stages y gates por proyecto. Sin archivo custom, usa el pipeline por defecto.
cp examples/workflow-def.example.json .forgeone/workflow-def.json
forgeone workflow validate
Schema: schema/workflow-def-v1.schema.json.
Context trail
Registra qué contexto usó el agente (packs y archivos de configuración detectados).
forgeone workflow context-record --note "contexto del slice"
forgeone workflow context-record --pack path/to/pack.json
Detecta, entre otros: .cursor/rules, .github/copilot-instructions.md, AGENTS.md, CLAUDE.md.
MCP server
forgeone mcp serve [--path <repo>]
| Tool |
Efecto |
flow_status |
stage, pendingGates, def activa |
flow_history |
últimos eventos del slice |
flow_context_record |
evento context |
flow_verify_record |
evento verify |
flow_record_gate |
gate pendiente con by: agent:<nombre> |
Cursor (.cursor/mcp.json) o VS Code (.vscode/mcp.json):
{
"mcpServers": {
"forgeone-flow": {
"command": "npx",
"args": ["-y", "forgeone-flow", "mcp", "serve"]
}
}
}
Governance report
forgeone workflow report
forgeone workflow report --workflow-id <id>
forgeone workflow report --all [--path <dir>]
forgeone workflow report --json
Incluye actores por gate, verify por capa, contexto y warnings (gates viejos, ship sin capa A, slice sin contexto). También en la sección Governance del pipeline view.
Extensión VS Code
Vista en la Activity Bar (ForgeOne Flow): workflow activo, stage, gates, evidencia, métricas, ecosystem y acciones de registro. Comando ForgeOne Flow: Focus Panel para abrir el panel.
| Acción |
Efecto |
| Refresh Workflow |
Relee state y events |
| Record Gate |
Quick pick de pendingGates |
| Verify-record (Capa A / B) |
Registra verify |
| Open Pipeline View |
Webview del pipeline |
Desarrollo local:
npm install
npm run compile
npm run package # → forgeone-flow.vsix
# Extensions → Install from VSIX…
Publicación maintainer: docs/RELEASE.md.
Profiles
forgeone profile detect
forgeone profile detect --path /path/to/repo
forgeone profile list
forgeone profile verify-suggest
Perfiles: vscode-extension, node-library, dotnet-app, python-app, go-app, rust-app, docs-repo, entre otros.
Índice: workflows/profiles/README.md.
Metrics y verify-record
forgeone workflow metrics
forgeone workflow verify-record --layer A --command "npm run verify:local" --result pass
Capas A / B / C: ver workflows/verification-layers.md.
Status multi-repo
forgeone workflow status-all --path ~/workspace
forgeone workflow status-all --path ~/workspace --json
Artefactos en tu repo
.forgeone/
workflow-state.json # etapa y gates pendientes
events.jsonl # historial
workflow-def.json # opcional — definición custom
context-pack.json # opcional — schema context-pack-v1
Licencia
MIT — LICENSE.
