Menu
Use when writing or updating Engineering session notes. Covers the format, what to include, and filing location.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
AI feature engineering — llama, embeddings, RAG quality, inference reliability, cost/token discipline.
System architecture, structured code review bar, and technical documentation.
Backend HTTP API, SQLite, Qdrant, integration contracts, schema and migration safety.
Maturity / inspection pass over [ORG_NAME] code sections (BCS). Load your org’s code-sections ledger, run verify ladder, update shared_context summary on main when columns change.
Data pipelines, ingest, remediation, entity quality — PDF/docs through to vector store.
Decision continuity, handoffs, supersession — Engineering Orchestrator (Mike) accountable; pair with session-notes.
| name | session-notes |
| description | Use when writing or updating Engineering session notes. Covers the format, what to include, and filing location. |
At the end of every Engineering work session, or during the session when significant work is completed. Session notes are the Engineering equivalent of HQ's memory log.
[ENGINEERING_REPO]/notes/session_YYYY-MM-DD.txt
One file per day. Append to existing file if multiple sessions in a day.
=== Session: YYYY-MM-DD HH:MM CDT ===
## Summary
[2-3 sentence overview of what was accomplished]
## Work Completed
- [Specific task/change with file references]
- [Test results: N passing, N new, N regressions]
- [Branch: branch-name, commit: hash]
## Decisions Made
- [Decision with rationale]
- [XD-NNN reference if cross-org]
## Issues Found
- [Bug/gap with severity and owner]
## Next Steps
- [What needs to happen next]
- [Blockers for HQ if any]
## Files Changed
- [List of key files modified]
../../../shared_context/project_status_sync.STUB.md if milestones change