bridge
Capture cross-project connections on the fly. Use when you notice a link between two projects — a shared pattern, a people-bridge, a narrative that feeds another project. Persists to thinking/bridges/ as structured YAML. Use when user says "bridge", "this connects to", "this feeds into", "same pattern as", or explicitly names a cross-project link.
digital-stoic-org · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add digital-stoic-org/agent-skills --skill bridgeAbout this skill
name: bridge description: > Capture cross-project connections on the fly. Use when you notice a link between two projects — a shared pattern, a people-bridge, a narrative that feeds another project. Persists to thinking/bridges/ as structured YAML. Use when user says "bridge", "this connects to", "this feeds into", "same pattern as", or explicitly names a cross-project link. allowed-tools: [Bash, Read, Write, Edit, Glob] model: haiku argument-hint: " → : " context: main user-invocable: true
Bridge — Cross-Project Connection Capture
Capture cross-project bridges in the moment, while you're in context. Bridges are knowledge — they live in thinking/bridges/, not in project artifacts.
Why
Bridges are discovered during work, not during planning. When you're deep in a meeting and realize "this pattern connects to another project" — that's when /bridge captures it.
Step 0: Load Config
Read $PRAXIS_DIR/config/projects.yaml. This file contains:
- Project aliases (keys), names, roles, tiers, goals, flywheel roles
- Stakeholders with
also_incross-references (for people-bridge detection) - GTD and praxis paths
Use project YAML keys as aliases (case-insensitive matching). If a user types a project name instead of alias, fuzzy-match against name fields.
If config missing → ⚠️ No project config found at $PRAXIS_DIR/config/projects.yaml. Create it with your project definitions.
Archetypes
Every bridge has a type. The 10 archetypes:
| Code | Archetype | One-liner |
|---|---|---|
flywheel | 🔄 Flywheel loop | Output of A feeds B feeds C → back to A |
knowledge | 🧠 Knowledge cascade | Framework/learning from one domain reusable in another |
people | 👤 People-bridge | Same person carries context across projects |
terrain | 🌱 Terrain d'essai | One project is live lab for methods used in another |
narrative | 📖 Narrative amplifier | One project generates stories that make another credible |
identity | 🎭 Identity coherence | Projects collectively tell a story about who you are |
complexity | 🔬 Complexity lab | Managing complexity in one domain trains patterns for another |
local | 🤝 Local network overlay | Geographic proximity creates compound serendipity |
option | ⚡ Option value | One project creates future optionality for another |
mirror | 🪞 Mirror project | Introspective insights reshape how other projects are framed |
Commands
| Command | Action |
|---|---|
/bridge <src> → <tgt>: <desc> | Capture a bridge (auto-detect archetype) |
/bridge <src> → <tgt> [type]: <desc> | Capture with explicit archetype |
/bridge list | Show recent bridges (last 10) |
/bridge list <project> | Show bridges involving a project |
/bridge map | Generate mermaid bridge map from all captures |
/bridge stats | Weekly summary — counts by project and archetype |
Storage
Directory: $PRAXIS_DIR/thinking/bridges/
Each bridge is a YAML file: {date}-{seq}-{source}-to-{target}.yaml
Example: 2026-04-08-1-hp-to-brand.yaml
Sequence: Within a day, increment seq (1, 2, 3...). Check existing files for the day to determine next seq.
Schema
source: HP
target: BR
archetype: narrative
emoji: 📖
description: "Philosopher council on construct AI → reframes human-centric positioning from marketing to philosophy"
direction: one-way # one-way | bidirectional
strength: potential # active | potential | theoretical
context: "During introspect session, realized philosopher encounters are unique differentiator"
date: 2026-04-08
Fields:
source,target: Project alias (uppercase, from config keys)archetype: One of the 10 codesemoji: Archetype emojidescription: The bridge itself — what flows from source to targetdirection:one-way(A→B only) orbidirectional(A↔B, create one file with note)strength:active(happening now),potential(could happen, not activated),theoretical(speculative)context: Optional — what triggered the discovery (session, meeting, realization)date: ISO date
Capture (/bridge <args>)
Parse Arguments
Input: /bridge HP → BR: philosopher encounters reframe human-centric positioning
- Split on
→to get source and rest - Split rest on
:to get target (+ optional[type]) and description - Resolve aliases against config keys (case-insensitive). If no match, fuzzy-match against
namefields. - If
[type]present, use it; otherwise auto-detect archetype
Auto-Detect Archetype
If no explicit type, use two signals:
Signal 1 — Keywords in description:
- "pattern", "framework", "method", "learned", "reusable" →
knowledge - Person name (check config stakeholders) or "carries context", "cross-pollinates" →
people - "story", "credibility", "proof", "case study" →
narrative - "test ground", "lab", "experiment", "tried in" →
terrain - "loop", "feeds back", "cycle" →
flywheel - "brand", "who I am", "positioning", "identity" →
identity - "admin", "bureaucracy", "same skill", "transfers" →
complexity - "local", "geographic" →
local - "future", "optionality", "if it works", "unlocks" →
option - "introspect", "philosopher", "reframe", "reshape" →
mirror
Signal 2 — Config context:
- If source or target has
flywheel_role: terrain→ lean towardterrain - If source or target has
flywheel_role: mirror→ lean towardmirror - If a stakeholder name appears in description and has
also_in→people
If ambiguous, default to knowledge and mention in response.
Detect Direction & Strength
- Default:
one-way,potential - If description contains "↔" or "bidirectional" or "both ways" →
bidirectional - If description contains "already", "happening", "active", "doing this" →
active - If description contains "could", "should", "would", "not yet" →
potential - If description contains "maybe", "speculative", "in theory" →
theoretical