Works with

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add mag123c/toktrack --skill next --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Next?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mag123c-next/badge)](https://www.skillsdirectory.com/skills/mag123c-next)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: next
description: Session start - check progress, suggest next task
required_context:
  - .claude/ai-context/architecture.md
---

# Next

## Flow
```
Read Planning → Git Log → Analyze → Present → Suggest /clarify
```

## Execution

1. **Read Planning**
   ```bash
   # Read ONLY the latest planning file (by date prefix YYYYMMDD-)
   # e.g., 20260205-improvements.md > 20260128-cli-parsers.md
   # Check checkbox status: [ ] incomplete, [x] complete
   ```

2. **Git Log**
   ```bash
   git log --oneline -5
   git status --short
   ```

3. **Analyze**
   - Identify current phase
   - Count completed/total tasks
   - Identify next priority task

4. **Present** (table format)
   | Phase | Status | Progress |
   |-------|--------|----------|
   | Phase 0 | ✅ | 5/5 |
   | Phase 1 | 🔄 | 3/4 |

5. **Suggest**
   - Summarize next task
   - Suggest running `/clarify`

## Output Format
```markdown
## Current Status
- Phase: {current_phase}
- Progress: {completed}/{total} tasks

## Next Task
**{task_id}: {task_name}**
{brief_description}

## Action
Run `/clarify` to start: {task_summary}
```

## Rules
- **Read only the latest dated planning file** (highest YYYYMMDD- prefix)
- If no planning files → infer from git log + code state
- Keep output concise (5-10 lines)
- Always suggest /clarify connection