Agent skill
smith-plan
Plan tracking protocol (portable). Progress tracking with checkboxes, iteration workflow, completion/blocker signals. Use when executing multi-step plans, tracking task progress, or working from plan files. IMPORTANT - Always update the plan file after completing tasks.
Install this agent skill to your Project
npx add-skill https://github.com/tianjianjiang/smith/tree/main/smith-plan
Metadata
Additional technical details for this skill
- tags
-
plan-mode workflow progress-tracking
- version
- 1.0.0
SKILL.md
Plan Tracking Protocol
Portable protocol for tracking plan progress across iterations. Platform-agnostic — works with any AI agent that can read/write files.
- Load if: Executing plans, tracking multi-step tasks
- Prerequisites: @smith-ctx/SKILL.md
CRITICAL: Plan Sync Protocol (Primacy Zone)
After completing ANY task, you MUST update the plan file.
This ensures the next iteration sees your progress.
- Skipping the sync step after completing work
- Leaving tasks unmarked after completion
- Modifying plan format in ways that break checkbox parsing
Progress Tracking Format
Use this format in plan files for trackable progress:
## Tasks
- [x] Task 1: Set up project structure
- [x] Task 2: Create database schema
- [ ] Task 3: Implement API endpoints <- CURRENT
- [ ] Task 4: Add authentication
- [ ] Task 5: Write tests
## Progress Log
### Iteration 1 ([TIMESTAMP])
- Completed: Task 1, Task 2
- Notes: Used PostgreSQL instead of MySQL per user preference
### Iteration 2 ([TIMESTAMP])
- Working on: Task 3
- Blockers: None
Workflow Per Iteration
1. LOAD: Read plan file
-> Locate and read the plan
2. IDENTIFY: Find first uncompleted task (- [ ])
-> Skip tasks marked [x]
3. EXECUTE: Complete the current task
-> Do the actual implementation work
4. SYNC: Update plan file with progress
-> Mark task [x], add progress log entry
-> Write to SAME file path
5. CONTINUE or COMPLETE
-> If more tasks: proceed to next
-> If all done: signal completion
Plan Update Template
When updating the plan, use this pattern:
# 1. Mark task complete (change - [ ] to - [x])
# 2. Add progress log entry with timestamp
# 3. Note any blockers or changes
# 4. Save to the same file path
Completion Signal
When all tasks are done, output this exact phrase:
PLAN COMPLETE: All tasks finished successfully.
Blocker Signal
If you hit a blocker requiring human input:
BLOCKER: [description of issue requiring human decision]
Important Rules
- ALWAYS update the plan file after completing work
- NEVER skip the sync step - next iteration depends on it
- Use checkbox format
- [ ]/- [x]for trackable tasks - Add timestamps to progress log entries
- Note file changes in progress log for traceability
- @smith-ctx/SKILL.md - Context management
@smith-plan-claude/SKILL.md- Claude Code automation (hooks, scripts)@smith-ralph/SKILL.md- Ralph Loop iterative development
ACTION (Recency Zone)
Per iteration:
- Read plan file
- Find first
- [ ]task - Execute the task
- Mark
- [x], add progress log entry - Continue or signal completion
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
tianjianjiang/smith
smith-style
File naming, path standards, and conventional commits. Use when naming files, creating branches, writing commit messages, or setting up new projects. Covers underscore vs hyphen conventions, commit format, and branch naming patterns.
tianjianjiang/smith
smith-stacks
Stacked pull request workflows for large features. Use when creating stacked PRs, managing dependent PRs, or rebasing after parent merges. Covers stack creation, merge order, and squash merge handling.
tianjianjiang/smith
smith-python
Python development with uv, pytest, ruff, and type hints. Use when writing Python code, running tests, managing Python packages, or working with virtual environments. Covers import organization, type hints, pytest patterns, and environment variables.
tianjianjiang/smith
smith-principles
Fundamental coding principles (DRY, KISS, YAGNI, SOLID, HHH). Use when starting any development task, evaluating implementation approaches, or reviewing code quality. Always active as foundation for all development decisions.
tianjianjiang/smith
smith-nuxt
Nuxt 3 development patterns including auto-import stubbing for tests, environment variable conventions, and middleware testing. Use when working with Nuxt projects, testing Nuxt components/middleware, or configuring Nuxt environment variables.
tianjianjiang/smith
smith-analysis
Reasoning frameworks and problem decomposition techniques. Use when planning implementation, evaluating arguments, estimating scope, decomposing complex tasks, or applying first principles thinking.
Didn't find tool you were looking for?