From progress-tracker
This skill should be used when the user asks to "/prog note", "/prog-note", "record a project update", "add status update", "log decision/risk/handoff", or needs to write structured update entries into progress tracking.
npx claudepluginhub siuninyue/siunin-plugins --plugin progress-trackerThis skill uses the workspace's default tool permissions.
Write structured updates into Progress Tracker through CLI commands only.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Write structured updates into Progress Tracker through CLI commands only.
Prefer these normalized fields:
category: one of status|decision|risk|handoff|assignment|meetingsummary: short required sentencedetails: optional long-form detailsfeature_id: optional numeric feature idbug_id: optional bug idrole: optional architecture|coding|testingowner: optional owner textsource: optional, default prog_updatenext_action: optional next steprefs: optional list of refsIf user input is unstructured, infer summary from the first sentence and set category to status by default.
plugins/progress-tracker/prog add-update to append an update.progress.json directly.role and owner are provided with feature_id, also call:
plugins/progress-tracker/prog set-feature-owner <feature_id> <role> <owner>plugins/progress-tracker/prog add-update \
--category "<category>" \
--summary "<summary>" \
--details "<details>" \
--source "prog_update"
plugins/progress-tracker/prog set-feature-owner <feature_id> <role> "<owner>"
Return concise confirmation:
category + summaryfeature_id/bug_id if any