progress-tracker

Show progress-tracker command help

Complete current feature via deterministic acceptance gatekeeping

Report, list, or fix bugs with smart scheduling and systematic debugging

Initialize project progress tracking with feature breakdown

Sync project capability memory from git history with batch confirmation

Start implementing the next pending feature

Record a structured progress update (status/decision/risk/handoff/assignment/meeting)

Create architectural plan with technology selection and system design

Reset active progress tracking files with confirmation and auto-archive

Launch Progress UI web server and open browser

Undo the last completed feature and revert its code changes

Display project progress status

This skill should be used when the user runs "/prog init", asks to "initialize progress tracking", "break down a goal into features", "create a feature list with test steps", or needs to start a new tracked project.

This skill should be used when the user asks to "/prog done", "complete feature", "mark feature as done", "finish implementation", or runs the prog-done command. Handles feature verification, progress tracking updates, and Git commits.

This skill should be used when feature complexity is complex (score 26-40) and the coordinator delegates architecture-heavy or multi-file implementation. Executes brainstorming, planning, and subagent-driven execution with opus and updates workflow and AI metrics.

This skill should be used when feature complexity is simple (score 0-15) and the coordinator delegates low-risk tasks such as single-file changes, clear requirements, and limited test steps. Executes direct TDD with haiku and updates workflow and AI metrics.

This skill should be used when the user runs "/prog plan", asks to "create architecture plan", "choose tech stack", "document architecture decisions", or needs system design guidance before implementation.

This skill should be used when the user asks to "fix a bug", "report a bug", "/prog-fix", "investigate bug", or mentions debugging workflow within progress-tracker plugin. Manages bug discovery, verification, scheduling, and TDD-based fixing.

This skill should be used when the user runs "/prog next", asks to "implement next feature", "start next feature", "continue implementation", or needs to resume interrupted feature execution. Routes features to appropriate implementation paths based on complexity assessment.

This skill should be used when the user asks to "create a git commit", "commit changes", "commit and push", "make a commit", "handle git", "git auto", "git auto start", "git auto done", or "git auto fix", or needs git operations automated with branch/PR/merge decisions.

This skill should be used when the user asks to "/prog log", "sync project memory", "sync capabilities", or requests incremental capability backfill from git history.

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.

This skill should be used when the user runs "/prog reset", "/prog undo", asks to "reset progress tracking", "revert last completed feature", or needs safe administrative rollback operations.

This skill should be used when the user runs "/prog", asks to "resume progress", "recover interrupted workflow", "continue unfinished feature", or returns after an interrupted development session.

This skill should be used when the user runs "/prog", asks to "show project status", "show progress", "how many features are done", or requests a completion summary. Reads progress tracking files, computes completion metrics, displays current feature state, and provides actionable next-step recommendations.

This skill should be used when the user asks to "generate test documentation", "create acceptance report", "write bug fix report", "document testing results", "create test guide", or "standardize test documents". Defines naming conventions, frontmatter standards, and content structure for all testing documents in docs/progress-tracker/testing/. Automatically referenced by feature-complete and bug-fix skills.

This skill should be used when the user runs "/prog-ui", asks to "open progress UI", "launch progress web UI", or wants to view progress in a browser. Manages the Progress UI server lifecycle (detect, start, open browser) for the current project.

6 hooks across 3 events