/project-health
Scan active projects for status, blockers and next actions. Use when the user says 'how are my projects', 'what's stuck', 'project status'. Also use proactively when projects have gone quiet. Not for writing a spec for a new product idea; use `product-brief`.
$ npx -y skills add davekilleen/Dex --skill project-health --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition โ
- You can call itInvoke it directly when you want it.
- Slash command
/project-health
Context preview
The summary Claude sees to decide when to auto-load this skill.
Scan active projects for status, blockers and next actions. Use when the user says 'how are my projects', 'what's stuck', 'project status'. Also use proactively when projects have gone quiet. Not for writing a spec for a new product idea; use `product-brief`.
SKILL.md
project-health.SKILL.mdname: project-health
description: "Scan active projects for status, blockers and next actions. Use when the user says 'how are my projects', 'what's stuck', 'project status'. Also use proactively when projects have gone quiet. Not for writing a spec for a new product idea; use `product-brief`."
Quick scan of all active projects to see what's stalled, blocked, or needs attention.
What This Does
Checks each project in `04-Projects/` for: 1. Activity levels (when was project last touched?) 2. Week Priorities presence (does project have active tasks?) 3. Blockers (anything blocking progress?) 4. Next steps clarity (is the next action clear?)
Process
Step 1: Scan Projects
List all projects in `04-Projects/`:
ls -la 04-Projects/
Step 2: Check Each Project
For each project folder or file:
**Activity Check:**
- Get last modification time
- >7 days without activity = yellow
- >14 days without activity = red
**Week Priorities Presence:**
- Scan `00-Inbox/Weekly_Plans.md` for project mentions
- No tasks for 2+ weeks = yellow
**Blocker Check:**
- Look for "blocked", "waiting on", "stuck" in project notes
- Any logged blocker = red
**Next Step Clarity:**
- Check if there's a clear next action
- No next step = yellow
Step 3: Output Dashboard
### Project Health Dashboard
| Project | Status | Issue | Days Since Activity |
|---------|--------|-------|---------------------|
| [Project A] | ๐ข | On track | 2 |
| [Project B] | ๐ก | No active tasks | 8 |
| [Project C] | ๐ด | Blocked - waiting on [X] | 15 |
**Summary:** [N] projects ([X] ๐ข / [Y] ๐ก / [Z] ๐ด)
Status Meanings
- ๐ข **Green**: Active, clear next steps, no blockers
- ๐ก **Yellow**: Stale 7-14 days, OR no active tasks, OR unclear next step
- ๐ด **Red**: Blocked, OR stale 14+ days
When to Use
- Weekly planning to check project health
- When feeling disconnected from the big picture
- Before 1:1s to surface blocked projects
- When deciding what to work on next
Follow-up Actions
For yellow projects:
- Add a task to Week Priorities
- Clarify next step in project notes
For red projects:
- Identify what's blocking progress
- Escalate if needed
- Or decide to pause/archive the project
---
Track Usage (Silent)
Update `System/usage_log.md` to mark project health check as used.
**Analytics (Silent):**
Call `track_event` with event_name `project_health_checked` and properties:
- projects_reviewed
- blockers_found
This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".
Read more
name: project-health description: "Scan active projects for status, blockers and next actions. Use when the user says 'how are my projects', 'what's stuck', 'project status'. Also use proactively when projects have gone quiet. Not for writing a spec for a new product idea; use `product-brief`."
Quick scan of all active projects to see what's stalled, blocked, or needs attention.
What This Does
Checks each project in `04-Projects/` for: 1. Activity levels (when was project last touched?) 2. Week Priorities presence (does project have active tasks?) 3. Blockers (anything blocking progress?) 4. Next steps clarity (is the next action clear?)
Process
Step 1: Scan Projects
List all projects in `04-Projects/`:
ls -la 04-Projects/
Step 2: Check Each Project
For each project folder or file:
**Activity Check:**
- Get last modification time
- >7 days without activity = yellow
- >14 days without activity = red
**Week Priorities Presence:**
- Scan `00-Inbox/Weekly_Plans.md` for project mentions
- No tasks for 2+ weeks = yellow
**Blocker Check:**
- Look for "blocked", "waiting on", "stuck" in project notes
- Any logged blocker = red
**Next Step Clarity:**
- Check if there's a clear next action
- No next step = yellow
Step 3: Output Dashboard
### Project Health Dashboard | Project | Status | Issue | Days Since Activity | |---------|--------|-------|---------------------| | [Project A] | ๐ข | On track | 2 | | [Project B] | ๐ก | No active tasks | 8 | | [Project C] | ๐ด | Blocked - waiting on [X] | 15 | **Summary:** [N] projects ([X] ๐ข / [Y] ๐ก / [Z] ๐ด)
Status Meanings
- ๐ข **Green**: Active, clear next steps, no blockers
- ๐ก **Yellow**: Stale 7-14 days, OR no active tasks, OR unclear next step
- ๐ด **Red**: Blocked, OR stale 14+ days
When to Use
- Weekly planning to check project health
- When feeling disconnected from the big picture
- Before 1:1s to surface blocked projects
- When deciding what to work on next
Follow-up Actions
For yellow projects:
- Add a task to Week Priorities
- Clarify next step in project notes
For red projects:
- Identify what's blocking progress
- Escalate if needed
- Or decide to pause/archive the project
---
Track Usage (Silent)
Update `System/usage_log.md` to mark project health check as used.
**Analytics (Silent):**
Call `track_event` with event_name `project_health_checked` and properties:
- projects_reviewed
- blockers_found
This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".
A personal operating system powered by Claude. Strategic work management, meeting intelligence, relationship tracking, daily planning โ all configured for your specific role. No coding required.
Repo: davekilleen/Dex
Other skills on davekilleen-dex.
- /agent-browser
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click
Open skill - /agent-native-architecture
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
Open skill - /andrew-kane-gem-writer
This skill should be used when writing Ruby gems following Andrew Kane's proven patterns and philosophy. It applies when creating new Ruby gems, refactoring existing gems, designing gem APIs, or when clean, minimal, production-ready Ruby library code is needed. Triggers on
Open skill - /brainstorming
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore
Open skill - /compound-docs
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Open skill - /create-agent-skills
Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
Open skill

