68 lines
2.4 KiB
Markdown
68 lines
2.4 KiB
Markdown
---
|
|
description: "Vista cross-cutting de issues + flows. Subcomandos: today, weekly, search, dashboard. Mezcla los dos universos en una lista priorizable."
|
|
---
|
|
|
|
# /work — Vista cross-cutting issues + flows
|
|
|
|
Issues = trabajo de implementacion. Flows = casos de uso multi-app. `/work` los muestra juntos para responder "que hago ahora" sin saltar entre dos sitios.
|
|
|
|
## Sintaxis
|
|
|
|
```
|
|
/work today # top items prio alta + deps satisfechas (issues + flows)
|
|
/work weekly # review semanal: closed vs planeados
|
|
/work search "texto" # FTS sobre issues + flows + completed
|
|
/work dashboard # JSON consumible por tab Work (issue 0102)
|
|
```
|
|
|
|
## Implementacion
|
|
|
|
**Fase 1 (manual via Claude):**
|
|
|
|
El agente lee `dev/issues/*.md` + `dev/flows/*.md`, parsea frontmatter YAML, ordena por:
|
|
|
|
1. `priority: alta` primero.
|
|
2. `status: pendiente` con `depends` todos `completado` (no bloqueados).
|
|
3. Items con DoD/Acceptance >=80% (a punto de cerrar).
|
|
4. Fecha `updated` mas reciente.
|
|
|
|
Imprime tabla unificada:
|
|
|
|
```
|
|
KIND | ID | TITLE | PRIO | STATUS | NEXT STEP
|
|
issue| 0099 | datahub app launcher | alta | pendiente | revisar deps
|
|
flow | 0001 | hn-top-stories | high | pending | cerrar DoD user-facing
|
|
issue| 0100 | migrate issue frontmatter | alta | pendiente | ejecutar pipeline
|
|
...
|
|
```
|
|
|
|
**Fase 2 (cuando 0101 dev_console exista):**
|
|
|
|
`./apps/dev_console/dev_console work <subcomando> $ARGS`.
|
|
|
|
## Subcomandos
|
|
|
|
### `today`
|
|
|
|
Filtro: `priority in (alta, media)` + `status: pendiente` + dependencias resueltas. Max 10 items. Si hay >10, prioriza `alta` y avisa "N items pendientes en cola".
|
|
|
|
### `weekly`
|
|
|
|
Git log `--since='1 week ago'` sobre `dev/issues/completed/` y `dev/flows/completed/` -> tabla de items cerrados. Comparado con `created: <esta semana>` -> ratio in/out.
|
|
|
|
### `search "texto"`
|
|
|
|
`grep -ri` sobre `dev/issues/` + `dev/flows/` (incluido completed/), filtra por title/body. Output: `path:line: match`.
|
|
|
|
### `dashboard`
|
|
|
|
Output JSON estructurado para consumo por tab Work del `registry_dashboard` (issue 0102). Estructura:
|
|
|
|
```json
|
|
{
|
|
"issues": {"pendiente": [...], "in-progress": [...], "bloqueado": [...], "completado_24h": [...]},
|
|
"flows": [{"id": "0001", "dod_percent": 50, "user_facing_percent": 0, "...": ...}],
|
|
"telemetry": {"calls_24h": N, "violations_24h": N, "pending_proposals": N}
|
|
}
|
|
```
|