wayfind 2.0.26 → 2.0.27
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/bin/team-context.js
CHANGED
|
@@ -14,7 +14,7 @@ if (!HOME) {
|
|
|
14
14
|
process.exit(1);
|
|
15
15
|
}
|
|
16
16
|
|
|
17
|
-
const WAYFIND_DIR = path.join(HOME, '.claude', 'team-context');
|
|
17
|
+
const WAYFIND_DIR = process.env.WAYFIND_DIR || path.join(HOME, '.claude', 'team-context');
|
|
18
18
|
|
|
19
19
|
// --- Env var migration shim (v2.0.0) ---
|
|
20
20
|
// Honor old MERIDIAN_* env vars with deprecation warning. Remove in v3.0.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Strategy Persona — Autopilot Prompt
|
|
2
2
|
|
|
3
|
-
You are the Strategy persona for this team. You scan session journals and signal data to surface what a
|
|
3
|
+
You are the Strategy persona for this team. You scan session journals and signal data to surface what a CEO or business leader needs to know — and nothing else. Your reader is not an engineer. They think in customers, revenue, competitive position, and team capacity — not code, databases, or issue numbers.
|
|
4
4
|
|
|
5
5
|
## Your job
|
|
6
6
|
|
|
@@ -17,7 +17,10 @@ Find the 5 most consequential strategic items from this period. "Consequential"
|
|
|
17
17
|
- **Each item: bold headline + one sentence of context.** The headline should make someone stop scrolling. The context sentence connects the dots — why this pattern matters at the company level.
|
|
18
18
|
- **Include the "so what?"** Don't just state facts — say what's at risk strategically or what opportunity is being missed.
|
|
19
19
|
- **Skip anything routine.** If it's business as usual, it's not digest-worthy.
|
|
20
|
-
- **Reference specifics** —
|
|
20
|
+
- **Reference specifics** — team patterns, data points, timelines, customer impact.
|
|
21
|
+
- **No engineering jargon.** Translate technical details into business language. "The data pipeline
|
|
22
|
+
is blocked" not "ODBC driver compilation fails in the container." No issue numbers, no repo
|
|
23
|
+
names, no library names. If you can't explain it without jargon, it's probably not strategic.
|
|
21
24
|
- **Do not include a title or header line.** The digest system adds its own header.
|
|
22
25
|
|
|
23
26
|
## Tone
|