List active WikiFlow plans with task progress and completion percentages.
npx skills add https://github.com/liqunx/wikiflow --skill wf-status-liqunx
Please help me install this Agent Skill. Skill: wf-status Source: https://github.com/liqunx/wikiflow/tree/main/skills/wf-status Command: npx skills add https://github.com/liqunx/wikiflow --skill wf-status-liqunx
When you’re running document-driven development, it’s hard to know which WikiFlow plans are currently active and how far each one has progressed; wf-status makes that visibility instant by summarizing progress and tasks across active plans.
.wikiflow/config.json and scans docs/changes/active/ to find valid plans containing spec.md and tasks.md.tasks.md to compute completion percentage and renders an ASCII progress bar.--active/--draft/--paused/--blocked, keyword filtering by plan name/description, and natural-language queries like “plans with progress over 50%”.Run wf-status inside the documentation repository (where .wikiflow/config.json and docs/changes/active/ exist) to list all active development plans and their progress.
High-intent search queries and answers about installing and using this skill.
To track active WikiFlow plans, read `.wikiflow/config.json` and scan `docs/changes/active/` to parse `spec.md` and `tasks.md`. This computes completion percentages and renders standardized task analytics for your documentation workflow.
Filter WikiFlow project progress using status flags like `--active`, `--draft`, `--paused`, or `--blocked`. You can also apply keyword filtering by plan name or use natural-language queries like "plans with progress over 50%" for precise task analytics.
Task progress computation works by parsing task checkboxes from `tasks.md` files in active plans. It calculates completion percentages and renders an ASCII progress bar, providing instant read-only dashboard visibility into your document-driven development workflow.
You cannot modify files when checking WikiFlow status. The tool enforces read-only safety constraints, explicitly prohibiting file modifications to ensure it functions solely as a read-only dashboard for monitoring plan health and completion rates.
Yes, you need a documentation repository containing `.wikiflow/config.json` and a `docs/changes/active/` directory. Valid plans must include both `spec.md` and `tasks.md` files for the status tracker to discover and parse project progress.
liqunxInitialize WikiFlow projects by creating directory structures and .wikiflow/config.json.
tikazyqMonitor execution plan progress and track SubPlan and Round statuses.
MINT-IAAggregate phase, plan, requirements, git metrics, and timeline into a single dashboard.
AcidicSoilNavigate Flow framework projects by reading DASHBOARD.md for current work and progress.