session-status
Tracks session progress and efficiency using breadcrumbs and takt time metrics.
Install
mkdir -p .claude/skills/session-status && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5691" && unzip -o skill.zip -d .claude/skills/session-status && rm skill.zipInstalls to .claude/skills/session-status
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Generate breadcrumb headers/footers with takt time tracking and muda metricsKey capabilities
- →Collect current session state data including feature name and phase
- →Calculate takt time by comparing duration against predefined targets
- →Format a single-line breadcrumb header with status, feature, and progress
- →Generate a context-specific footer with dynamic action prompts
- →Track silent metrics like loop count, waiting time, and rework
- →Integrate with Ask, Agent, and Plan modes for automatic invocation
How it works
This skill generates persistent status headers and footers by gathering session state, calculating takt time against targets, and formatting the information.
Inputs & outputs
When to use session-status
- →Track session duration during active coding
- →Visualize phase progress in long tasks
- →Monitor workflow efficiency
- →Standardize session status reporting
About this skill
Session Status Skill
Generate consistent navigation breadcrumbs showing current position, takt time, and session metrics.
When to Use
- At START of every Ask/Agent/Plan mode response
- At END of every Ask/Agent/Plan mode response
- When session metrics are needed for Session Journal sync
Phase 1: Gather State
Collect current session state:
| Data | Source |
|---|---|
| Feature name | From init context or branch name |
| Current phase | DIVERGE / CONVERGE / DEFINE / AGENT |
| Loop count | Incremented on each user feedback cycle |
| Progress | Validated items / total items |
| Duration | Time since phase started |
| Status | G (flow) / Y (waiting) / R (stopped) |
Phase 2: Calculate Takt
Compare duration against targets from 03-shared.mdc:
| Phase | Target | Warning | Stop |
|---|---|---|---|
| DIVERGE (per loop) | 15min | 30min | 60min |
| CONVERGE | 20min | 40min | 90min |
| DEFINE | 10min | 20min | 45min |
| Commit (each) | 10min | 20min | 30min |
Determine suffix:
- Under target: (none)
- Warning exceeded:
! - Stop exceeded:
!!
Phase 3: Format Header
Generate single-line breadcrumb:
Format: [STATUS] | [Feature] | [PHASE_PROGRESS] | L[N] | [X]/[Y] | [TIME]
Examples by phase:
- DIVERGE:
G | Collaboration | DIVERGE ###....... | L3 | 5/9 | 18m - CONVERGE:
G | Collaboration | DIVERGE OK | CONVERGE ##.... | L1 | 22m - DEFINE:
G | Collaboration | DIVERGE OK | CONVERGE OK | DEFINE ###.. | L2 | 35m - AGENT:
G | Collaboration | AGENT | C2/5 | 45m - Warning:
Y | Collaboration | DIVERGE ###....... | L3 | 5/9 | 32m! - Stopped:
R | Collaboration | AGENT | JIDOKA STOP
Progress bar: 10 chars, # filled, . empty, proportional to completion.
Phase 4: Format Footer
Generate context-specific footer:
---
Next: [action prompt]
Dynamic prompts by context:
| Context | Footer Prompt |
|---|---|
| DIVERGE with DIG | Provide OK/KO/DIG for: #4, #6, #7 |
| Gate 1 passed | All validated. Say "converge" to proceed. |
| Gate 2 | Choose option: A / B / C |
| Gate 3 | Approve phasing: OK / REORDER / SPLIT |
| AGENT | Commit 2/5 in progress... |
| Jidoka stop | Reply with A, B, C, or D |
| Autonomous | Iteration 3/5... |
Phase 5: Track Muda (Silent)
Update session metrics in memory:
| Metric | Tracking Rule |
|---|---|
| Loop count | Increment on user feedback |
| Waiting time | Time between user responses |
| Rework | Items DIG'd 3+ times |
| RED count | qa-commit failures |
| Escalations | Jidoka Tier 2/3 events |
Output Format
## Session Status
**Header:** [formatted header string]
**Footer:** [formatted footer string]
### Metrics (Silent)
- Duration: [N]min
- Loops: [N]
- Rework: [N]
- Waiting: [N]min
- RED count: [N]
Header/Footer Examples
Ask Mode - DIVERGE L3
Header:
G | Collaboration | DIVERGE ###....... | L3 | 5/9 | 18m
Footer:
---
Next: Provide OK/KO/DIG for: #4, #6, #7
Ask Mode - Gate 1 Passed
Header:
G | Collaboration | DIVERGE OK | CONVERGE #......... | L1 | 22m
Footer:
---
Next: All wireframes validated. Say "converge" to proceed.
Agent Mode - Commit in Progress
Header:
G | Collaboration | AGENT | C2/5 | 45m
Footer:
---
Next: Implementing Commit 2: Add workspace membership entity...
Jidoka Stop
Header:
R | Collaboration | AGENT | JIDOKA STOP
Footer:
---
Next: Reply with A (different approach), B (skip), C (pause), or D (abort)
Integration
This skill is invoked by:
ask.mdc- At start and end of every responseagent.mdc- At start and end of every responseplan.mdc- At start and end of every responsepush-pr.mdc- Collects final metrics for session-journal sync
Invocation
Auto-invoked by modes. Manual trigger: "show session status"
Tools Used
| Tool | Purpose |
|---|---|
| (none) | Pure calculation, no external tools |
How it compares
This skill provides real-time, standardized session status with takt time and dynamic prompts, offering more structured and actionable feedback than manual status updates.
Compared to similar skills
session-status side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| session-status (this skill) | 1 | 7mo | Review | Beginner |
| it-operations | 1 | 7mo | No flags | Advanced |
| customerio-cost-tuning | 0 | 25d | Review | Intermediate |
| perplexity-incident-runbook | 0 | 25d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by WellApp-ai
View all by WellApp-ai →You might also like
it-operations
davila7
Manages IT infrastructure, monitoring, incident response, and service reliability. Provides frameworks for ITIL service management, observability strategies, automation, backup/recovery, capacity planning, and operational excellence practices.
customerio-cost-tuning
jeremylongshore
Optimize Customer.io costs and usage. Use when reducing expenses, optimizing usage, or right-sizing your Customer.io plan. Trigger with phrases like "customer.io cost", "reduce customer.io spend", "customer.io billing", "customer.io pricing".
perplexity-incident-runbook
jeremylongshore
Execute Perplexity incident response procedures with triage, mitigation, and postmortem. Use when responding to Perplexity-related outages, investigating errors, or running post-incident reviews for Perplexity integration failures. Trigger with phrases like "perplexity incident", "perplexity outage", "perplexity down", "perplexity on-call", "perplexity emergency", "perplexity broken".
plex
Akpo-Fure
>-
oly
slaveOftime
Use when starting a long-running or interactive CLI command with oly, especially when it may need later input, should be detachable, or should keep durable logs for supervision and resume.
pagerduty
fisker086
Query PagerDuty incidents, services, and on-call schedules