Keep ADR for historical overview? #370

Activity

1. bradygaster

   added

   squadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a member

   squad:mcmanus

   squad:keaton

   priority:p2Next sprintNext sprint

   type:featureNew capabilityNew capability

   on Mar 13, 2026
2. github-actions

   added

   squad:flight

   go:needs-researchNeeds investigationNeeds investigation

   on Mar 13, 2026
3. github-actions commented on Mar 13, 2026

   

   github-actionsBot

   on Mar 13, 2026 – with GitHub Actions

   Contributor

   More actions

   🏗️ Squad Triage — Flight (Lead)

   Issue: #370 — Keep ADR for historical overview?
   Assigned to: Flight (Lead)
   Reason: No specific domain match — assigned to Lead for further analysis

   @copilot evaluation: No strong capability match — routed to squad member.

   Team roster:

   • Flight (Lead) → label: squad:flight
   • Procedures (Prompt Engineer) → label: squad:procedures
   • EECOM (Core Dev) → label: squad:eecom
   • FIDO (Quality Owner) → label: squad:fido
   • PAO (DevRel) → label: squad:pao
   • CAPCOM (SDK Expert) → label: squad:capcom
   • CONTROL (TypeScript Engineer) → label: squad:control
   • Surgeon (Release Manager) → label: squad:surgeon
   • Booster (CI/CD Engineer) → label: squad:booster
   • GNC (Node.js Runtime) → label: squad:gnc
   • Network (Distribution) → label: squad:network
   • RETRO (Security) → label: squad:retro
   • INCO (CLI UX & Visual Design) → label: squad:inco
   • GUIDO (VS Code Extension) → label: squad:guido
   • Telemetry (Aspire & Observability) → label: squad:telemetry
   • VOX (REPL & Interactive Shell) → label: squad:vox
   • DSKY (TUI Engineer) → label: squad:dsky
   • Sims (E2E Test Engineer) → label: squad:sims
   • Handbook (SDK Usability) → label: squad:handbook
   • Ralph (Work Monitor) → label: squad:ralph
   • @copilot (Coding Agent) → label: squad:copilot

   To reassign, remove the current squad:* label and add the correct one.
4. bradygaster

   removed

   squad:flight

   on Mar 13, 2026
5. bradygaster commented on Mar 13, 2026

   

   bradygaster

   on Mar 13, 2026

   Collaborator

   More actions

   📌 Brady requested this issue be assigned to @diberry (docs/UX triage). Pending collaborator invite to complete assignment.
6. bradygaster

   added

   squad:flight

   squad:pao

   and removed

   squad:keaton

   squad:mcmanus

   on Mar 13, 2026
7. github-actions commented on Mar 13, 2026

   

   github-actionsBot

   on Mar 13, 2026 – with GitHub Actions

   Contributor

   More actions

   📋 Assigned to Flight (Lead)

   Issue: #370 — Keep ADR for historical overview?

   Flight will pick this up in the next Copilot session.

   For Copilot coding agent: If enabled, this issue will be worked automatically.
   Otherwise, start a Copilot session and say:
   Flight, work on issue #370
8. github-actions commented on Mar 13, 2026

   

   github-actionsBot

   on Mar 13, 2026 – with GitHub Actions

   Contributor

   More actions

   📋 Assigned to PAO (DevRel)

   Issue: #370 — Keep ADR for historical overview?

   PAO will pick this up in the next Copilot session.

   For Copilot coding agent: If enabled, this issue will be worked automatically.
   Otherwise, start a Copilot session and say:
   PAO, work on issue #370
9. diberry commented on Mar 14, 2026

   

   diberry

   on Mar 14, 2026

   Contributor

   More actions

   PAO triage note (from @diberry):

   This is labeled \ ype:feature\ and \squad:pao, but after reviewing it, this is a product/design decision — not a docs task.

   The ask is for a new structured artifact (ADR format) that doesn't exist in Squad today. Implementing it would require changes to Scribe's behavior, new templates, and a consolidation mechanism. \decisions.md\ already captures decisions, but the reporter wants richer before/after context — that's a design choice about what Squad records.

   PAO's take: Nothing to document until the feature ships. Suggesting this stays with Flight for architectural evaluation. If it gets built, PAO will document it.

   Recommend removing \squad:pao\ and keeping \squad:flight\ as the primary owner.
10. github

    deleted a comment from github-actions on Mar 16, 2026
11. tamirdresher

    added a commit that references this issue on Mar 16, 2026

    feat: a11y fixes and test coverage (github#382)

    ...

    This issue will close once commit 0024771 is merged into the 'main' branch.

    0024771
12. github

    deleted a comment from github-actions on Mar 18, 2026
13. bradygaster commented on Mar 20, 2026

    

    bradygaster

    on Mar 20, 2026

    Collaborator

    More actions

    Great suggestion — and good news, Squad already has several mechanisms that serve this purpose:

    1. *\decisions.md* — the team's shared decision ledger. Every architectural/scope decision gets recorded here with context and rationale. This is the closest thing to ADRs.
    2. *\decisions/inbox/* — agents write decisions to individual drop files, Scribe merges them into the canonical ledger. Before/after context is preserved.
    3. *\orchestration-log/* — records who worked on what, why they were chosen, and outcomes. Great for tracing how decisions played out.
    4. *Agent \history.md* — each agent's personal knowledge base. Reusable patterns, architecture notes, key file paths.
    5. Skills (.copilot/skills/) — proven patterns extracted from work, with confidence levels.

    The combination of decisions.md (the what and why) + orchestration-log (the who and how) effectively gives you ADR-style records. If you find gaps in what's captured, let us know!

    Closing as addressed by existing mechanisms.

    👍React with 👍1Reacted by Sturla Thorvaldsson
14. bradygaster commented on Mar 20, 2026

    

    bradygaster

    on Mar 20, 2026

    Collaborator

    More actions

    Addressed by existing decisions.md, orchestration-log, and skills system.
15. bradygaster

    closed this as completedon Mar 20, 2026
16. bradygaster

    removed

    squad:flight

    squad:pao

    on Sep 11, 2026