astra-logbook
Skill2 starsChanged 2 months agoMITView on GitHub
Fase 7 de ASTRA (Bitacora). Escribe el devlog del sprint en docs/astra/devlogs/ (direcciones registradas, costos estimados vs reales, hallazgos y cierres, deuda, aprendizajes) y verifica que deployments.json, orbit.md, chart.md y audit.md digan la verdad del estado final. Usar cuando el usuario dice "bitacora", "devlog", "cerrar el sprint", "documentar lo desplegado".
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- astra-auditSkill
- astra-buildSkill
- astra-chartSkill
- astra-launchSkill
- astra-logbookSkill
- astra-orbitSkill
- astraSkill
- astra-standardsSkill
- astra-testnetSkill
- astra-auditSkill
- astra-buildSkill
- astra-chartSkill
- astra-launchSkill
- astra-logbookSkill
- astra-orbitSkill
- astraSkill
- astra-standardsSkill
- astra-testnetSkill
- astra-auditSkill
- astra-buildSkill
- astra-chartSkill
- astra-launchSkill
- astra-orbitSkill
- astraSkill
- astra-standardsSkill
- astra-testnetSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
No embellecer: los costos reales y los hallazgos van como fueron.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
astra-logbook — Fase 7: Bitácora
Cuándo
Al cerrar un sprint (después del Lanzamiento, o al pausar un sprint que no llegó). Produce docs/astra/devlogs/YYYY-MM-DD-<slug>.md.
Pasos
- Lee
.astra/deployments.json(astra deployments list),docs/astra/orbit.md,chart.md,audit.md,launch.mdy el historial de commits del sprint. - Escribe el devlog desde
templates/devlog.template.md: cadena, fases recorridas y fechas de gates; qué se hizo; tabla de direcciones registradas (solo las del registro); costos estimados vs reales por operación (A10); auditoría (hallazgos por severidad, cómo se cerraron, cuáles se aceptaron y por quién); lo que quedó fuera y la deuda; aprendizajes. - Coherencia: si el devlog dice algo que un artefacto no dice (una dirección no registrada, un cambio de diseño no anotado en la Carta, un hallazgo cerrado que sigue "abierta" en la auditoría), corrige el artefacto, no solo el devlog.
astra checken OK sobre el commit final. Commitastra: bitácora <slug>.
No hacer
- Sin claves, sin datos personales, sin direcciones que no estén en el registro.
- No embellecer: los costos reales y los hallazgos van como fueron.
Done
Devlog escrito y ningún artefacto contradice lo desplegado.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

