メニュー
Manage SPECS/Workplan.md task operations for this repository. Use when you need to add a new task entry with the canonical template, pick the next actionable task, or mark a task as completed while keeping selector state in sync.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate repeated task delivery using the repository FLOW process by running one task at a time and delegating execution to $flow-run. Use when asked to process multiple tasks in sequence, run tasks in a continuous cycle, or keep shipping the next task only after the previous task pull request has passing CI.
Run the complete task workflow for this repository by strictly following SPECS/COMMANDS/FLOW.md from BRANCH through ARCHIVE-REVIEW, including required commit checkpoints and quality gates. Use when asked to do the next task end-to-end, complete the full workflow, or execute "start to finish" task delivery in this project.
Review GitHub pull request CI outcomes with the GitHub CLI and extract actionable failure details from GitHub Actions logs. Use when asked to check failing PR checks, inspect lint/test/type-check errors, identify failing jobs, or summarize why a PR pipeline failed and what to fix first.
Create or update GitHub pull requests with the GitHub CLI (`gh`) using the repository PR template. Use when asked to open a PR, fix PR description formatting, align description with `.github/PULL_REQUEST_TEMPLATE.md`, or prepare a merge-ready PR with validation results.
Create focused, scoped git commits for the current task. Use when the workflow requires committing work, when only specific files should be staged, when commit messages must be clear and present-tense, or when validating the worktree state before push/archive.
Task tracking and workflow management for the mcpbridge-wrapper project. Use when working on mcpbridge-wrapper to: (1) Get the next task to work on, (2) Mark tasks as completed, (3) View project progress, (4) List available tasks. The workplan is stored in SPECS/Workplan.md with 65 tasks across 7 phases. Task state is persisted in .task_state.json.
| name | workplan-task-ops |
| description | Manage SPECS/Workplan.md task operations for this repository. Use when you need to add a new task entry with the canonical template, pick the next actionable task, or mark a task as completed while keeping selector state in sync. |
Manage task lifecycle operations in SPECS/Workplan.md using the repository conventions.
Collect these before running any operation:
SPECS/Workplan.md⬜️ open or ✅ completed)Use these sources of truth:
SPECS/TASK_TEMPLATE.md for task entry format and markersSPECS/Workplan.md for the actual task listscripts/pick_next_task.py for next-task selection and completion state updatesP{phase}-T{n}FU-{parent/topic}-{n}BUG-T{n}Place the task in the correct section of SPECS/Workplan.md.
Copy the open-task block from SPECS/TASK_TEMPLATE.md and fill all fields:
⬜️ markerDescription, Priority, Dependencies, ParallelizableOutputs/ArtifactsAcceptance Criteria with unchecked boxesnonepython3 scripts/pick_next_task.py
Read the suggested task and dependency statuses.
Confirm the suggestion is still open in SPECS/Workplan.md (⬜️) and not archived.
Update SPECS/INPROGRESS/next.md using the output template in SPECS/COMMANDS/SELECT.md.
Confirm completion evidence exists (implementation done, validation/review state consistent).
Update the task block in SPECS/Workplan.md:
⬜️ to ✅Status line with date when applicable[x])python3 scripts/pick_next_task.py --done <TASK_ID>
python3 scripts/pick_next_task.py
SPECS/TASK_TEMPLATE.md.