← ClaudeAtlas

tablerolisted

Trigger: tablero, estado del proyecto, dónde vamos, avance, project status, status board. Publica el estado de un proyecto como artefacto: métricas, backlog por fases, costos y Gantt simulable.
sergiohidalgo-pro/tablero · ★ 0 · Data & Documents · score 75
Install: claude install-skill sergiohidalgo-pro/tablero
## Activation Contract Load when the user asks for the state of a project or sub-project: "tablero", "dónde vamos", "estado", "avance", "cómo vamos", "status board", or asks to update a tablero published earlier. Do NOT load for a one-line status answer, a commit log summary, or a plain checklist. ## Hard Rules - Every number comes from a primary source read in THIS session (git, pipeline runs, cloud CLI, tickets, transcripts). Never from memory or a summary. If a figure cannot be sourced, mark it as an estimate and say what would confirm it. - Hours are session hours with a human present, cutting pauses > 20 min — never pipeline wall-clock. State the cutoff rule in the artifact. - `Σ act` across `PHASES` must match total `SESSIONS` hours within 0,5 h. Reconcile the data before publishing; never adjust one side to hide the gap. - Costs are incremental: only what is new. Name the price source and date, and list what is excluded because it was already paid. - Never invent qualitative claims about rhythm or productivity. `EVAL_EXTRA` entries need a time and a result. - `CONTEXTO.estado` measures whether the project can proceed unblocked, NOT how much is done. Green only when nothing but hours is missing; red when a decision, credential or answer someone else owes is what stands in the way. Every `falta` entry names the owner or the input it waits on. - The `stamp` is one short plain-text line (date-time · milestone in ≤ 8 words �� sources, ≤ 120 characters, no `<b>`/`<code>`