Pair the capability scouts: rename to scout-capability, add scout-displacement #154

Closed
opened 2026-06-04 07:39:09 +00:00 by coilysiren · 0 comments
Owner

Make the two capability scouts legibly a pair.

tooling-capability-scout finds capability to ADD (external catalog in).
There is no outbound counterpart that finds custom code to SHED (your own
subsystems in, matched to off-the-shelf OSS). They are one portfolio task
run in opposite directions and should read as a set.

Plan:

  • Rename tooling-capability-scout -> tooling-scout-capability so both
    sort adjacent under a tooling-scout-* family stem.
  • Add tooling-scout-displacement (build-vs-buy / NIH audit) with a
    stateful verdict ledger so the recurring sweep diffs instead of redoing.
  • Cross-link both ways with a ## Paired with section and mirrored intros.
Make the two capability scouts legibly a pair. `tooling-capability-scout` finds capability to ADD (external catalog in). There is no outbound counterpart that finds custom code to SHED (your own subsystems in, matched to off-the-shelf OSS). They are one portfolio task run in opposite directions and should read as a set. **Plan:** - Rename `tooling-capability-scout` -> `tooling-scout-capability` so both sort adjacent under a `tooling-scout-*` family stem. - Add `tooling-scout-displacement` (build-vs-buy / NIH audit) with a stateful verdict ledger so the recurring sweep diffs instead of redoing. - Cross-link both ways with a `## Paired with` section and mirrored intros.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os#154
No description provided.