@taskforcehq/taskforce 0.3.324 → 0.3.327

package/dist/resources/templates/workflow-sources/workflowDocs.mjs

@@ -1,530 +0,0 @@
-const MIN_VERSION = '0.3.13-beta.2';
-const ALLOWED_STATUSES = ['task', 'on-hold', 'in-progress', 'review', 'done'];
-const FORBIDDEN_STATUSES = ['cancelled'];
-
-const baseToolPolicy = (criticalTools, forbiddenTools = []) => ({
-    requiredToolsPolicy: {
-        critical: 'strict-fail',
-        nonCritical: 'warn-and-fallback'
-    },
-    criticalTools,
-    ...(forbiddenTools.length ? { forbiddenTools } : {}),
-    statusTransitions: {
-        allowedStatuses: ALLOWED_STATUSES,
-        forbiddenStatuses: FORBIDDEN_STATUSES
-    }
-});
-
-const baseContextPolicy = {
-    sourcePriority: ['mcp'],
-    mcp: {
-        knownTaskIdTool: '{{MCP_PREFIX}}get_task',
-        taskAttachmentListTool: '{{MCP_PREFIX}}get_task_attachments',
-        taskAttachmentReadTool: '{{MCP_PREFIX}}read_task_attachment',
-        unknownTaskIdTools: ['{{MCP_PREFIX}}list_tasks', '{{MCP_PREFIX}}search_tasks']
-    },
-    mcpUnavailableAction: 'stop-and-request-user-action'
-};
-
-const protocolBlock = (label) => [
-    `> **${label} protocol**:`,
-    '> 1. **MCP-first load**:',
-    '>    - If task ID is known, call `{{MCP_PREFIX}}get_task`.',
-    '>    - If task ID is unknown, use `{{MCP_PREFIX}}list_tasks` / `{{MCP_PREFIX}}search_tasks` to identify it.',
-    '>    - If task attachments may matter, call `{{MCP_PREFIX}}get_task_attachments` and then `{{MCP_PREFIX}}read_task_attachment` for the specific files you need.',
-    '>    - Do not try to open task attachment HTTP paths directly when MCP attachment-read tools are available.',
-    '>    - If MCP is unavailable, stop and request user action.',
-    '> 2. Print `prompts.startupChecklist`.'
-].join('\n');
-
-export const workflowDocs = [
-    {
-        name: 'do',
-        description: 'Dispatcher workflow that routes to specialized workflows based on slash command and approach.',
-        metadata: { alwaysApply: true },
-        dispatch: {
-            aliases: ['/do', '-d'],
-            routeByApproach: true,
-            approachMap: {
-                evaluate: 'evaluate',
-                collaborate: 'collaborate',
-                plan: 'plan',
-                review: 'review',
-                implement: 'execute'
-            },
-            default: 'execute'
-        },
-        compat: {
-            minTaskforceVersion: MIN_VERSION,
-            requiredToolsCritical: ['{{MCP_PREFIX}}get_task'],
-            requiredToolsOptional: ['{{MCP_PREFIX}}list_tasks', '{{MCP_PREFIX}}search_tasks', '{{MCP_PREFIX}}get_task_attachments', '{{MCP_PREFIX}}read_task_attachment', '{{MCP_PREFIX}}link_task_context', '{{MCP_PREFIX}}save_task_attachment']
-        },
-        toolPolicy: baseToolPolicy(['{{MCP_PREFIX}}get_task']),
-        contextPolicy: baseContextPolicy,
-        prompts: {
-            startupChecklist: [
-                '1.  [ ] **Task Loaded**: [ID] (Status: [Status])',
-                '2.  [ ] **Dispatch Target**: [evaluate | collaborate | plan | review | execute]'
-            ].join('\n'),
-            handoffChecklist: [
-                '- [ ] Dispatch target selected per slash-command precedence',
-                '- [ ] Routed to target workflow and exited dispatcher'
-            ].join('\n')
-        },
-        content: {
-            default: [
-                '# Taskforce Do Dispatcher (v2)',
-                '',
-                protocolBlock('DISPATCH'),
-                '',
-                '---',
-                '',
-                '## Routing Rules',
-                '1. Slash command wins over approach routing.',
-                '2. If user explicitly invokes:',
-                '   - `/evaluate` -> route to `evaluate`',
-                '   - `/collaborate` -> route to `collaborate`',
-                '   - `/plan` -> route to `plan`',
-                '   - `/review` -> route to `review`',
-                '   - `/execute` -> route to `execute`',
-                '3. If user invokes `/do`, route by `dispatch.approachMap` when task approach is mapped.',
-                '4. If no mapped approach exists, route to `dispatch.default` (`execute`).',
-                '5. After routing, print `prompts.handoffChecklist` and stop. Do not run execution phases in this workflow.'
-            ].join('\n')
-        }
-    },
-    {
-        name: 'execute',
-        description: 'Implementation workflow with MCP-first loading and status safety constraints.',
-        metadata: { alwaysApply: true },
-        dispatch: {
-            aliases: ['/execute', '-x'],
-            routeByApproach: false,
-            default: 'execute'
-        },
-        compat: {
-            minTaskforceVersion: MIN_VERSION,
-            requiredToolsCritical: ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}update_task', '{{MCP_PREFIX}}add_comment', '{{MCP_PREFIX}}finish_task'],
-            requiredToolsOptional: ['{{MCP_PREFIX}}resolve_profile', '{{MCP_PREFIX}}list_assignees', '{{MCP_PREFIX}}list_tasks', '{{MCP_PREFIX}}search_tasks', '{{MCP_PREFIX}}get_task_attachments', '{{MCP_PREFIX}}read_task_attachment', '{{MCP_PREFIX}}get_config', '{{MCP_PREFIX}}create_task', '{{MCP_PREFIX}}link_task_context', '{{MCP_PREFIX}}save_task_attachment']
-        },
-        toolPolicy: baseToolPolicy(
-            ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}update_task', '{{MCP_PREFIX}}add_comment', '{{MCP_PREFIX}}finish_task'],
-            ['{{MCP_PREFIX}}archive_task']
-        ),
-        artifacts: {
-            walkthrough: {
-                path: 'walkthrough.md',
-                required: true
-            }
-        },
-        contextPolicy: baseContextPolicy,
-        prompts: {
-            startupChecklist: [
-                '1.  [ ] **Task Loaded**: [ID] (Status: [Status])',
-                '2.  [ ] **Mode**: [execute]',
-                "3.  [ ] **Specialists Loaded**: [List names or 'None']"
-            ].join('\n'),
-            handoffChecklist: [
-                '- [ ] Final status set with `{{MCP_PREFIX}}finish_task`',
-                '- [ ] Used `done` when no explicit human validation was requested, or `review` when human validation/approval was needed',
-                '- [ ] Summary comment added with `{{MCP_PREFIX}}add_comment`',
-                '- [ ] `walkthrough.md` updated',
-                '- [ ] Planning relationships changed only when explicitly requested',
-                '- [ ] Did NOT call `{{MCP_PREFIX}}archive_task`',
-                '- [ ] Did NOT set `cancelled` unless explicitly instructed'
-            ].join('\n')
-        },
-        content: {
-            default: [
-                '# Taskforce Execute Workflow (v2)',
-                '',
-                protocolBlock('EXECUTION'),
-                '',
-                '---',
-                '',
-                '## 1. Startup (Mandatory)',
-                '',
-                '1. **Load specialists**:',
-                '   - Read the task `specialists` array.',
-                '   - Read specialist instructions exported for the active environment.',
-                '   - Acknowledge specialist constraints before implementation.',
-                '',
-                '---',
-                '',
-                '## 2. Execute Mode',
-                '**Goal**: Execute and verify changes safely.',
-                '',
-                '### Phase A: Preparation',
-                '1. **Complexity gate**:',
-                '   - If task complexity is `3` to `5`, create or refresh `implementation_plan.md` before major code edits.',
-                '   - If complexity is below `3`, planning is optional.',
-                '2. **Task management mode gate (required before task mutations)**:',
-                '   - Choose exactly one mode and state it explicitly: `checklist_mode` or `planning_mode`.',
-                '   - Default to `checklist_mode` for linear/short execution.',
-                '   - Use `planning_mode` only when at least one is true:',
-                '     - multi-system or multi-owner work',
-                '     - meaningful parallelization',
-                '     - expected duration > 1 day',
-                '     - explicit dependency/risk tracking is needed',
-                '     - user explicitly asks for more structural planning context',
-                '3. **Identity + owner strategy gate (required before task creation/update)**:',
-                '   - Call `{{MCP_PREFIX}}resolve_profile` before creating tasks, assigning tasks, or adding agent-authored comments.',
-                '   - Stateless client pattern: call `{{MCP_PREFIX}}resolve_profile`, save the returned `profileToken`, and include `profileToken` on later mutating calls if the client does not preserve session state.',
-                '   - Use the returned profile ID directly when assigning work to yourself.',
-                '   - Call `{{MCP_PREFIX}}list_assignees` before assigning tasks to someone else, then use a concrete workspace member ID or AI profile ID.',
-                '   - Never use generic owner values like `agent` or `user`.',
-                '   - If unclear who should own the work, set `owner=unassigned` and add a clarification note.',
-                '4. **Preflight confirmation gate (required before creating multiple tasks)**:',
-                '   - Confirm mode: `checklist_mode` vs `planning_mode`.',
-                '   - Confirm owner default: a concrete assignee ID, `unassigned`, or a mixed plan with explicit IDs.',
-                '   - Confirm whether assignment should be set immediately.',
-                '5. **Config gate**:',
-                '   - Before setting category/type/priority/approach/status/complexity, call `{{MCP_PREFIX}}get_config`.',
-                '   - Treat `{{MCP_PREFIX}}get_config` as the source of truth for taxonomy and enum values; do not rely on remembered type/category names.',
-                '6. **Set active state**:',
-                '   - Set status to `in-progress` with `{{MCP_PREFIX}}update_task`.',
-                '',
-                '### Phase B: Execution',
-                '1. Implement code changes.',
-                '2. Run validation steps (automated tests + manual checks as needed).',
-                '3. If user requests planning relationship work:',
-                '   - Link/unlink a task to a workstream using `{{MCP_PREFIX}}set_task_workstream` or `{{MCP_PREFIX}}clear_task_workstream`.',
-                '   - Link/unlink a workstream to an initiative using `{{MCP_PREFIX}}set_workstream_initiative` or `{{MCP_PREFIX}}clear_workstream_initiative`.',
-                '   - Create new tasks/workstreams/initiatives only when they materially improve execution clarity.',
-                '4. If blocked, switch to Collaborate mode and capture blocker context.',
-                '',
-                '### Phase C: Handover',
-                '1. Update `walkthrough.md` with:',
-                '   - What changed',
-                '   - Validation evidence',
-                '   - Remaining risks',
-                '2. Add summary comment with `{{MCP_PREFIX}}add_comment`.',
-                '3. Use `{{MCP_PREFIX}}finish_task` for final handoff.',
-                '   - Use `outcome: "done"` when the work is complete and no explicit human validation is requested.',
-                '   - Use `outcome: "review"` when human validation or approval is still needed.',
-                '   - When uncertain, prefer `review`.',
-                '4. Never set `cancelled`, and never call `{{MCP_PREFIX}}archive_task`, unless explicitly instructed by the user.',
-                '5. Do not change sibling or related task statuses unless the user explicitly instructs it.',
-                '6. Print `prompts.handoffChecklist` and stop.'
-            ].join('\n')
-        }
-    },
-    {
-        name: 'plan',
-        description: 'Planning workflow for implementation strategy and verification design.',
-        metadata: { alwaysApply: false },
-        dispatch: {
-            aliases: ['/plan', '-p'],
-            default: 'plan'
-        },
-        compat: {
-            minTaskforceVersion: MIN_VERSION,
-            requiredToolsCritical: ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}update_task', '{{MCP_PREFIX}}add_comment'],
-            requiredToolsOptional: ['{{MCP_PREFIX}}list_tasks', '{{MCP_PREFIX}}search_tasks', '{{MCP_PREFIX}}get_task_attachments', '{{MCP_PREFIX}}read_task_attachment', '{{MCP_PREFIX}}get_config', '{{MCP_PREFIX}}link_task_context', '{{MCP_PREFIX}}save_task_attachment']
-        },
-        toolPolicy: baseToolPolicy(
-            ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}update_task', '{{MCP_PREFIX}}add_comment'],
-            ['{{MCP_PREFIX}}archive_task']
-        ),
-        artifacts: {
-            implementationPlan: {
-                path: 'task attachment "implementation-plan.md"',
-                required: false,
-                savePolicy: 'ask-before-save'
-            }
-        },
-        contextPolicy: baseContextPolicy,
-        prompts: {
-            startupChecklist: [
-                '1.  [ ] **Task Loaded**: [ID] (Status: [Status])',
-                '2.  [ ] **Mode**: [plan]',
-                "3.  [ ] **Specialists Loaded**: [List names or 'None']"
-            ].join('\n'),
-            optionalArtifactPrompt: 'I prepared the implementation plan in-screen. Save as `{path}` and attach it to this task context?',
-            handoffPrompt: 'Planning complete. Review the in-screen plan, then run `/do <id>` to execute.'
-        },
-        content: {
-            default: [
-                '# Taskforce Plan Workflow (v2)',
-                '',
-                protocolBlock('PLANNING'),
-                '',
-                '---',
-                '',
-                '## 1. Startup (Mandatory)',
-                '',
-                '1. Call `{{MCP_PREFIX}}get_config` before setting category/type/priority/approach/status/complexity.',
-                '   - Treat `{{MCP_PREFIX}}get_config` as the source of truth for taxonomy and enum values; do not rely on remembered type/category names.',
-                '2. Set status to `in-progress` via `{{MCP_PREFIX}}update_task`.',
-                '3. Load specialist instructions for the active environment and acknowledge constraints.',
-                '4. Load all relevant context sources tied to the task.',
-                '',
-                '---',
-                '',
-                '## 2. Planning Deliverable',
-                '',
-                '0. Choose and record task management mode for follow-on execution:',
-                '   - `checklist_mode` (single task + in-task checklist) for linear short work.',
-                '   - `planning_mode` (tasks grouped into workstreams/initiatives) only when structure improves clarity, dependencies, or ownership.',
-                '   - Record owner strategy as explicit assignee IDs, `unassigned`, or a mixed plan with explicit IDs.',
-                '',
-                '1. Define file-level change plan (exact files and intended changes).',
-                '2. Identify compatibility and regression risks.',
-                '3. Define automated and manual verification steps.',
-                '4. Present the implementation plan in-screen using this exact structure:',
-                '   - `## Implementation Plan`',
-                '   - `### Goal`',
-                '   - `### Change Plan`',
-                '   - `### Risk Analysis`',
-                '   - `### Verification Checklist`',
-                '5. Add a concise planning summary comment via `{{MCP_PREFIX}}add_comment` using this exact structure:',
-                '   - `## Plan Summary`',
-                '   - `### Goal`',
-                '   - `### Scope`',
-                '   - `### Next Action`',
-                '6. Ask whether to save as `{artifacts.implementationPlan.path}`.',
-                '7. If user confirms, persist task-specific content via `{{MCP_PREFIX}}save_task_attachment` using `filename: "implementation-plan.md"`.',
-                '   - Use `{{MCP_PREFIX}}link_task_context` only for external http(s) URLs that should stay as references.',
-                '8. If setting status to `task` or `on-hold`, add explicit comment justification using `{{MCP_PREFIX}}add_comment`.',
-                '9. Never set `cancelled`, and never call `{{MCP_PREFIX}}archive_task`, unless explicitly instructed by the user.',
-                '10. Print `prompts.handoffPrompt` and stop.'
-            ].join('\n')
-        }
-    },
-    {
-        name: 'collaborate',
-        description: 'Collaboration workflow for requirement refinement and architecture consensus.',
-        metadata: { alwaysApply: false },
-        dispatch: {
-            aliases: ['/collaborate', '-c'],
-            default: 'collaborate'
-        },
-        compat: {
-            minTaskforceVersion: MIN_VERSION,
-            requiredToolsCritical: ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}add_comment'],
-            requiredToolsOptional: ['{{MCP_PREFIX}}list_tasks', '{{MCP_PREFIX}}search_tasks', '{{MCP_PREFIX}}get_task_attachments', '{{MCP_PREFIX}}read_task_attachment', '{{MCP_PREFIX}}link_task_context', '{{MCP_PREFIX}}save_task_attachment']
-        },
-        toolPolicy: baseToolPolicy(
-            ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}add_comment'],
-            ['{{MCP_PREFIX}}archive_task']
-        ),
-        artifacts: {
-            collaborationBlueprint: {
-                path: 'task attachment "collaboration-blueprint.md"',
-                required: false,
-                savePolicy: 'ask-before-save'
-            }
-        },
-        contextPolicy: baseContextPolicy,
-        prompts: {
-            startupChecklist: [
-                '1.  [ ] **Task Loaded**: [ID] (Status: [Status])',
-                '2.  [ ] **Mode**: [collaborate]',
-                "3.  [ ] **Specialists Loaded**: [List names or 'None']"
-            ].join('\n'),
-            optionalArtifactPrompt: 'I prepared the collaboration blueprint in-screen. Save as `{path}` and attach it to this task context?'
-        },
-        content: {
-            default: [
-                '# Taskforce Collaborate Workflow (v2)',
-                '',
-                protocolBlock('COLLABORATION'),
-                '',
-                '---',
-                '',
-                '## 1. Collaboration Loop',
-                '',
-                '1. Load specialist instructions for the active environment.',
-                '2. Clarify goals, constraints, and edge cases with the user.',
-                '3. Propose architecture and tradeoffs.',
-                '4. Iterate to consensus.',
-                '',
-                '## 2. Blueprint Handover',
-                '',
-                '1. Present a structured blueprint in-screen.',
-                '2. Use this exact structure for consistency:',
-                '   - `## Collaboration Blueprint`',
-                '   - `### Problem Statement`',
-                '   - `### Constraints`',
-                '   - `### Proposed Architecture`',
-                '   - `### Must-Haves`',
-                '   - `### Non-Goals`',
-                '   - `### Risks & Open Questions`',
-                '   - `### Recommended Next Step`',
-                '3. Add a concise blueprint summary comment via `{{MCP_PREFIX}}add_comment` using this exact structure:',
-                '   - `## Collaboration Summary`',
-                '   - `### Architecture Direction`',
-                '   - `### Key Constraints`',
-                '   - `### Next Step`',
-                '4. Ask whether to save as `{artifacts.collaborationBlueprint.path}`.',
-                '5. If user confirms, persist task-specific content via `{{MCP_PREFIX}}save_task_attachment` using `filename: "collaboration-blueprint.md"`.',
-                '   - Use `{{MCP_PREFIX}}link_task_context` only for external http(s) URLs that should stay as references.',
-                '6. Ask concise clarification questions only if required fields above are missing.',
-                '7. If setting status to `task` or `on-hold`, add explicit comment justification using `{{MCP_PREFIX}}add_comment`.',
-                '8. Never set `cancelled`, and never call `{{MCP_PREFIX}}archive_task`, unless explicitly instructed by the user.',
-                '9. Ask user whether to proceed to `/plan`.',
-                '10. Stop.'
-            ].join('\n')
-        }
-    },
-    {
-        name: 'evaluate',
-        description: 'Evaluation workflow for strategic analysis, scoring, and recommendation.',
-        metadata: { alwaysApply: false },
-        dispatch: {
-            aliases: ['/evaluate', '-e'],
-            default: 'evaluate'
-        },
-        compat: {
-            minTaskforceVersion: MIN_VERSION,
-            requiredToolsCritical: ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}update_task', '{{MCP_PREFIX}}add_comment'],
-            requiredToolsOptional: ['{{MCP_PREFIX}}list_tasks', '{{MCP_PREFIX}}search_tasks', '{{MCP_PREFIX}}get_task_attachments', '{{MCP_PREFIX}}read_task_attachment', '{{MCP_PREFIX}}get_config', '{{MCP_PREFIX}}link_task_context', '{{MCP_PREFIX}}save_task_attachment']
-        },
-        toolPolicy: baseToolPolicy(
-            ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}update_task', '{{MCP_PREFIX}}add_comment'],
-            ['{{MCP_PREFIX}}archive_task']
-        ),
-        artifacts: {
-            evaluationReport: {
-                path: 'task attachment "evaluation.md"',
-                required: false,
-                savePolicy: 'ask-before-save'
-            }
-        },
-        contextPolicy: baseContextPolicy,
-        prompts: {
-            startupChecklist: [
-                '1.  [ ] **Task Loaded**: [ID] (Status: [Status])',
-                '2.  [ ] **Mode**: [evaluate]',
-                "3.  [ ] **Specialists Loaded**: [List names or 'None']"
-            ].join('\n'),
-            optionalArtifactPrompt: 'I prepared the evaluation in-screen. Save as `{path}` and attach it to this task context?'
-        },
-        content: {
-            default: [
-                '# Taskforce Evaluate Workflow (v2)',
-                '',
-                protocolBlock('EVALUATION'),
-                '',
-                '---',
-                '',
-                '## 1. Strategic Analysis',
-                '',
-                '1. Validate the problem and business/user impact.',
-                '2. Evaluate alternatives and opportunity cost.',
-                '3. Score value and risk with explicit reasoning.',
-                '4. Recommend: Proceed, Pivot, or Kill.',
-                '',
-                '## 2. Task Updates',
-                '',
-                '1. Use `{{MCP_PREFIX}}update_task` to adjust priority/status only within allowed statuses.',
-                '   - If setting status to `task` or `on-hold`, add explicit comment justification using `{{MCP_PREFIX}}add_comment`.',
-                '2. Present a structured evaluation in-screen using this exact structure:',
-                '   - `## Evaluation Summary`',
-                '   - `### Recommendation (Proceed | Pivot | Kill)`',
-                '   - `### Value Score (1-5)`',
-                '   - `### Risk Score (1-5)`',
-                '   - `### Alternatives Considered`',
-                '   - `### Key Tradeoffs`',
-                '   - `### Next Step`',
-                '3. Add a concise evaluation summary comment via `{{MCP_PREFIX}}add_comment` using this exact structure:',
-                '   - `## Evaluation Summary`',
-                '   - `### Recommendation (Proceed | Pivot | Kill)`',
-                '   - `### Value Score (1-5)`',
-                '   - `### Risk Score (1-5)`',
-                '   - `### Next Step`',
-                '4. Ask whether to save as `{artifacts.evaluationReport.path}`.',
-                '5. If user confirms, persist task-specific content via `{{MCP_PREFIX}}save_task_attachment` using `filename: "evaluation.md"`.',
-                '   - Use `{{MCP_PREFIX}}link_task_context` only for external http(s) URLs that should stay as references.',
-                '6. Never set `cancelled`, and never call `{{MCP_PREFIX}}archive_task`, unless explicitly instructed by the user.',
-                '',
-                '## 3. Optional Report Artifact',
-                '',
-                '1. Use report files only when user opts in.',
-                '2. Save to `task attachment "evaluation.md"` and attach to task context when approved.',
-                '   - If the document should become a shared durable document, save it through the canonical document/document-manager flow instead of a raw `docs/` file.',
-                '3. Stop.'
-            ].join('\n')
-        }
-    },
-    {
-        name: 'review',
-        description: 'Review workflow for QA analysis and pass/warn/fail handoff.',
-        metadata: { alwaysApply: false },
-        dispatch: {
-            aliases: ['/review', '-r'],
-            default: 'review'
-        },
-        compat: {
-            minTaskforceVersion: MIN_VERSION,
-            requiredToolsCritical: ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}add_comment'],
-            requiredToolsOptional: ['{{MCP_PREFIX}}list_tasks', '{{MCP_PREFIX}}search_tasks', '{{MCP_PREFIX}}get_task_attachments', '{{MCP_PREFIX}}read_task_attachment', '{{MCP_PREFIX}}update_task', '{{MCP_PREFIX}}link_task_context', '{{MCP_PREFIX}}save_task_attachment']
-        },
-        toolPolicy: baseToolPolicy(
-            ['{{MCP_PREFIX}}get_task', '{{MCP_PREFIX}}add_comment'],
-            ['{{MCP_PREFIX}}archive_task']
-        ),
-        artifacts: {
-            reviewReport: {
-                path: 'task attachment "review.md"',
-                required: false,
-                savePolicy: 'ask-before-save'
-            }
-        },
-        contextPolicy: baseContextPolicy,
-        prompts: {
-            startupChecklist: [
-                '1.  [ ] **Task Loaded**: [ID] (Status: [Status])',
-                '2.  [ ] **Mode**: [review]',
-                "3.  [ ] **Specialists Loaded**: [List names or 'None']"
-            ].join('\n'),
-            optionalArtifactPrompt: 'I prepared the review in-screen. Save as `{path}` and attach it to this task context?'
-        },
-        content: {
-            default: [
-                '# Taskforce Review Workflow (v2)',
-                '',
-                protocolBlock('REVIEW'),
-                '',
-                '---',
-                '',
-                '## 1. Review Analysis',
-                '',
-                '1. Identify the review target (plan, code, docs, or mixed artifacts).',
-                '2. Perform QA pass:',
-                '   - risk and safety check',
-                '   - regression check',
-                '   - standards compliance',
-                '3. Produce verdict: PASS / WARN / FAIL with actionable findings.',
-                '',
-                '## 2. Task Updates',
-                '',
-                '1. Present a structured review in-screen using this exact structure:',
-                '   - `## Review Verdict`',
-                '   - `### Verdict (PASS | WARN | FAIL)`',
-                '   - `### Findings`',
-                '   - `### Regression Risks`',
-                '   - `### Required Fixes`',
-                '   - `### Recommended Next Status`',
-                '2. Add a concise review summary comment via `{{MCP_PREFIX}}add_comment` using this exact structure:',
-                '   - `## Review Summary`',
-                '   - `### Verdict (PASS | WARN | FAIL)`',
-                '   - `### Findings`',
-                '   - `### Next Status`',
-                '3. Ask whether to save as `{artifacts.reviewReport.path}`.',
-                '4. If user confirms, persist task-specific content via `{{MCP_PREFIX}}save_task_attachment` using `filename: "review.md"`.',
-                '   - Use `{{MCP_PREFIX}}link_task_context` only for external http(s) URLs that should stay as references.',
-                '5. Keep status within allowed statuses (`task`, `on-hold`, `in-progress`, `review`, `done`) unless user explicitly instructs otherwise.',
-                '   - If setting status to `task` or `on-hold`, add explicit comment justification using `{{MCP_PREFIX}}add_comment`.',
-                '6. Never set `cancelled`, and never call `{{MCP_PREFIX}}archive_task`, unless explicitly instructed by the user.',
-                '',
-                '## 3. Optional Report Artifact',
-                '',
-                '1. Use report files only when user opts in.',
-                '2. Save to `task attachment "review.md"` and attach to task context when approved.',
-                '   - If the document should become a shared durable document, save it through the canonical document/document-manager flow instead of a raw `docs/` file.',
-                '3. Stop.'
-            ].join('\n')
-        }
-    }
-];

