القائمة
Scan the system with fresh eyes. Surface what's alive, what's connecting, what's trying to emerge. Route insights where they belong.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build topic reserves by searching your entire system, or run discovery mode to find what connects across territories. Use when consolidating scattered knowledge on a topic, before writing/sharing, or when curiosity has no specific target.
End work session intentionally. Use at natural stopping points, before context limits, or when switching contexts.
Pick up a workstream across sessions. Load context, find texture, align, then go. Use when jumping back into something that has history.
Refresh the current session's LOG with a fresh extraction. Use as the last step of /wrap, or any time the session has continued and you want the capture current. Idempotent — safe to invoke multiple times.
Create a living task doc from natural language. Use when you want to track work, capture a new project, or create a thinking log that accumulates context across sessions.
Open the floor for your AI's curiosity. Use when wrapping or at natural pauses.
| name | heartbeat |
| description | Scan the system with fresh eyes. Surface what's alive, what's connecting, what's trying to emerge. Route insights where they belong. |
Every new instance is a heartbeat. Use it.
The system accumulates faster than either of you can track. Sessions generate ideas, sparks pile up, tasks sit, goals drift, threads go quiet. No single session sees the full picture because each session is focused on what's in front of it.
The heartbeat steps back. It's a reflective scan across the whole system — not to generate a status report, but to notice what's forming, what's stale, and what's trying to emerge that doesn't have a name yet.
It also solves the memory curation gap: the system captures richly (sessions are verbatim) but doesn't distill. The heartbeat is where distillation happens — patterns get crystallized and routed to where they'll be found.
Skip it when deep in flow on a specific task. Don't interrupt momentum for reflection.
This is a conversation, not a report. That framing shapes everything — the scan, the reflection, the sharing. You're thinking together about what you see, not delivering findings. Lead with what's most interesting or surprising. "I noticed X keeps showing up and it might connect to Y" beats "here's a list of active threads" every time.
Read across the system with priority order. Start with orientation (where are we?), then widen to the full landscape. Not everything every time — use judgment.
Orient first:
Then widen:
Adapt the scan to your system. The categories matter more than specific file names — wherever your goals, tasks, captures, and reflections live, that's where you look.
Fresh eyes are the point. You're arriving without habituation. The things that look obvious to you might be invisible to someone who's been in it daily. That asymmetry is the skill's core value — lean into it.
Don't just list what you found. Think across it. Each layer builds on the previous one.
Pulse — What's active right now? What's new since last heartbeat? What's gone quiet?
Patterns — What connections are forming across sessions? What themes keep recurring? Where is the energy concentrated vs scattered?
Vital signs — Are we moving toward goals? What keeps getting deferred and why? What's conspicuously absent — things we said we'd do that haven't come up in weeks?
Emergence — What's trying to form that doesn't have a container yet? A spark that's shown up in 3 sessions might be ready to become something. A thread that keeps surfacing across different contexts might be an unnamed principle.
Whatever landed, put it where it'll be found:
| What surfaced | Where it goes |
|---|---|
| New spark or connection | Sparks file, idea log, or backlog |
| Methodology / how you work together | System docs, partnership notes |
| Convention or standard | Rules, guidelines, wherever standards live |
| Topic or domain insight | Knowledge base, reference docs, library |
| Something about the human | Their identity doc or personal notes |
| Something for the AI specifically | AI reflection space |
| Work pattern for a specific project | That project's docs |
| Direction drift or realization | Goals doc or backlog |
| Actionable work | Task doc or backlog |
| Nothing to route | That's fine. Not every heartbeat produces artifacts. |
Crystallized patterns don't go to one place — they go home. The heartbeat's job is to recognize what kind of insight it is and route accordingly.
The session capture preserves the full heartbeat conversation. No separate log needed.
Quick scan: anything about this heartbeat that felt off or could be smoother?
If yes → update this skill now. The improvement compounds.
If no → move on. Not every heartbeat teaches something about the heartbeat itself.
