メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create VS Code custom agents (.agent.md files) that define specialized AI personas with scoped tools, model preferences, handoffs, and hooks. Use when creating a new custom agent, configuring tool restrictions for a role, setting up agent handoffs for multi-step workflows, adding agent-scoped hooks, or deciding between agents vs prompt files vs skills.
Guide for the Project Initiation Manager when conducting the brief conversation. Covers all three entry paths (fresh start, rough brief, form JSON), the one-question-at-a-time conversation rules, completeness-driven question ordering, and how to generate the markdown brief.
Show pending tasks for a TaskFlow agent role. Lists what work is waiting and which project/feature each task belongs to. Use this to find out what an agent needs to do next.
Add TaskFlow to an existing project. Scans the workspace, detects existing agents/skills/MCP servers, and guides the user through creating a brief that captures what's already built.
Start a new TaskFlow project. Prompts for a project brief (file path or inline text), then hands off to the Project Initiation Manager to build and validate the brief before the Dev Manager configures the team. Use this to kick off a new development cycle.
Check for and apply pending TaskFlow schema migrations after pulling a new release.
| name | pipeline-status |
| description | 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. |
| argument-hint | [project ID or leave blank to list projects] |
| disable-model-invocation | true |
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.