package/dist/resources/templates/workflow-sources/workflowEditorOverrides.json

@@ -1 +0,0 @@
-{}

package/dist/resources/templates/workflows/collaborate.yaml

@@ -1,110 +0,0 @@
-version: 2
-name: collaborate
-description: Collaboration workflow for requirement refinement and architecture consensus.
-type: workflow
-metadata:
-  alwaysApply: false
-dispatch:
-  aliases:
-    - /collaborate
-    - "-c"
-  default: collaborate
-compat:
-  minTaskforceVersion: 0.3.13-beta.2
-  requiredToolsCritical:
-    - "{{MCP_PREFIX}}get_task"
-    - "{{MCP_PREFIX}}add_comment"
-  requiredToolsOptional:
-    - "{{MCP_PREFIX}}list_tasks"
-    - "{{MCP_PREFIX}}search_tasks"
-    - "{{MCP_PREFIX}}get_task_attachments"
-    - "{{MCP_PREFIX}}read_task_attachment"
-    - "{{MCP_PREFIX}}link_task_context"
-    - "{{MCP_PREFIX}}save_task_attachment"
-toolPolicy:
-  requiredToolsPolicy:
-    critical: strict-fail
-    nonCritical: warn-and-fallback
-  criticalTools:
-    - "{{MCP_PREFIX}}get_task"
-    - "{{MCP_PREFIX}}add_comment"
-  forbiddenTools:
-    - "{{MCP_PREFIX}}archive_task"
-  statusTransitions:
-    allowedStatuses:
-      - task
-      - on-hold
-      - in-progress
-      - review
-      - done
-    forbiddenStatuses:
-      - cancelled
-artifacts:
-  collaborationBlueprint:
-    path: task attachment "collaboration-blueprint.md"
-    required: false
-    savePolicy: ask-before-save
-contextPolicy:
-  sourcePriority:
-    - mcp
-  mcp:
-    knownTaskIdTool: "{{MCP_PREFIX}}get_task"
-    taskAttachmentListTool: "{{MCP_PREFIX}}get_task_attachments"
-    taskAttachmentReadTool: "{{MCP_PREFIX}}read_task_attachment"
-    unknownTaskIdTools:
-      - "{{MCP_PREFIX}}list_tasks"
-      - "{{MCP_PREFIX}}search_tasks"
-  mcpUnavailableAction: stop-and-request-user-action
-prompts:
-  startupChecklist: |-
-    1.  [ ] **Task Loaded**: [ID] (Status: [Status])
-    2.  [ ] **Mode**: [collaborate]
-    3.  [ ] **Specialists Loaded**: [List names or 'None']
-  optionalArtifactPrompt: I prepared the collaboration blueprint in-screen. Save as `{path}` and attach it to this task context?
-content:
-  default: |-
-    # Taskforce Collaborate Workflow (v2)
-
-    > **COLLABORATION protocol**:
-    > 1. **MCP-first load**:
-    >    - If task ID is known, call `{{MCP_PREFIX}}get_task`.
-    >    - If task ID is unknown, use `{{MCP_PREFIX}}list_tasks` / `{{MCP_PREFIX}}search_tasks` to identify it.
-    >    - If task attachments may matter, call `{{MCP_PREFIX}}get_task_attachments` and then `{{MCP_PREFIX}}read_task_attachment` for the specific files you need.
-    >    - Do not try to open task attachment HTTP paths directly when MCP attachment-read tools are available.
-    >    - If MCP is unavailable, stop and request user action.
-    > 2. Print `prompts.startupChecklist`.
-
-    ---
-
-    ## 1. Collaboration Loop
-
-    1. Load specialist instructions for the active environment.
-    2. Clarify goals, constraints, and edge cases with the user.
-    3. Propose architecture and tradeoffs.
-    4. Iterate to consensus.
-
-    ## 2. Blueprint Handover
-
-    1. Present a structured blueprint in-screen.
-    2. Use this exact structure for consistency:
-       - `## Collaboration Blueprint`
-       - `### Problem Statement`
-       - `### Constraints`
-       - `### Proposed Architecture`
-       - `### Must-Haves`
-       - `### Non-Goals`
-       - `### Risks & Open Questions`
-       - `### Recommended Next Step`
-    3. Add a concise blueprint summary comment via `{{MCP_PREFIX}}add_comment` using this exact structure:
-       - `## Collaboration Summary`
-       - `### Architecture Direction`
-       - `### Key Constraints`
-       - `### Next Step`
-    4. Ask whether to save as `{artifacts.collaborationBlueprint.path}`.
-    5. If user confirms, persist task-specific content via `{{MCP_PREFIX}}save_task_attachment` using `filename: "collaboration-blueprint.md"`.
-       - Use `{{MCP_PREFIX}}link_task_context` only for external http(s) URLs that should stay as references.
-    6. Ask concise clarification questions only if required fields above are missing.
-    7. If setting status to `task` or `on-hold`, add explicit comment justification using `{{MCP_PREFIX}}add_comment`.
-    8. Never set `cancelled`, and never call `{{MCP_PREFIX}}archive_task`, unless explicitly instructed by the user.
-    9. Ask user whether to proceed to `/plan`.
-    10. Stop.