From taskflow
Show the current state of the TaskFlow pipeline for a project — which steps are done, in progress, pending, blocked, or rejected. Use this to get an overview of where the pipeline stands.
How this skill is triggered — by the user, by Claude, or both
Slash command
/taskflow:pipeline-status [project ID or leave blank to list projects][project ID or leave blank to list projects]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. If the user provided a project ID, use it. Otherwise:
If the user provided a project ID, use it. Otherwise:
list_projects() and display the results so the user can pick one.Call read_pipeline_status(project_id=...).
Display the project name and status.
Display features (if any).
Display tasks grouped by status using this format:
| Task ID | Step | Step Name | Agent | Feature |
|---|
| Task ID | Step | Step Name | Agent | Feature |
|---|
| Task ID | Step | Step Name | Agent | Feature | Retry # |
|---|
(count only — e.g. "12 tasks completed")
If there are blocked tasks, highlight them and suggest:
"Blocked tasks require human intervention. You can reset retry_count or override status directly in the DB, or invoke the relevant agent to assess the situation."
If the pipeline looks stalled (no in-progress, no pending), suggest /my-tasks to check each role.
npx claudepluginhub pedrogrande/taskflowEnforces cross-project coding conventions for naming, readability, immutability, and code-quality review. Activates on new projects, refactoring, or code review.