ilandahan/AID / skills/context-tracking
context-tracking
VerifiedReal-time work context tracking for session continuity. Maintains task/step state across sessions, tracks progress, manages logs, integrates with phase enforcement.
| File | Kind | Size |
|---|---|---|
| SKILL.extended.md | markdown | 17.2 KB |
| SKILL.md | skill md | 4.0 KB |
| references/context-schema.md | markdown | 7.5 KB |
| references/session-management.md | markdown | 13.2 KB |
| references/step-templates.md | markdown | 12.1 KB |
SKILL.md
View on GitHub---
name: context-tracking
description: Real-time work context tracking for session continuity. Maintains task/step state across sessions, tracks progress, manages logs, integrates with phase enforcement.
---
# Context Tracking
Applies: every session, whenever work starts, a step/task changes, phase changes, or a conversation ends. Maintain `.aid/context.json`.
## Core Rule
1. READ context before starting work
2. UPDATE on every significant change
3. SYNC with phase state (`.aid/state.json`)
4. INTEGRATE with feedback (`/aid end`)
5. SAVE at conversation end
## Update Triggers
| Moment | Action |
|---|---|
| Session start | Read context |
| New task | Update current_task, reset current_step and progress |
| New step | Update current_step, add session note |
| Step complete | Move step to steps_completed, update current_step |
| Task complete | Clear current_task, prompt feedback |
| Phase change | Sync with state.json |
| End conversation | Final save with timestamp |
## Context Structure
```json
{
"$schema": "aid-context-v1",
"version": "1.0",
"last_updated": "ISO-8601",
"current_task": {
"key": "TASK-ID",
"title": "Task title",
"description": "What needs to be done",
"phase": 4,
"phase_note": "Additional phase context"
},
"current_step": {
"name": "Current step description",
"progress": 0,
"notes": "Step-specific notes"
},
"progress": {
"steps_completed": ["Step 1", "Step 2"],
"steps_pending": ["Step 3", "Step 4"]
},
"session_notes": [
{
"timestamp": "ISO-8601",
"note": "What happened"
}
],
"blockers": [
{
"id": "BLOCKER-001",
"description": "What's blocking",
"severity": "high|medium|low",
"resolution": "How to resolve"
}
]
}
```
Field detail: `references/context-schema.md`.
## Phase-Aware Context
| Phase | Task Types | Step Templates |
|---|---|---|
| 1 PRD | Requirements | User stories, acceptance |
| 2 Tech Spec | Architecture | Design, API, security |
| 3 Impl Plan | Planning | Task breakdown |
| 4 Development | Coding | TDD cycle, impl |
| 5 QA | QA | Testing, deploy |
## Standard Step Templates
More templates: `references/step-templates.md`.
Component Development (Phase 4)
1. Load task context
2. Read Tech Spec
3. Write tests (TDD)
4. Implement
5. Run tests
6. Self review
7. Commit
Bug Fix (Phase 4)
1. Load context
2. Reproduce issue
3. Write failing test
4. Implement fix
5. Verify
6. Commit
## Session Notes
Append to `session_notes` at these moments:
| When | Note Content |
|---|---|
| Session start | "Session started - resuming [task title]" |
| Task started | "Started task: [key] - [title]" |
| Task completed | "Completed task: [key]" |
| Step completed | "Completed step: [step name]" |
| Progress milestone | "Progress: [description of milestone]" |
| Phase changed | "Phase transition: [old] -> [new]" |
| Blocker added/resolved | "Blocker [added/resolved]: [description]" |
## Blocker Management
Track blockers in the `blockers` array (fields: `id`, `description`, `severity` = `high|medium|low`, `resolution`; ids like `BLOCKER-001`). Remove a blocker from the array when resolved and add a session note documenting the resolution.
## Error Handling
No context.json:
```
No .aid/context.json found
Creating context:
1. What feature?
2. What phase?
3. What task?
```
Stale context (>24h):
```
Context stale (36h old)
Last: PROJ-124 "AuthService" (60%)
Still accurate?
[1] Yes, continue
[2] No, completed offline
[3] Start fresh
```
Context-State mismatch:
```
Context: Phase 3
State: Phase 4
Syncing to Phase 4...
```
## File Locations
```
.aid/
state.json # Phase state
context.json # Task/step context
~/.aid/
feedback/pending/
feedback/processed/
```
Session lifecycle detail: `references/session-management.md`.
## Commands
| Command | Purpose |
|---|---|
| /context | Show current |
| /context tasks | Task progression |
| /context steps | Current steps |
| /context log | Session log |
| /context update | Manual update |
| /good-morning | Full startup |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |