Josh Knapp
2dffef0767
All checks were successful
Build App / compute-version (push) Successful in 2s
Build App / build-macos (push) Successful in 2m47s
Build Container / build-container (push) Successful in 9m0s
Build App / build-linux (push) Successful in 4m41s
Build App / build-windows (push) Successful in 5m33s
Build App / create-tag (push) Successful in 3s
Build App / sync-to-github (push) Successful in 10s
The mission-control (Flight Control) project is being closed upstream. This embeds the project files directly in the repo under container/mission-control/, bakes them into the Docker image at /opt/mission-control, and copies them into place at container startup instead of git cloning from GitHub. Also adds missing osc52-clipboard, audio-shim, and triple-c-sso-refresh to the programmatic Docker build context in image.rs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.4 KiB
2.4 KiB
Mission Debrief — Project Crew
Crew definitions for post-mission retrospective. The Flight Director interviews both the human and a project-side Architect to capture strategic technical perspective.
Crew
Architect
- Context: {project}/
- Model: Sonnet
- Role: Provides architectural perspective on mission outcomes. Evaluates whether the system evolved well across flights, identifies structural issues, and assesses long-term maintainability of what was built.
- Actions: debrief-interview
Interaction Protocol
Architect Interview
- Flight Director loads full mission context (all flights, logs, debriefs, code)
- Flight Director spawns Architect to review overall system evolution
- Architect examines architectural changes across all flights
- Architect provides structured debrief input
Human Interview
- Flight Director interviews human with mission-level questions
- Covers coordination experience, outcome satisfaction, process feedback
Synthesis
- Flight Director synthesizes Architect input + human input + document analysis
- Generates mission debrief artifact
Template Variables
The Flight Director substitutes these variables in prompts at runtime:
| Variable | Description |
|---|---|
{project-slug} |
Project identifier from projects.md |
Prompts
Architect: Debrief Interview
role: architect
phase: mission-debrief
project: {project-slug}
action: debrief-interview
Review the system changes produced across all flights in this mission. Examine
the architectural evolution, pattern consistency, and structural health.
Provide structured input for the debrief:
**Architectural Assessment**:
- Did the system's architecture improve, maintain, or degrade?
- Are there structural issues that emerged across flights?
- Were design decisions consistent across the mission?
**Pattern Analysis**:
- What patterns were established? Are they good ones?
- Is there inconsistency that should be reconciled?
- Are there reusable patterns worth documenting?
**Technical Debt**:
- What debt was introduced across the mission?
- What's the priority for addressing it?
- Are there quick wins vs. long-term concerns?
**Forward-Looking**:
- What architectural considerations should the next mission account for?
- Are there scaling or performance concerns on the horizon?
- What documentation or conventions should be established?