scripts-plan

Summary

Shell scripts that track plan progress for Markdown plan files with - [ ] / - [x] task checkboxes — used directly by developers and automatically by /implement — in NEXT mode and on every ALL-mode iteration.

When to use

Use these scripts whenever you are working with Markdown plan files that contain - [ ] / - [x] task checkboxes:

• To see which task is next and the current completion percentage — use plan-progress.sh.

Invocation

plan-progress.sh

Prints a formatted progress header for the next uncompleted task. Uses progress-header-phased.template (phased plans) or progress-header-flat.template (flat plans).

Bundled inside the /implement skill at skills/implement/scripts/plan-progress.sh; normally invoked by /implement, not run by hand.

bash skills/implement/scripts/plan-progress.sh <plan_file>

Exit codes: 0 = header printed + NEXT_TASK_* machine-readable lines; 1 = all tasks complete; 2 = usage error or file not found; 3 = no recognized task section heading.

Internal dependencies (called by plan-progress.sh — not invoked directly)

• task_section.awk — AWK fragment that activates when the parser enters a recognized task section heading (## Tasks, ## Task, or ## Task breakdown).
• progress-header-phased.template — Mustache-style template for phased plans (plans with ### phase headings).
• progress-header-flat.template — Mustache-style template for flat plans (no phase headings).

Dependency table

Example 1 — Check plan progress with plan-progress.sh

bash skills/implement/scripts/plan-progress.sh plans/FEAT-001-skill-command-script-handouts.md

Progress   : [█████████░░░] 79%  (15/19 tasks, 3/6 phases)
Next task  : 4.1  **File**: `handout/scripts-plan.html`

NEXT_TASK_NAME=**File**: `handout/scripts-plan.html`
NEXT_TASK_PHASE=4
NEXT_TASK_NUMBER=1

Related tools

• /implement — Calls plan-progress.sh in NEXT-mode Step 1 and at the start of every ALL-mode iteration.