Stats
Actions
Tags
From feature-workflow
Updates plan.md progress logs and checks off completed implementation steps. Use after finishing tasks, making feature commits, or indicating work done. Always asks before editing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/feature-workflow:tracking-progressThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Track feature implementation progress by updating plan.md when tasks are completed.
Track feature implementation progress by updating plan.md when tasks are completed.
Invoke this skill when the user:
This skill modifies files. Always ask before making changes.
Read docs/features/DASHBOARD.md and look at the In Progress section to find current features.
If multiple exist, check context or ask which one.
Read docs/features/[id]/plan.md
Locate:
From the user's statement, identify what was completed and match it to implementation steps.
Prepare:
- [ ] → - [x]Show proposed changes, get confirmation, then use Edit tool to apply.
User: "Done with the JWT token refresh logic"
Response:
Update progress in plan.md?
1. Add progress log entry:
### 2026-01-15
- Completed JWT token refresh logic in auth/tokens.ts
- Next: Implement session timeout handling
2. Mark complete:
- [x] Implement JWT token refresh logic
Proceed? (yes/no)
After confirmation:
Progress updated in plan.md:
- Added log entry for 2026-01-15
- Marked complete: Implement JWT token refresh logic
Remaining steps: 4 of 7
This skill works with:
/feature-submit - Uses plan.md checkbox state to auto-generate PR body/feature-ship - Relies on accurate progress trackingnpx claudepluginhub schuettc/claude-code-plugins --plugin feature-workflowImplements approved plans from .claude/scratchpad files by reading code fully, executing phases sequentially, verifying work, and updating checkboxes.
Tracks task completion in markdown plan files using plan-file-management subcommands. Mandates test verification of observables and evidence before marking tasks done. Activates on *-plan.md files.
Manages a 4-phase feature development pipeline: research, implementation planning, progress tracking, and phased execution for major features. Supports status checks and next-step guidance via subcommands.