Summary
When crew complete missions that produce reports (triage, analysis, research), the Admiral should automatically save them to docs/ before recalling the crew. This workflow should be baked into the admiral workspace template so every new starbase gets it out of the box.
Motivation
Currently, crew reports only live in comms history or fleet crew observe output — both ephemeral. If you recall a crew before saving, the report is lost. We've been doing this manually and it should be a default behavior.
Scope
- Update the admiral workspace template CLAUDE.md — add a rule instructing the Admiral to save crew reports to
docs/{sector}-{report-type}-{YYYY-MM-DD}.md before recalling crew
- Ship
docs/workflow-crew-reports.md in the template — documents when/how/why to save reports
- Ensure
docs/ directory exists in the template scaffold
Out of Scope
- Shell hooks or automation — this is an LLM instruction in CLAUDE.md, not a script
- Changes to the Fleet CLI or comms system
Reference
Working implementation already exists in starbase 432a3a:
Summary
When crew complete missions that produce reports (triage, analysis, research), the Admiral should automatically save them to
docs/before recalling the crew. This workflow should be baked into the admiral workspace template so every new starbase gets it out of the box.Motivation
Currently, crew reports only live in comms history or
fleet crew observeoutput — both ephemeral. If you recall a crew before saving, the report is lost. We've been doing this manually and it should be a default behavior.Scope
docs/{sector}-{report-type}-{YYYY-MM-DD}.mdbefore recalling crewdocs/workflow-crew-reports.mdin the template — documents when/how/why to save reportsdocs/directory exists in the template scaffoldOut of Scope
Reference
Working implementation already exists in starbase
432a3a:admiral/CLAUDE.mdRule fix: prevent terminal viewport jumping to line 0 on tab/window switch #7admiral/docs/workflow-crew-reports.md