القائمة
Check for and apply pending TaskFlow schema migrations after pulling a new release.
التثبيت باستخدام 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.
Guide for the product_manager agent when writing feature records and definitions of done in step 3. Auto-loaded when a step-3 task is in progress.
| name | upgrade |
| description | Check for and apply pending TaskFlow schema migrations after pulling a new release. |
| user-invocable | true |
Use this command after pulling a new release of TaskFlow to ensure your database schema is up-to-date.
upgrade MCP tool to check for and apply any pending schema migrations.status is "up-to-date": tell the user their schema is current, show the current version number.status is "migrations applied": list the migrations that were applied and the new version number./pipeline-status to verify their project data is intact.✅ Schema is up-to-date (version X)
or
🔄 Applied N migration(s):
- 001_add_cycle_number
- 002_add_whatever
Schema version: X → Y
Run /pipeline-status to verify your project data.