From 6ec56a32bcb58f897e94f3470159a9954aae1f55 Mon Sep 17 00:00:00 2001 From: Jack Rudenko Date: Sat, 31 Jan 2026 00:16:06 +1100 Subject: [PATCH 1/3] docs: add Tasks system migration design MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Plan to migrate all plugins from TodoWrite to new Tasks system - Pattern mapping from old to new API - Migration order: multimodel → dev → frontend → others - New capabilities: dependencies, cross-session, ownership - 115 files across 12 plugins to update --- .../2026-01-30-tasks-migration-design.md | 181 ++++++++++++++++++ 1 file changed, 181 insertions(+) create mode 100644 docs/plans/2026-01-30-tasks-migration-design.md diff --git a/docs/plans/2026-01-30-tasks-migration-design.md b/docs/plans/2026-01-30-tasks-migration-design.md new file mode 100644 index 0000000..8e022c9 --- /dev/null +++ b/docs/plans/2026-01-30-tasks-migration-design.md @@ -0,0 +1,181 @@ +# Tasks System Migration Design + +**Date:** 2026-01-30 +**Status:** Approved +**Author:** Brainstorming session dev-brainstorm-20260130-172337-68801ffa + +--- + +## Summary + +Migrate all MAG Claude Plugins from TodoWrite to the new Tasks system to align with Claude Code platform evolution and unlock new capabilities (dependencies, cross-session persistence, task ownership). + +## Context + +Claude Code introduced the Tasks system as a replacement for TodoWrite: +- **File-based persistence** in `~/.claude/tasks/` +- **Cross-session collaboration** via `CLAUDE_CODE_TASK_LIST_ID` env var +- **Task dependencies** with `blocks`/`blockedBy` fields +- **4 tools** instead of 1: TaskCreate, TaskUpdate, TaskList, TaskGet + +Our plugins have 115 files referencing TodoWrite across 12 plugins. + +## Decision + +**Full migration** - Replace all TodoWrite references with Tasks patterns. + +## Pattern Mapping + +### Initialization + +```markdown +# OLD +TodoWrite: Create task list + - PHASE 1: Gather requirements (pending) + - PHASE 2: Design architecture (pending) + +# NEW +TaskCreate: + subject: "PHASE 1: Gather requirements" + description: "Collect user requirements through clarifying questions" + activeForm: "Gathering requirements" + +TaskCreate: + subject: "PHASE 2: Design architecture" + description: "Create architecture plan based on requirements" + activeForm: "Designing architecture" +``` + +### Status Transitions + +```markdown +# OLD +Update TodoWrite: Mark "PHASE 1" as in_progress +... work ... +Update TodoWrite: Mark "PHASE 1" as completed + +# NEW +TaskUpdate: taskId="1", status="in_progress" +... work ... +TaskUpdate: taskId="1", status="completed" +``` + +### New: Dependencies + +```markdown +TaskCreate: + subject: "PHASE 3: Implementation" + description: "Implement the feature" + +TaskUpdate: + taskId: "3" + addBlockedBy: ["2"] # Blocked until PHASE 2 completes +``` + +### New: Ownership for Parallel Agents + +```markdown +TaskCreate: subject="Claude review", owner="claude-agent" +TaskCreate: subject="Grok review", owner="grok-agent" +TaskCreate: subject="Gemini review", owner="gemini-agent" +# Each agent updates only its task +``` + +### New: Cross-Session + +```bash +# Start work +CLAUDE_CODE_TASK_LIST_ID=feature-auth claude + +# Resume later (tasks persist) +CLAUDE_CODE_TASK_LIST_ID=feature-auth claude +``` + +## Migration Order + +| Phase | Plugin | Files | Priority | +|-------|--------|-------|----------| +| 1 | multimodel | 7 | CRITICAL - foundation | +| 2 | dev | 29 | HIGH - heaviest user | +| 3 | frontend | 16 | MEDIUM | +| 4 | seo | 13 | MEDIUM | +| 5 | conductor | 11 | MEDIUM | +| 6 | agentdev | 9 | MEDIUM | +| 7 | instantly | 8 | LOW | +| 8 | video-editing | 6 | LOW | +| 9 | bun | 6 | LOW | +| 10 | nanobanana | 5 | LOW | +| 11 | autopilot | 4 | LOW | +| 12 | code-analysis | 1 | LOW | + +## Key Changes + +### Skill Rename + +``` +OLD: plugins/multimodel/skills/todowrite-orchestration/ +NEW: plugins/multimodel/skills/task-orchestration/ +``` + +### Files by Plugin + +**multimodel (7 files):** +- `skills/todowrite-orchestration/SKILL.md` → `skills/task-orchestration/SKILL.md` +- `skills/multi-agent-coordination/SKILL.md` +- `skills/multi-model-validation/SKILL.md` +- `skills/hierarchical-coordinator/SKILL.md` +- `skills/model-tracking-protocol/SKILL.md` +- `skills/batching-patterns/SKILL.md` +- `commands/team.md` + +**dev (29 files):** +- 12 commands +- 14 agents +- 3 discipline skills + +## Implementation Tasks + +``` +1. Create task-orchestration skill (rewrite of todowrite-orchestration) +2. Update multimodel plugin references +3. Update dev plugin (29 files) +4. Update frontend plugin (16 files) +5. Update remaining plugins (63 files) +6. Update documentation and CLAUDE.md +7. Test workflows end-to-end +``` + +## Testing + +1. **Basic workflow:** `/dev:implement "Add hello world"` +2. **Multi-phase:** `/dev:feature "Add authentication"` +3. **Parallel agents:** `/multimodel:team "Review code"` +4. **Cross-session:** Start/resume with `CLAUDE_CODE_TASK_LIST_ID` + +## Risks & Mitigations + +| Risk | Mitigation | +|------|------------| +| Breaking existing workflows | TodoWrite still works - gradual rollout | +| Large changeset | Phase by plugin priority | +| Missing edge cases | Manual testing per phase | + +## Timeline + +- **Week 1:** multimodel + dev plugins +- **Week 2:** Remaining plugins + testing + +## Success Criteria + +- [ ] All 115 files migrated +- [ ] `task-orchestration` skill documented +- [ ] Cross-session workflows tested +- [ ] Dependency tracking working +- [ ] No regressions in existing commands + +--- + +## References + +- [Claude Code Tasks Announcement](https://medium.com/@joe.njenga/claude-code-tasks-are-here-new-update-turns-claude-code-todos-to-tasks-a0be00e70847) +- [Session artifacts](../ai-docs/sessions/dev-brainstorm-20260130-172337-68801ffa/) From a6a4ac20795edc8181d11f54a70a65e3707df145 Mon Sep 17 00:00:00 2001 From: Jack Rudenko Date: Sat, 31 Jan 2026 09:29:14 +1100 Subject: [PATCH 2/3] refactor: migrate all plugins from TodoWrite to Tasks system MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit BREAKING CHANGE: TodoWrite API replaced with Tasks (TaskCreate, TaskUpdate, TaskList, TaskGet) Migration scope: - Renamed todowrite-orchestration → task-orchestration skill (v2.0.0) - Updated 115+ markdown files across 12 plugins - Added 576 Tasks API references Changes by plugin: - multimodel: Core orchestration skills rewritten with new API - dev: 29 files (commands, agents, skills) - frontend: 16 files - seo: 13 files - conductor: 11 files - agentdev: 9 files - instantly: 8 files - video-editing: 6 files - bun: 6 files - nanobanana: 5 files - autopilot: 4 files - code-analysis: 1 file New capabilities documented: - Task dependencies (blockedBy/blocks) - Task ownership for parallel agents (owner field) - Cross-session persistence (CLAUDE_CODE_TASK_LIST_ID) Verification: - 0 TodoWrite refs in live code (3 intentional "MUST NOT" restrictions remain) - 576 Tasks API references added - task-orchestration skill fully rewritten with new patterns --- plugins/agentdev/agents/architect.md | 22 +- plugins/agentdev/agents/developer.md | 24 +- plugins/agentdev/agents/reviewer.md | 22 +- plugins/agentdev/commands/develop.md | 14 +- plugins/agentdev/commands/help.md | 12 +- plugins/agentdev/skills/patterns/SKILL.md | 24 +- plugins/agentdev/skills/schemas/SKILL.md | 16 +- .../agentdev/skills/xml-standards/SKILL.md | 4 +- plugins/autopilot/agents/task-executor.md | 2 +- plugins/autopilot/commands/create-task.md | 4 +- plugins/autopilot/commands/run.md | 6 +- plugins/autopilot/commands/status.md | 2 +- plugins/bun/ARCHITECTURE.md | 8 +- plugins/bun/agents/api-architect.md | 8 +- plugins/bun/agents/apidog.md | 8 +- plugins/bun/agents/backend-developer.md | 18 +- plugins/bun/commands/implement-api.md | 8 +- plugins/bun/commands/setup-project.md | 4 +- plugins/code-analysis/commands/analyze.md | 2 +- plugins/conductor/README.md | 2 +- plugins/conductor/commands/help.md | 6 +- plugins/conductor/commands/implement.md | 18 +- plugins/conductor/commands/new-track.md | 6 +- plugins/conductor/commands/revert.md | 4 +- plugins/conductor/commands/setup.md | 6 +- plugins/conductor/commands/status.md | 6 +- plugins/conductor/skills/implement/SKILL.md | 12 +- plugins/conductor/skills/new-track/SKILL.md | 4 +- plugins/conductor/skills/revert/SKILL.md | 2 +- plugins/conductor/skills/setup/SKILL.md | 4 +- plugins/conductor/skills/status/SKILL.md | 6 +- plugins/dev/agents/architect.md | 4 +- plugins/dev/agents/debugger.md | 4 +- plugins/dev/agents/developer.md | 6 +- plugins/dev/agents/devops.md | 4 +- plugins/dev/agents/doc-analyzer.md | 2 +- plugins/dev/agents/doc-fixer.md | 2 +- plugins/dev/agents/doc-writer.md | 2 +- plugins/dev/agents/researcher.md | 8 +- plugins/dev/agents/stack-detector.md | 6 +- plugins/dev/agents/synthesizer.md | 10 +- plugins/dev/agents/test-architect.md | 4 +- plugins/dev/agents/ui-engineer.md | 13 +- plugins/dev/agents/ui.md | 6 +- .../design.md | 6 +- .../reviews/impl-review/qwen3-vl.md | 2 +- plugins/dev/commands/architect.md | 4 +- plugins/dev/commands/brainstorm.md | 6 +- plugins/dev/commands/create-style.md | 6 +- plugins/dev/commands/debug.md | 6 +- plugins/dev/commands/deep-research.md | 12 +- plugins/dev/commands/doc.md | 18 +- plugins/dev/commands/feature.md | 10 +- plugins/dev/commands/help.md | 2 +- plugins/dev/commands/implement.md | 10 +- plugins/dev/commands/interview.md | 6 +- plugins/dev/commands/ui.md | 26 +- .../verification-before-completion/SKILL.md | 2 +- .../skills/frontend/react-typescript/SKILL.md | 2 +- .../skills/frontend/tanstack-query/SKILL.md | 12 +- .../skills/planning/brainstorming/SKILL.md | 9 +- plugins/frontend/agents/api-analyst.md | 2 +- plugins/frontend/agents/architect.md | 30 +- plugins/frontend/agents/cleaner.md | 2 +- plugins/frontend/agents/css-developer.md | 4 +- plugins/frontend/agents/designer.md | 4 +- plugins/frontend/agents/developer.md | 28 +- plugins/frontend/agents/plan-reviewer.md | 20 +- plugins/frontend/agents/reviewer.md | 22 +- plugins/frontend/agents/test-architect.md | 42 +- plugins/frontend/agents/tester.md | 2 +- plugins/frontend/agents/ui-developer.md | 4 +- plugins/frontend/commands/implement-ui.md | 36 +- plugins/frontend/commands/implement.md | 198 +-- plugins/frontend/commands/import-figma.md | 8 +- plugins/frontend/commands/review.md | 38 +- .../frontend/skills/api-integration/SKILL.md | 4 +- .../frontend/skills/react-patterns/SKILL.md | 2 +- .../frontend/skills/tanstack-query/SKILL.md | 12 +- .../frontend/skills/ui-implementer/SKILL.md | 4 +- plugins/instantly/agents/campaign-analyst.md | 14 +- .../instantly/agents/outreach-optimizer.md | 12 +- plugins/instantly/agents/sequence-builder.md | 10 +- plugins/instantly/commands/ab-test.md | 6 +- plugins/instantly/commands/analytics.md | 8 +- plugins/instantly/commands/leads.md | 4 +- plugins/instantly/commands/sequence.md | 6 +- plugins/instantly/commands/start.md | 8 +- plugins/multimodel/commands/team.md | 4 +- .../skills/batching-patterns/SKILL.md | 33 +- .../skills/hierarchical-coordinator/SKILL.md | 24 +- .../skills/model-tracking-protocol/SKILL.md | 14 +- .../skills/multi-agent-coordination/SKILL.md | 14 +- .../skills/multi-model-validation/SKILL.md | 14 +- .../skills/task-orchestration/SKILL.md | 1424 +++++++++++++++++ .../skills/todowrite-orchestration/SKILL.md | 985 ------------ plugins/nanobanana/agents/image-generator.md | 6 +- plugins/nanobanana/agents/style-manager.md | 6 +- plugins/nanobanana/commands/edit.md | 4 +- plugins/nanobanana/commands/generate.md | 4 +- plugins/nanobanana/commands/style.md | 4 +- plugins/seo/agents/analyst.md | 6 +- plugins/seo/agents/data-analyst.md | 2 +- plugins/seo/agents/editor.md | 4 +- plugins/seo/agents/researcher.md | 4 +- plugins/seo/agents/writer.md | 4 +- plugins/seo/commands/alternatives.md | 16 +- plugins/seo/commands/audit.md | 4 +- plugins/seo/commands/brief.md | 4 +- plugins/seo/commands/optimize.md | 4 +- plugins/seo/commands/performance.md | 4 +- plugins/seo/commands/research.md | 10 +- plugins/seo/commands/review.md | 18 +- plugins/seo/commands/start.md | 16 +- .../video-editing/agents/timeline-builder.md | 6 +- plugins/video-editing/agents/transcriber.md | 6 +- .../video-editing/agents/video-processor.md | 6 +- .../commands/create-fcp-project.md | 6 +- plugins/video-editing/commands/transcribe.md | 6 +- plugins/video-editing/commands/video-edit.md | 6 +- 120 files changed, 2068 insertions(+), 1624 deletions(-) create mode 100644 plugins/multimodel/skills/task-orchestration/SKILL.md delete mode 100644 plugins/multimodel/skills/todowrite-orchestration/SKILL.md diff --git a/plugins/agentdev/agents/architect.md b/plugins/agentdev/agents/architect.md index c835134..cf54147 100644 --- a/plugins/agentdev/agents/architect.md +++ b/plugins/agentdev/agents/architect.md @@ -3,7 +3,7 @@ name: architect description: Expert agent designer for Claude Code agents and commands. Use when planning new agents, improving existing agents, or designing slash commands. Examples: (1) "Design a GraphQL reviewer agent" - creates comprehensive design plan. (2) "Plan improvements to backend-developer" - analyzes and designs enhancements. (3) "Design a /deploy-aws command" - creates orchestrator design. model: opus color: purple -tools: TodoWrite, Read, Write, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Glob, Grep, Bash skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestration:multi-model-validation --- @@ -16,11 +16,11 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati - Quality gates and workflow design - Tool selection and configuration - Proxy mode implementation - - TodoWrite integration patterns + - Tasks integration patterns Design comprehensive, production-ready Claude Code agents and commands - that follow XML standards, integrate TodoWrite, and support multi-model validation. + that follow XML standards, integrate Tasks, and support multi-model validation. Create detailed design documents that agent-developer can implement faithfully. @@ -100,8 +100,8 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati **If NO SESSION_PATH**: Use legacy paths (ai-docs/) - - You MUST use TodoWrite to track design workflow: + + You MUST use Tasks to track design workflow: 1. Analyze requirements and context 2. Design role and identity 3. Design instructions and workflow @@ -110,7 +110,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati 6. Design specialized sections 7. Create design document 8. Present summary - + Create design document at SESSION_PATH (if provided) or legacy location: @@ -153,7 +153,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati - Initialize TodoWrite with design phases + Initialize Tasks with design phases Read user request and extract requirements Search for similar existing agents Identify agent type (orchestrator/planner/implementer/reviewer/tester) @@ -162,7 +162,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati Design role: identity, expertise, mission - Design critical constraints (proxy mode, TodoWrite) + Design critical constraints (proxy mode, Tasks) Design core principles with priorities Design workflow phases with quality gates Design knowledge section with best practices @@ -227,7 +227,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati - [ ] Agent type identified - [ ] Role clearly defined - [ ] Critical constraints specified - - [ ] TodoWrite integrated + - [ ] Tasks integrated - [ ] Proxy mode supported (if needed) - [ ] Workflow has phases with quality gates - [ ] Knowledge section has best practices @@ -241,7 +241,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati Design an agent that reviews GraphQL schemas - 1. Initialize TodoWrite with design phases + 1. Initialize Tasks with design phases 2. Classify as Reviewer type (color: cyan) 3. Design role: GraphQL schema review expert 4. Design review criteria: schema design, security, performance @@ -254,7 +254,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati Design a /deploy-aws command for ECS deployment - 1. Initialize TodoWrite with design phases + 1. Initialize Tasks with design phases 2. Classify as Orchestrator (command) 3. Design 6 phases: pre-checks, build, push, deploy, health, rollback 4. Design delegation rules to existing agents diff --git a/plugins/agentdev/agents/developer.md b/plugins/agentdev/agents/developer.md index 5739e8c..80b0ca9 100644 --- a/plugins/agentdev/agents/developer.md +++ b/plugins/agentdev/agents/developer.md @@ -3,7 +3,7 @@ name: developer description: Expert agent implementer for Claude Code agents and commands. Use when you have an approved design plan and need to create the actual agent/command file. Examples: (1) "Implement agent from ai-docs/agent-design-graphql-reviewer.md" - creates the agent file. (2) "Create the /deploy command from design" - implements orchestrator. (3) "Fix backend-developer based on review" - applies fixes. model: sonnet color: green -tools: TodoWrite, Read, Write, Edit, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Glob, Grep, Bash skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestration:multi-model-validation --- @@ -98,8 +98,8 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati **If NO SESSION_PATH**: Use legacy paths (ai-docs/) - - You MUST use TodoWrite to track implementation: + + You MUST use Tasks to track implementation: 1. Read and analyze design plan 2. Implement frontmatter YAML 3. Implement core XML sections @@ -107,7 +107,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati 5. Validate YAML and XML 6. Write file 7. Present results - + You MUST receive a design plan before implementation. @@ -151,7 +151,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati - Initialize TodoWrite with implementation phases + Initialize Tasks with implementation phases Read design plan file Extract target file path Determine agent/command type @@ -169,7 +169,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati Implement `` (identity, expertise, mission) Implement `` (constraints, principles, workflow) Add proxy mode support if specified - Add TodoWrite requirement + Add Tasks requirement Implement `` Implement `` (2-4 scenarios) Implement `` @@ -187,7 +187,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati Check all XML tags closed and nested Verify all design sections included Check code blocks properly formatted - Verify TodoWrite integration present + Verify Tasks integration present @@ -217,8 +217,8 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati Opening ``` with language, proper indentation, closing ``` - - todowrite_requirement in constraints, workflow mentions it + + tasks_requirement in constraints, workflow mentions it All design sections implemented, no placeholders @@ -231,7 +231,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati ai-docs/agent-design-graphql-reviewer.md .claude/agents/graphql-reviewer.md - 1. TodoWrite: Create implementation phases + 1. TaskCreate: Create implementation phases 2. Read design plan 3. Frontmatter: name, description (3 examples), model: sonnet, color: cyan 4. Implement `` with GraphQL expertise @@ -246,7 +246,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati ai-docs/implementation-review-consolidated.md plugins/bun/agents/backend-developer.md - 1. TodoWrite: Create fix phases + 1. TaskCreate: Create fix phases 2. Read review feedback 3. Read current agent file 4. Identify changes needed @@ -284,7 +284,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati **Validation**: - [x] YAML syntax valid - [x] XML structure correct -- [x] TodoWrite integrated +- [x] Tasks integrated **Next Steps**: 1. Review file diff --git a/plugins/agentdev/agents/reviewer.md b/plugins/agentdev/agents/reviewer.md index 116080d..71dea13 100644 --- a/plugins/agentdev/agents/reviewer.md +++ b/plugins/agentdev/agents/reviewer.md @@ -3,7 +3,7 @@ name: reviewer description: Expert agent quality reviewer for Claude Code agents and commands. Use when validating implemented agents for quality, completeness, and standards compliance. Examples: (1) "Review .claude/agents/graphql-reviewer.md" - validates YAML, XML, completeness. (2) "Check plugins/bun/agents/backend-developer.md" - reviews against standards. (3) "Provide feedback on /deploy-aws command" - reviews orchestration patterns. model: opus color: cyan -tools: TodoWrite, Read, Write, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Glob, Grep, Bash skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestration:multi-model-validation, orchestration:quality-gates --- @@ -13,7 +13,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati - Agent/command quality validation - XML tag standards compliance - YAML frontmatter validation - - TodoWrite integration verification + - Tasks integration verification - Proxy mode implementation review - Completeness and clarity assessment - Security and safety review @@ -99,19 +99,19 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati **If NO SESSION_PATH**: Use legacy paths (ai-docs/) - - You MUST use TodoWrite to track review workflow: + + You MUST use Tasks to track review workflow: 1. Read agent/command file 2. Validate YAML frontmatter 3. Validate XML structure 4. Check completeness 5. Review examples - 6. Check TodoWrite integration + 6. Check Tasks integration 7. Review tools and config 8. Security review 9. Generate feedback 10. Present results - + - You are a REVIEWER, not IMPLEMENTER @@ -154,7 +154,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati - Initialize TodoWrite with review phases + Initialize Tasks with review phases Read agent/command file Identify agent type Create review document file @@ -186,7 +186,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati Evaluate example quality (concrete, actionable) - Check TodoWrite integration + Check Tasks integration Verify tool list matches agent type Review proxy mode if present Security and safety check @@ -216,7 +216,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati 2-4 concrete, actionable examples - + Requirement in constraints, in workflow, in examples @@ -248,7 +248,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati - Missing required sections **HIGH**: - - Missing TodoWrite integration + - Missing Tasks integration (TaskCreate, TaskUpdate, etc.) - Poor example quality - Wrong tool list for type @@ -279,7 +279,7 @@ skills: agentdev:xml-standards, agentdev:schemas, agentdev:patterns, orchestrati **Status**: FAIL CRITICAL: 2 (unclosed XML, invalid YAML) - HIGH: 4 (no TodoWrite, 1 example, wrong tools) + HIGH: 4 (no Tasks, 1 example, wrong tools) Score: 4.2/10 Recommendation: Fix critical issues before use diff --git a/plugins/agentdev/commands/develop.md b/plugins/agentdev/commands/develop.md index f58ac6c..b669cae 100644 --- a/plugins/agentdev/commands/develop.md +++ b/plugins/agentdev/commands/develop.md @@ -4,8 +4,8 @@ description: | Orchestrates design (architect) -> plan review -> implementation (developer) -> quality review (reviewer) -> iteration. Tracks model performance to ai-docs/llm-performance.json for shortlist optimization. Enable debug mode with /agentdev:debug-enable before running. -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep -skills: orchestration:multi-model-validation, orchestration:quality-gates, orchestration:todowrite-orchestration, orchestration:error-recovery, agentdev:xml-standards, agentdev:debug-mode +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep +skills: orchestration:multi-model-validation, orchestration:quality-gates, orchestration:task-orchestration, orchestration:error-recovery, agentdev:xml-standards, agentdev:debug-mode --- @@ -28,7 +28,7 @@ skills: orchestration:multi-model-validation, orchestration:quality-gates, orche **You MUST:** - Use Task tool to delegate ALL work to agents - - Use TodoWrite to track workflow + - Use Tasks to track workflow - Use AskUserQuestion for approval gates - Coordinate multi-agent workflows @@ -47,7 +47,7 @@ skills: orchestration:multi-model-validation, orchestration:quality-gates, orche - Initialize TodoWrite with all phases + Initialize Tasks with all phases Check Claudish availability for multi-model reviews @@ -57,7 +57,7 @@ skills: orchestration:multi-model-validation, orchestration:quality-gates, orche Setup workflow, validate prerequisites, initialize session - Create TodoWrite with all phases + Create task list with all phases **Dependency Check**: ```bash @@ -182,7 +182,7 @@ Review the design plan at ${SESSION_PATH}/design.md Evaluate: 1. Design completeness 2. XML/YAML structure validity -3. TodoWrite integration +3. Tasks integration 4. Proxy mode support 5. Example quality @@ -517,5 +517,5 @@ Ready to use! - User satisfied - Report generated - **Model performance tracked to ai-docs/llm-performance.json** - - All TodoWrite tasks completed + - All task tasks completed diff --git a/plugins/agentdev/commands/help.md b/plugins/agentdev/commands/help.md index 85d669b..5bf594a 100644 --- a/plugins/agentdev/commands/help.md +++ b/plugins/agentdev/commands/help.md @@ -58,7 +58,7 @@ Present the following help information to the user: | Skill | Description | |-------|-------------| | **xml-standards** | XML tag structure patterns following Anthropic best practices | -| **patterns** | Common agent patterns: proxy mode, TodoWrite integration, quality checks | +| **patterns** | Common agent patterns: proxy mode, Tasks integration, quality checks | | **schemas** | YAML frontmatter schemas for agent/command files | --- @@ -71,7 +71,7 @@ name: my-agent description: When to use this agent with examples model: sonnet # or opus, haiku color: blue -tools: TodoWrite, Read, Write, Edit, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash --- # Agent Instructions @@ -90,12 +90,12 @@ PROXY_MODE: x-ai/grok-code-fast-1 [actual task here] ``` -### TodoWrite Integration +### Tasks Integration Agents should track progress: ```markdown -1. Create todo list at start -2. Mark tasks in_progress when starting -3. Mark completed immediately when done +1. Create task list at start with TaskCreate +2. Mark tasks in_progress when starting with TaskUpdate +3. Mark completed immediately when done with TaskUpdate ``` ### Quality Checks diff --git a/plugins/agentdev/skills/patterns/SKILL.md b/plugins/agentdev/skills/patterns/SKILL.md index b4ef917..a13dce6 100644 --- a/plugins/agentdev/skills/patterns/SKILL.md +++ b/plugins/agentdev/skills/patterns/SKILL.md @@ -1,6 +1,6 @@ --- name: patterns -description: Common agent patterns and templates for Claude Code. Use when implementing agents to follow proven patterns for proxy mode, TodoWrite integration, and quality checks. +description: Common agent patterns and templates for Claude Code. Use when implementing agents to follow proven patterns for proxy mode, Tasks integration, and quality checks. --- plugin: agentdev updated: 2026-01-20 @@ -59,16 +59,16 @@ Enable agents to delegate to external AI models via Claudish. --- -## TodoWrite Integration Pattern +## Tasks Integration Pattern Every agent must track workflow progress. ```xml - - You MUST use TodoWrite to track your workflow. + + You MUST use Tasks to track your workflow. - **Before starting**, create todo list: + **Before starting**, create task list: 1. Phase 1 description 2. Phase 2 description 3. Phase 3 description @@ -77,12 +77,12 @@ Every agent must track workflow progress. - Mark "in_progress" when starting - Mark "completed" immediately after finishing - Keep only ONE task "in_progress" at a time - + - Initialize TodoWrite with all phases + Initialize Tasks with all phases Mark PHASE 1 as in_progress ... perform work ... Mark PHASE 1 as completed @@ -195,7 +195,7 @@ Every agent must track workflow progress. Clear statement of what this phase achieves - Mark PHASE 1 as in_progress in TodoWrite + Mark PHASE 1 as in_progress in task list Detailed action step Detailed action step Mark PHASE 1 as completed @@ -227,7 +227,7 @@ description: | Examples: (1) "Design X" (2) "Plan Y" (3) "Architect Z" model: sonnet color: purple -tools: TodoWrite, Read, Write, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Glob, Grep, Bash --- ``` @@ -240,7 +240,7 @@ description: | Examples: (1) "Create X" (2) "Build Y" (3) "Implement Z" model: sonnet color: green -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep --- ``` @@ -253,7 +253,7 @@ description: | Examples: (1) "Review X" (2) "Validate Y" (3) "Check Z" model: sonnet color: cyan -tools: TodoWrite, Read, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Glob, Grep, Bash --- ``` @@ -263,6 +263,6 @@ tools: TodoWrite, Read, Glob, Grep, Bash description: | Orchestrates {workflow} with multi-agent coordination. Workflow: PHASE 1 → PHASE 2 → PHASE 3 -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- ``` diff --git a/plugins/agentdev/skills/schemas/SKILL.md b/plugins/agentdev/skills/schemas/SKILL.md index fc08949..9f5c59b 100644 --- a/plugins/agentdev/skills/schemas/SKILL.md +++ b/plugins/agentdev/skills/schemas/SKILL.md @@ -19,7 +19,7 @@ description: | # Required: detailed with examples (3) "Task description" - launches agent for Z model: sonnet # Required: sonnet | opus | haiku color: purple # Optional: purple | cyan | green | orange | blue | red -tools: TodoWrite, Read, Write # Required: comma-separated, space after comma +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write # Required: comma-separated, space after comma skills: skill1, skill2 # Optional: referenced skills --- ``` @@ -49,20 +49,20 @@ skills: skill1, skill2 # Optional: referenced skills ### Tool Patterns by Agent Type **Orchestrators (Commands):** -- Must have: `Task`, `TodoWrite`, `Read`, `Bash` +- Must have: `Task`, `TaskCreate, TaskUpdate, TaskList, TaskGet`, `Read`, `Bash` - Often: `AskUserQuestion`, `Glob`, `Grep` - Never: `Write`, `Edit` **Planners:** -- Must have: `TodoWrite`, `Read`, `Write` (for docs) +- Must have: `TaskCreate, TaskUpdate, TaskList, TaskGet`, `Read`, `Write` (for docs) - Often: `Glob`, `Grep`, `Bash` **Implementers:** -- Must have: `TodoWrite`, `Read`, `Write`, `Edit` +- Must have: `TaskCreate, TaskUpdate, TaskList, TaskGet`, `Read`, `Write`, `Edit` - Often: `Bash`, `Glob`, `Grep` **Reviewers:** -- Must have: `TodoWrite`, `Read` +- Must have: `TaskCreate, TaskUpdate, TaskList, TaskGet`, `Read` - Often: `Glob`, `Grep`, `Bash` - Never: `Write`, `Edit` @@ -104,7 +104,7 @@ skills: skill1, skill2 # Optional: referenced skills ### Command Frontmatter - [ ] Opening `---` present - [ ] `description` explains workflow -- [ ] `allowed-tools` includes Task for orchestrators +- [ ] `allowed-tools` includes Task, TaskCreate, TaskUpdate, TaskList, TaskGet for orchestrators - [ ] Closing `---` present - [ ] No YAML syntax errors @@ -124,10 +124,10 @@ name: agent-name ### Incorrect Tool Format ```yaml # WRONG - no spaces after commas -tools: TodoWrite,Read,Write +tools: TaskCreate, TaskUpdate, TaskList, TaskGet,Read,Write # CORRECT -tools: TodoWrite, Read, Write +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write ``` ### Missing Examples diff --git a/plugins/agentdev/skills/xml-standards/SKILL.md b/plugins/agentdev/skills/xml-standards/SKILL.md index f5f7dab..4771b34 100644 --- a/plugins/agentdev/skills/xml-standards/SKILL.md +++ b/plugins/agentdev/skills/xml-standards/SKILL.md @@ -36,7 +36,7 @@ Defines behavior constraints and workflow. Description of critical rule that must be followed - You MUST use TodoWrite to track workflow progress. + You MUST use Tasks to track workflow progress. @@ -110,7 +110,7 @@ Communication style and output format. ```xml - Task, Bash, Read, TodoWrite, AskUserQuestion + Task, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion Write, Edit diff --git a/plugins/autopilot/agents/task-executor.md b/plugins/autopilot/agents/task-executor.md index 7c3b7bf..11ab3e7 100644 --- a/plugins/autopilot/agents/task-executor.md +++ b/plugins/autopilot/agents/task-executor.md @@ -3,7 +3,7 @@ name: task-executor description: Main agent that executes picked-up Linear tasks using ReAct pattern model: sonnet color: blue -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep, Task +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep, Task skills: dev:universal-patterns, dev:context-detection, autopilot:state-machine --- diff --git a/plugins/autopilot/commands/create-task.md b/plugins/autopilot/commands/create-task.md index 9b28557..422c703 100644 --- a/plugins/autopilot/commands/create-task.md +++ b/plugins/autopilot/commands/create-task.md @@ -1,6 +1,6 @@ --- description: Create a Linear task from CLI and assign to autopilot for execution -allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TodoWrite +allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet skills: autopilot:linear-integration, autopilot:tag-command-mapping --- @@ -25,7 +25,7 @@ skills: autopilot:linear-integration, autopilot:tag-command-mapping - You MUST use TodoWrite to track task creation workflow: + You MUST use Tasks to track task creation workflow: 1. Parse user request 2. Classify task type 3. Generate acceptance criteria diff --git a/plugins/autopilot/commands/run.md b/plugins/autopilot/commands/run.md index bfc9e34..b630e5c 100644 --- a/plugins/autopilot/commands/run.md +++ b/plugins/autopilot/commands/run.md @@ -1,6 +1,6 @@ --- description: Manually trigger execution of a specific Linear task -allowed-tools: Task, Bash, Read, Write, TodoWrite, AskUserQuestion +allowed-tools: Task, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion skills: autopilot:linear-integration, autopilot:tag-command-mapping, autopilot:state-machine, autopilot:proof-of-work --- @@ -30,7 +30,7 @@ skills: autopilot:linear-integration, autopilot:tag-command-mapping, autopilot:s **You MUST:** - Use Task tool to delegate to task-executor agent - - Track progress via TodoWrite + - Track progress via Tasks - Enforce state transitions - Generate proof artifacts @@ -191,7 +191,7 @@ skills: autopilot:linear-integration, autopilot:tag-command-mapping, autopilot:s Present execution summary - Mark all TodoWrite tasks completed + Mark all task items completed diff --git a/plugins/autopilot/commands/status.md b/plugins/autopilot/commands/status.md index 24957e6..0afaa53 100644 --- a/plugins/autopilot/commands/status.md +++ b/plugins/autopilot/commands/status.md @@ -1,6 +1,6 @@ --- description: Check autopilot status, queue, and task progress -allowed-tools: Bash, Read, AskUserQuestion, TodoWrite +allowed-tools: Bash, Read, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, TaskGet skills: autopilot:linear-integration, autopilot:state-machine --- diff --git a/plugins/bun/ARCHITECTURE.md b/plugins/bun/ARCHITECTURE.md index 86d33be..ef81d9b 100644 --- a/plugins/bun/ARCHITECTURE.md +++ b/plugins/bun/ARCHITECTURE.md @@ -177,7 +177,7 @@ INPUT: Architecture plan (from ai-docs/) ├─> PHASE 1: Analysis │ • Reads existing patterns │ • Identifies required layers - │ • Creates TodoWrite task list + │ • Creates task list │ ├─> PHASE 2: Database layer │ • Updates Prisma schema @@ -388,7 +388,7 @@ USER: /implement-api Create user management API │ • Detect frontend plugin (for code review) │ • Inform user of benefits │ - ├─> STEP 0: Initialize TodoWrite + ├─> STEP 0: Initialize Tasks │ • PHASE 1: Architecture planning │ • PHASE 1: User approval gate │ • PHASE 2: Implementation @@ -1268,9 +1268,9 @@ For implementation only (plan exists): @backend-developer ``` -### 2. Always Use TodoWrite +### 2. Always Use Tasks -All agents and commands use TodoWrite. You'll see: +All agents and commands use Tasks. You'll see: - Task lists during execution - Progress tracking - Clear completion status diff --git a/plugins/bun/agents/api-architect.md b/plugins/bun/agents/api-architect.md index f339473..9b00376 100644 --- a/plugins/bun/agents/api-architect.md +++ b/plugins/bun/agents/api-architect.md @@ -11,8 +11,8 @@ You are an elite Backend API Architecture Specialist with deep expertise in mode You architect backend APIs by creating comprehensive, step-by-step implementation plans. You do NOT write implementation code directly - instead, you create detailed architectural blueprints and actionable plans that other agents (like backend-developer) or developers will follow. -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to create and maintain a todo list throughout your planning workflow. This provides visibility and ensures systematic completion of all planning phases. +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to create and maintain a todo list throughout your planning workflow. This provides visibility and ensures systematic completion of all planning phases. ## Your Expertise Areas @@ -33,10 +33,10 @@ You MUST use the TodoWrite tool to create and maintain a todo list throughout yo ### STEP 0: Initialize Todo List (MANDATORY FIRST STEP) -Before starting any planning work, you MUST create a todo list using the TodoWrite tool: +Before starting any planning work, you MUST create a task list using the Tasks system: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "Perform gap analysis and ask clarifying questions" status: "in_progress" activeForm: "Performing gap analysis and asking clarifying questions" diff --git a/plugins/bun/agents/apidog.md b/plugins/bun/agents/apidog.md index 21a2b02..207dd64 100644 --- a/plugins/bun/agents/apidog.md +++ b/plugins/bun/agents/apidog.md @@ -36,17 +36,17 @@ You synchronize API specifications with Apidog by: 4. Importing specs to Apidog 5. Providing validation URLs -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to create and maintain a todo list throughout your workflow. This provides visibility and ensures systematic completion of all synchronization phases. +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to create and maintain a todo list throughout your workflow. This provides visibility and ensures systematic completion of all synchronization phases. ## Your Workflow Process ### STEP 0: Initialize Todo List (MANDATORY FIRST STEP) -Before starting any work, you MUST create a todo list using the TodoWrite tool: +Before starting any work, you MUST create a task list using the Tasks system: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "Verify APIDOG_PROJECT_ID environment variable" status: "in_progress" activeForm: "Verifying APIDOG_PROJECT_ID environment variable" diff --git a/plugins/bun/agents/backend-developer.md b/plugins/bun/agents/backend-developer.md index 191242a..62ec587 100644 --- a/plugins/bun/agents/backend-developer.md +++ b/plugins/bun/agents/backend-developer.md @@ -19,10 +19,10 @@ You are an expert TypeScript backend developer specializing in building producti ## Core Development Principles -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to create and maintain a todo list throughout your implementation workflow. This provides visibility into your progress and ensures systematic completion of all implementation tasks. +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to create and maintain a todo list throughout your implementation workflow. This provides visibility into your progress and ensures systematic completion of all implementation tasks. -**Before starting any implementation**, create a todo list that includes: +**Before starting any implementation**, create a task list that includes: 1. All features/tasks from the provided documentation or plan 2. Implementation tasks (routes, controllers, services, repositories) 3. Quality check tasks (formatting, linting, type checking, testing) @@ -244,27 +244,27 @@ model User { Before presenting any code, you MUST perform these checks in order: 1. **Code Formatting**: Run Biome.js formatter on all modified files - - Add to TodoWrite: "Run Biome.js formatter on modified files" + - TaskCreate: "Run Biome.js formatter on modified files" - Command: `bun run format` or `biome format --write` - Mark as completed after running successfully 2. **Linting**: Run Biome.js linter and fix all errors and warnings - - Add to TodoWrite: "Run Biome.js linter and fix all errors" + - TaskCreate: "Run Biome.js linter and fix all errors" - Command: `bun run lint` or `biome lint --write` - Mark as completed after all issues are resolved 3. **Type Checking**: Run TypeScript compiler and resolve all type errors - - Add to TodoWrite: "Run TypeScript type checking and fix errors" + - TaskCreate: "Run TypeScript type checking and fix errors" - Command: `bun run typecheck` or `tsc --noEmit` - Mark as completed after all type errors are resolved 4. **Testing**: Run relevant tests with Bun's test runner - - Add to TodoWrite: "Run Bun tests for modified areas" + - TaskCreate: "Run Bun tests for modified areas" - Command: `bun test` (optionally with file pattern) - Mark as completed after all tests pass 5. **Prisma Client**: Generate Prisma client if schema changed - - Add to TodoWrite: "Generate Prisma client" + - TaskCreate: "Generate Prisma client" - Command: `bunx prisma generate` - Mark as completed after generation succeeds @@ -278,7 +278,7 @@ For each feature implementation, follow this workflow: 1. Read existing codebase to understand patterns 2. Identify required layers (routes, controllers, services, repositories) 3. Check for existing utilities/middleware to reuse -4. Create comprehensive todo list with TodoWrite +4. Create comprehensive todo list with Tasks ### Phase 2: Database Layer (if needed) 1. Update Prisma schema if new models needed diff --git a/plugins/bun/commands/implement-api.md b/plugins/bun/commands/implement-api.md index 6d6d351..c1677b0 100644 --- a/plugins/bun/commands/implement-api.md +++ b/plugins/bun/commands/implement-api.md @@ -1,6 +1,6 @@ --- description: Full-cycle API implementation with multi-agent orchestration, architecture planning, implementation, testing, and quality gates -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- ## Mission @@ -15,7 +15,7 @@ Orchestrate a complete API feature implementation workflow using specialized age - Use Task tool to delegate ALL implementation work to agents - Use Bash to run git commands (status, diff, log) - Use Read/Glob/Grep to understand context -- Use TodoWrite to track workflow progress +- Use Tasks to track workflow progress - Use AskUserQuestion for user approval gates - Coordinate agent workflows and feedback loops @@ -82,10 +82,10 @@ architecture planning to investigate existing patterns and find the best integra ### STEP 0: Initialize Global Workflow Todo List (MANDATORY FIRST STEP) -**BEFORE** starting any phase, you MUST create a global workflow todo list using TodoWrite to track the entire implementation lifecycle: +**BEFORE** starting any phase, you MUST create a global workflow todo list using Tasks to track the entire implementation lifecycle: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "PHASE 1: Launch api-architect for API architecture planning" status: "in_progress" activeForm: "PHASE 1: Launching api-architect for API architecture planning" diff --git a/plugins/bun/commands/setup-project.md b/plugins/bun/commands/setup-project.md index 803339f..63511dd 100644 --- a/plugins/bun/commands/setup-project.md +++ b/plugins/bun/commands/setup-project.md @@ -1,6 +1,6 @@ --- description: Initialize a new Bun + TypeScript backend project with best practices setup (Hono, Prisma, Biome, testing, Docker) -allowed-tools: Bash, Write, AskUserQuestion, TodoWrite, Read +allowed-tools: Bash, Write, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, TaskGet, Read --- ## Mission @@ -18,7 +18,7 @@ $ARGUMENTS Create a todo list to track the setup process: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "Gather project requirements and configuration preferences" status: "in_progress" activeForm: "Gathering project requirements" diff --git a/plugins/code-analysis/commands/analyze.md b/plugins/code-analysis/commands/analyze.md index 5e020a3..2a1799e 100644 --- a/plugins/code-analysis/commands/analyze.md +++ b/plugins/code-analysis/commands/analyze.md @@ -1,6 +1,6 @@ --- description: Deep codebase investigation to understand architecture, trace functionality, find implementations, and analyze code patterns -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- ## Mission diff --git a/plugins/conductor/README.md b/plugins/conductor/README.md index 8767b94..6c008ff 100644 --- a/plugins/conductor/README.md +++ b/plugins/conductor/README.md @@ -203,7 +203,7 @@ Task: 2.1 (Implement password hashing) ## Integration with Other Plugins Conductor works alongside: -- **orchestration plugin:** Leverages todowrite-orchestration, quality-gates +- **orchestration plugin:** Leverages task-orchestration, quality-gates - **frontend plugin:** Can manage frontend development workflows - **bun plugin:** Can manage backend development workflows diff --git a/plugins/conductor/commands/help.md b/plugins/conductor/commands/help.md index 275ad84..9752564 100644 --- a/plugins/conductor/commands/help.md +++ b/plugins/conductor/commands/help.md @@ -23,10 +23,10 @@ allowed-tools: Read, Glob - + Simple informational command. - TodoWrite is NOT required. - + Tasks are NOT required. + This command ONLY displays information. diff --git a/plugins/conductor/commands/implement.md b/plugins/conductor/commands/implement.md index a4b73b9..cfc35af 100644 --- a/plugins/conductor/commands/implement.md +++ b/plugins/conductor/commands/implement.md @@ -1,6 +1,6 @@ --- description: Execute tasks from track plan with TDD workflow and git commits -allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TodoWrite, Glob, Grep +allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- @@ -28,11 +28,11 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TodoWrite, Glob, Grep - - Use TodoWrite to mirror plan.md tasks. - Keep TodoWrite and plan.md in sync. + + Use Tasks to mirror plan.md tasks. + Keep Tasks and plan.md in sync. Mark tasks in BOTH when status changes. - + Task status MUST follow this progression: @@ -153,13 +153,13 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TodoWrite, Glob, Grep Ask which track to work on (if multiple active) Load track's spec.md and plan.md Load conductor/workflow.md for procedures - Initialize TodoWrite from plan.md tasks + Initialize Tasks from plan.md tasks Find first pending task (or ask user) Mark task as [~] in_progress in plan.md - Update TodoWrite to match + TaskUpdate to match Read task requirements and context @@ -182,7 +182,7 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TodoWrite, Glob, Grep Mark task as [x] complete in plan.md Commit plan.md update separately Update metadata.json with commit info - Update TodoWrite to match + TaskUpdate to match @@ -329,7 +329,7 @@ Why: {business reason for this change} 1. Load feature_auth_20260105 track 2. Read plan.md - find first pending task: 1.1 Create user table 3. Mark 1.1 as [~] in plan.md - 4. Initialize TodoWrite with plan tasks + 4. Initialize Tasks with plan tasks **Red Phase:** 5. Create test file: tests/user-table.test.ts diff --git a/plugins/conductor/commands/new-track.md b/plugins/conductor/commands/new-track.md index f807daa..2faf57c 100644 --- a/plugins/conductor/commands/new-track.md +++ b/plugins/conductor/commands/new-track.md @@ -1,6 +1,6 @@ --- description: Create development track with spec and hierarchical task plan -allowed-tools: AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep +allowed-tools: AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- @@ -25,7 +25,7 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep - You MUST use TodoWrite to track planning progress: + You MUST use Tasks to track planning progress: 1. Validate conductor setup exists 2. Gather track requirements 3. Generate track ID @@ -82,7 +82,7 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep Check conductor/ directory exists Check required files: product.md, tech-stack.md, workflow.md If missing, HALT with guidance to run setup - Initialize TodoWrite + Initialize Tasks diff --git a/plugins/conductor/commands/revert.md b/plugins/conductor/commands/revert.md index 31a2f45..10dda4b 100644 --- a/plugins/conductor/commands/revert.md +++ b/plugins/conductor/commands/revert.md @@ -1,6 +1,6 @@ --- description: Git-aware logical undo at track, phase, or task level -allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TodoWrite, Glob, Grep +allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- @@ -25,7 +25,7 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, Edit, TodoWrite, Glob, Grep - You MUST use TodoWrite to track the revert workflow. + You MUST use Tasks to track the revert workflow. **Before starting**, create todo list with these 5 phases: 1. Scope Selection - Identify what to revert (track/phase/task) diff --git a/plugins/conductor/commands/setup.md b/plugins/conductor/commands/setup.md index b97c20d..485800b 100644 --- a/plugins/conductor/commands/setup.md +++ b/plugins/conductor/commands/setup.md @@ -1,6 +1,6 @@ --- description: Initialize Conductor with interactive Q&A to create project context files -allowed-tools: AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep +allowed-tools: AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- @@ -25,7 +25,7 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep - You MUST use TodoWrite to track setup progress: + You MUST use Tasks to track setup progress: 1. Check for existing conductor/ directory 2. Determine project type (Greenfield/Brownfield) 3. Create product.md through Q&A @@ -82,7 +82,7 @@ allowed-tools: AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep Check if conductor/ directory exists If exists, check setup_state.json for resume If complete setup exists, confirm re-initialization - Initialize TodoWrite with setup phases + Initialize Tasks with setup phases diff --git a/plugins/conductor/commands/status.md b/plugins/conductor/commands/status.md index d227eb9..16034fb 100644 --- a/plugins/conductor/commands/status.md +++ b/plugins/conductor/commands/status.md @@ -23,11 +23,11 @@ allowed-tools: Bash, Read, Glob, Grep - + This is a read-only command that only displays status. - TodoWrite is NOT required because there are no implementation phases. + Tasks are NOT required because there are no implementation phases. The command performs a single atomic operation: read and present status. - + This command ONLY reads files. diff --git a/plugins/conductor/skills/implement/SKILL.md b/plugins/conductor/skills/implement/SKILL.md index 647da8a..2aec3f7 100644 --- a/plugins/conductor/skills/implement/SKILL.md +++ b/plugins/conductor/skills/implement/SKILL.md @@ -30,8 +30,8 @@ updated: 2026-01-20 - Use TodoWrite to mirror plan.md tasks. - Keep TodoWrite and plan.md in sync. + Use Tasks to mirror plan.md tasks. + Keep Tasks and plan.md in sync. Mark tasks in BOTH when status changes. @@ -154,13 +154,13 @@ updated: 2026-01-20 Ask which track to work on (if multiple active) Load track's spec.md and plan.md Load conductor/workflow.md for procedures - Initialize TodoWrite from plan.md tasks + Initialize Tasks from plan.md tasks Find first pending task (or ask user) Mark task as [~] in_progress in plan.md - Update TodoWrite to match + TaskUpdate to match Read task requirements and context @@ -183,7 +183,7 @@ updated: 2026-01-20 Mark task as [x] complete in plan.md Commit plan.md update separately Update metadata.json with commit info - Update TodoWrite to match + TaskUpdate to match @@ -330,7 +330,7 @@ Why: {business reason for this change} 1. Load feature_auth_20260105 track 2. Read plan.md - find first pending task: 1.1 Create user table 3. Mark 1.1 as [~] in plan.md - 4. Initialize TodoWrite with plan tasks + 4. Initialize Tasks with plan tasks **Red Phase:** 5. Create test file: tests/user-table.test.ts diff --git a/plugins/conductor/skills/new-track/SKILL.md b/plugins/conductor/skills/new-track/SKILL.md index 59d5d13..483eb95 100644 --- a/plugins/conductor/skills/new-track/SKILL.md +++ b/plugins/conductor/skills/new-track/SKILL.md @@ -26,7 +26,7 @@ updated: 2026-01-20 - You MUST use TodoWrite to track planning progress: + You MUST use Tasks to track planning progress: 1. Validate conductor setup exists 2. Gather track requirements 3. Generate track ID @@ -83,7 +83,7 @@ updated: 2026-01-20 Check conductor/ directory exists Check required files: product.md, tech-stack.md, workflow.md If missing, HALT with guidance to run setup - Initialize TodoWrite + Initialize Tasks diff --git a/plugins/conductor/skills/revert/SKILL.md b/plugins/conductor/skills/revert/SKILL.md index 3ca1428..47c8993 100644 --- a/plugins/conductor/skills/revert/SKILL.md +++ b/plugins/conductor/skills/revert/SKILL.md @@ -26,7 +26,7 @@ updated: 2026-01-20 - You MUST use TodoWrite to track the revert workflow. + You MUST use Tasks to track the revert workflow. **Before starting**, create todo list with these 5 phases: 1. Scope Selection - Identify what to revert (track/phase/task) diff --git a/plugins/conductor/skills/setup/SKILL.md b/plugins/conductor/skills/setup/SKILL.md index 4f4b3c4..356028d 100644 --- a/plugins/conductor/skills/setup/SKILL.md +++ b/plugins/conductor/skills/setup/SKILL.md @@ -26,7 +26,7 @@ updated: 2026-01-20 - You MUST use TodoWrite to track setup progress: + You MUST use Tasks to track setup progress: 1. Check for existing conductor/ directory 2. Determine project type (Greenfield/Brownfield) 3. Create product.md through Q&A @@ -83,7 +83,7 @@ updated: 2026-01-20 Check if conductor/ directory exists If exists, check setup_state.json for resume If complete setup exists, confirm re-initialization - Initialize TodoWrite with setup phases + Initialize Tasks with setup phases diff --git a/plugins/conductor/skills/status/SKILL.md b/plugins/conductor/skills/status/SKILL.md index 8ed1864..d2a728b 100644 --- a/plugins/conductor/skills/status/SKILL.md +++ b/plugins/conductor/skills/status/SKILL.md @@ -24,11 +24,11 @@ updated: 2026-01-20 - + This is a read-only skill that only displays status. - TodoWrite is NOT required because there are no implementation phases. + Tasks are NOT required because there are no implementation phases. The skill performs a single atomic operation: read and present status. - + This skill ONLY reads files. diff --git a/plugins/dev/agents/architect.md b/plugins/dev/agents/architect.md index 34e1668..99bb6bf 100644 --- a/plugins/dev/agents/architect.md +++ b/plugins/dev/agents/architect.md @@ -3,7 +3,7 @@ name: architect description: Language-agnostic architecture planning for system design and trade-off analysis model: sonnet color: purple -tools: TodoWrite, Read, Write, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, Glob, Grep skills: dev:universal-patterns --- @@ -25,7 +25,7 @@ skills: dev:universal-patterns - You MUST use TodoWrite to track architecture workflow. + You MUST use Tasks to track architecture workflow. Before starting, create todo list: 1. Read skills and understand requirements diff --git a/plugins/dev/agents/debugger.md b/plugins/dev/agents/debugger.md index 68df397..a1c3570 100644 --- a/plugins/dev/agents/debugger.md +++ b/plugins/dev/agents/debugger.md @@ -3,7 +3,7 @@ name: debugger description: Language-agnostic debugging for error analysis and root cause investigation model: sonnet color: orange -tools: TodoWrite, Read, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Glob, Grep, Bash skills: dev:debugging-strategies --- @@ -25,7 +25,7 @@ skills: dev:debugging-strategies - You MUST use TodoWrite to track debugging workflow. + You MUST use Tasks to track debugging workflow. Before starting, create todo list: 1. Parse error message diff --git a/plugins/dev/agents/developer.md b/plugins/dev/agents/developer.md index 72b9734..fe57e08 100644 --- a/plugins/dev/agents/developer.md +++ b/plugins/dev/agents/developer.md @@ -3,7 +3,7 @@ name: developer description: Language-agnostic implementation agent that adapts to any technology stack model: sonnet color: green -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep skills: dev:universal-patterns --- @@ -25,7 +25,7 @@ skills: dev:universal-patterns - You MUST use TodoWrite to track implementation workflow. + You MUST use Tasks to track implementation workflow. Before starting, create todo list: 1. Load and analyze skills @@ -309,7 +309,7 @@ skills: dev:universal-patterns - Be precise about files created/modified - - Show progress through TodoWrite + - Show progress through Tasks - Report quality check results clearly - Explain any deviations from skills (with reason) - Provide file paths and line counts diff --git a/plugins/dev/agents/devops.md b/plugins/dev/agents/devops.md index 308e880..7ac6b95 100644 --- a/plugins/dev/agents/devops.md +++ b/plugins/dev/agents/devops.md @@ -3,7 +3,7 @@ name: devops description: Infrastructure and DevOps specialist with extended thinking for complex decisions model: opus color: blue -tools: TodoWrite, Read, Write, Bash, WebSearch, WebFetch, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, WebSearch, WebFetch, Glob, Grep skills: dev:bunjs-production --- @@ -66,7 +66,7 @@ skills: dev:bunjs-production - You MUST use TodoWrite to track infrastructure workflow: + You MUST use Tasks to track infrastructure workflow: 1. Analyze requirements 2. Research best practices (WebSearch) 3. Design architecture diff --git a/plugins/dev/agents/doc-analyzer.md b/plugins/dev/agents/doc-analyzer.md index a65e363..26aa3fa 100644 --- a/plugins/dev/agents/doc-analyzer.md +++ b/plugins/dev/agents/doc-analyzer.md @@ -40,7 +40,7 @@ skills: The orchestrator (/dev:doc) owns the todo list exclusively. Report your progress via your return message only. - Your internal workflow (not tracked in TodoWrite): + Your internal workflow (not tracked in task list): 1. Read documentation to analyze 2. Read source code for verification 3. Score content quality diff --git a/plugins/dev/agents/doc-fixer.md b/plugins/dev/agents/doc-fixer.md index 39c73d0..a1c0d5a 100644 --- a/plugins/dev/agents/doc-fixer.md +++ b/plugins/dev/agents/doc-fixer.md @@ -42,7 +42,7 @@ skills: The orchestrator (/dev:doc) owns the todo list exclusively. Report your progress via your return message only. - Your internal workflow (not tracked in TodoWrite): + Your internal workflow (not tracked in task list): 1. Read analysis report 2. Prioritize issues by severity 3. Apply structural fixes diff --git a/plugins/dev/agents/doc-writer.md b/plugins/dev/agents/doc-writer.md index b0de322..a8d7eb4 100644 --- a/plugins/dev/agents/doc-writer.md +++ b/plugins/dev/agents/doc-writer.md @@ -42,7 +42,7 @@ skills: The orchestrator (/dev:doc) owns the todo list exclusively. Report your progress via your return message only. - Your internal workflow (not tracked in TodoWrite): + Your internal workflow (not tracked in task list): 1. Read context and requirements 2. Select appropriate template 3. Generate documentation diff --git a/plugins/dev/agents/researcher.md b/plugins/dev/agents/researcher.md index 0a71acd..20ddfc3 100644 --- a/plugins/dev/agents/researcher.md +++ b/plugins/dev/agents/researcher.md @@ -3,7 +3,7 @@ name: researcher description: Deep research agent for web exploration and local investigation model: sonnet color: blue -tools: TodoWrite, Read, Write, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, Glob, Grep skills: dev:universal-patterns --- @@ -27,7 +27,7 @@ skills: dev:universal-patterns - You MUST use TodoWrite to track research workflow. + You MUST use Tasks to track research workflow. Before starting, create todo list: 1. Understand research sub-question @@ -477,7 +477,7 @@ skills: dev:universal-patterns Return brief summary - 1. Initialize TodoWrite with 6 phases + 1. Initialize Tasks with 6 phases 2. Extract SESSION_PATH, sub-question, queries 3. Note MODEL_STRATEGY=gemini-direct (web search available) 4. Execute each search query via web search @@ -507,7 +507,7 @@ skills: dev:universal-patterns Return brief summary - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Note MODEL_STRATEGY=native (no web search) 3. Use Glob to find MCP-related files: Glob("**/*mcp*/**/*") diff --git a/plugins/dev/agents/stack-detector.md b/plugins/dev/agents/stack-detector.md index 11d35cd..f49b889 100644 --- a/plugins/dev/agents/stack-detector.md +++ b/plugins/dev/agents/stack-detector.md @@ -3,7 +3,7 @@ name: stack-detector description: Analyzes project to detect technology stack and recommend skills model: sonnet color: blue -tools: TodoWrite, Read, Write, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Glob, Grep, Bash --- @@ -25,7 +25,7 @@ tools: TodoWrite, Read, Write, Glob, Grep, Bash - You MUST use TodoWrite to track detection workflow. + You MUST use Tasks to track detection workflow. Before starting, create todo list: 1. Scan config files @@ -97,7 +97,7 @@ tools: TodoWrite, Read, Write, Glob, Grep, Bash - Create TodoWrite with all detection phases + Create task list with all detection phases Mark PHASE 1 as in_progress Identify current working directory Mark PHASE 1 as completed diff --git a/plugins/dev/agents/synthesizer.md b/plugins/dev/agents/synthesizer.md index 4484397..ced0c9c 100644 --- a/plugins/dev/agents/synthesizer.md +++ b/plugins/dev/agents/synthesizer.md @@ -3,7 +3,7 @@ name: synthesizer description: Research synthesis for consolidating multi-source findings with consensus detection model: sonnet color: cyan -tools: TodoWrite, Read, Write, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Glob, Grep skills: dev:universal-patterns --- @@ -27,7 +27,7 @@ skills: dev:universal-patterns - You MUST use TodoWrite to track synthesis workflow. + You MUST use Tasks to track synthesis workflow. Before starting, create todo list: 1. Read all findings files @@ -569,7 +569,7 @@ skills: dev:universal-patterns Return brief summary - 1. Initialize TodoWrite with 7 phases + 1. Initialize Tasks with 7 phases 2. Use Glob to find findings files 3. Read all three explorer findings 4. Extract findings from each: @@ -603,7 +603,7 @@ skills: dev:universal-patterns Save to: ai-docs/sessions/dev-research-graphql-20260106/report.md - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Read research plan (original questions) 3. Read all synthesis iterations (iteration-1.md, iteration-2.md) 4. Read all findings files (context) @@ -631,7 +631,7 @@ skills: dev:universal-patterns Save to: ai-docs/sessions/dev-research-redis-20260106/synthesis/iteration-3.md - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Read current findings 3. Read iteration-1.md (previous synthesis) 4. Read iteration-2.md (previous synthesis) diff --git a/plugins/dev/agents/test-architect.md b/plugins/dev/agents/test-architect.md index 89fb1fa..081ee59 100644 --- a/plugins/dev/agents/test-architect.md +++ b/plugins/dev/agents/test-architect.md @@ -3,7 +3,7 @@ name: test-architect description: Black box test architect that creates tests from requirements only model: sonnet color: orange -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep --- @@ -51,7 +51,7 @@ tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep - You MUST use TodoWrite to track test development workflow. + You MUST use Tasks to track test development workflow. Before starting, create todo list: 1. Read and analyze requirements diff --git a/plugins/dev/agents/ui-engineer.md b/plugins/dev/agents/ui-engineer.md index 681238b..990f881 100644 --- a/plugins/dev/agents/ui-engineer.md +++ b/plugins/dev/agents/ui-engineer.md @@ -7,7 +7,10 @@ description: | model: sonnet color: magenta tools: - - TodoWrite + - TaskCreate + - TaskUpdate + - TaskList + - TaskGet - Read - Write - Edit @@ -59,7 +62,7 @@ skills: - You MUST use TodoWrite to track component generation workflow. + You MUST use Tasks to track component generation workflow. Before starting, create todo list with these EXACT 8 items (including Phase 0 for vision): 0. Acquire visual context (NEW - if screenshot/review provided) @@ -509,7 +512,7 @@ skills: Gather visual understanding before implementation - Mark PHASE 0 as in_progress via TodoWrite + Mark PHASE 0 as in_progress via Tasks Detect Gemini provider availability using provider_detection logic IF visual mode available: - Load screenshot/reference images if provided @@ -529,7 +532,7 @@ skills: Define the unique design direction before coding - Mark PHASE 1 as in_progress via TodoWrite + Mark PHASE 1 as in_progress via Tasks Analyze user request (component type, context, mood) Select or create a visual metaphor: - If user specified style: Use that metaphor @@ -1449,7 +1452,7 @@ skills: - Asymmetric layout creates visual interest - Custom chart styling (no default library look) - **TodoWrite would track**: + **Tasks would track**: 1. Conceptualize visual metaphor - in_progress 2. Design component structure - pending 3. Implement base component - pending diff --git a/plugins/dev/agents/ui.md b/plugins/dev/agents/ui.md index ecf2b06..f7b3e36 100644 --- a/plugins/dev/agents/ui.md +++ b/plugins/dev/agents/ui.md @@ -3,7 +3,7 @@ name: ui description: UI design review, usability analysis, accessibility checks, and Figma implementation help model: sonnet color: cyan -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep skills: - dev:ui-analyse - dev:design-references @@ -214,7 +214,7 @@ skills: - You MUST use TodoWrite to track design review workflow: + You MUST use Tasks to track design review workflow: 1. Input Validation and Figma Detection 2. Design Source Setup 3. Visual Analysis @@ -359,7 +359,7 @@ skills: - Initialize TodoWrite with review phases + Initialize Tasks with review phases **NEW**: Scan prompt for Figma URLs using regex pattern **NEW**: If Figma URL found, extract fileKey, fileName, nodeId **NEW**: Check if Figma MCP tools are available diff --git a/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/design.md b/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/design.md index 9109b2b..50f2907 100644 --- a/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/design.md +++ b/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/design.md @@ -31,7 +31,7 @@ description: | Complete feature development lifecycle with multi-agent orchestration. Workflow: DETECT -> ARCHITECT -> IMPLEMENT -> TEST -> REVIEW -> DEPLOY Universal support for any technology stack with quality gates at each phase. -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model-validation, orchestration:quality-gates --- ``` @@ -65,7 +65,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model - You MUST use TodoWrite to track full lifecycle. + You MUST use Tasks to track full lifecycle. Before starting, create comprehensive todo list with all 7 phases: 0. Initialize (detect stack, check dependencies) @@ -85,7 +85,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model **You MUST:** - Use Task tool to delegate ALL work to agents - - Use TodoWrite to track full lifecycle + - Use Tasks to track full lifecycle - Enforce quality gates between phases - Support multi-model validation diff --git a/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/reviews/impl-review/qwen3-vl.md b/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/reviews/impl-review/qwen3-vl.md index 9f028a7..894f52e 100644 --- a/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/reviews/impl-review/qwen3-vl.md +++ b/plugins/dev/ai-docs/sessions/agentdev-dev-feature-v2-20260105-234119-90dd/reviews/impl-review/qwen3-vl.md @@ -30,7 +30,7 @@ | Field | Status | Notes | |-------|--------|-------| | description | PASS | Multi-line, includes workflow description | -| allowed-tools | PASS | Correct format: `Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep` | +| allowed-tools | PASS | Correct format: `Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep` | | skills | PASS | References 5 skills including orchestration patterns | **Result**: YAML is valid and complete. diff --git a/plugins/dev/commands/architect.md b/plugins/dev/commands/architect.md index 3e80906..efe1e7d 100644 --- a/plugins/dev/commands/architect.md +++ b/plugins/dev/commands/architect.md @@ -1,6 +1,6 @@ --- description: Universal architecture planning for any stack with trade-off analysis -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: dev:context-detection, dev:universal-patterns, orchestration:quality-gates --- @@ -25,7 +25,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:quality-gat - You MUST use TodoWrite to track architecture workflow. + You MUST use Tasks to track architecture workflow. Before starting, create todo list with all 7 phases: 0. Initialize (detect stack) diff --git a/plugins/dev/commands/brainstorm.md b/plugins/dev/commands/brainstorm.md index 3e0be6a..d8678dc 100644 --- a/plugins/dev/commands/brainstorm.md +++ b/plugins/dev/commands/brainstorm.md @@ -1,6 +1,6 @@ --- description: Collaborative ideation and planning with multi-model exploration and consensus scoring -allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: dev:brainstorming, superpowers:using-git-worktrees, superpowers:writing-plans --- @@ -39,7 +39,7 @@ skills: dev:brainstorming, superpowers:using-git-worktrees, superpowers:writing- - You MUST use TodoWrite to track brainstorming workflow. + You MUST use Tasks to track brainstorming workflow. Before starting, create todo list with all 6 phases: 0. Problem Analysis (capture scope, constraints, success criteria) @@ -89,7 +89,7 @@ skills: dev:brainstorming, superpowers:using-git-worktrees, superpowers:writing- ``` - Create TodoWrite items for all 6 phases from the skill + Create task items for all 6 phases from the skill Follow the brainstorming skill workflow exactly diff --git a/plugins/dev/commands/create-style.md b/plugins/dev/commands/create-style.md index fe4f99a..d9d04e2 100644 --- a/plugins/dev/commands/create-style.md +++ b/plugins/dev/commands/create-style.md @@ -3,7 +3,7 @@ description: | Interactive wizard to create and update project design style guides. Supports reference image capture, style updates, and visual reference management. Actions: create, update, capture, add-reference, remove-reference, list-references -allowed-tools: AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep +allowed-tools: AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: - dev:design-references - dev:ui-style-format @@ -41,7 +41,7 @@ skills: - Use AskUserQuestion for all user input gates - Use Write to create .claude/design-style.md - Use Read to check for existing style file - - Use TodoWrite to track wizard progress + - Use Tasks to track wizard progress - Use Bash for file operations in `.claude/` directory **You MUST NOT:** @@ -100,7 +100,7 @@ skills: Check for existing style and initialize wizard - Initialize TodoWrite with wizard phases + Initialize Tasks with wizard phases Use Read tool to check if .claude/design-style.md exists If exists, ask: Update existing or create new? If updating, read existing file as base diff --git a/plugins/dev/commands/debug.md b/plugins/dev/commands/debug.md index 8209dd4..d3c9e28 100644 --- a/plugins/dev/commands/debug.md +++ b/plugins/dev/commands/debug.md @@ -1,6 +1,6 @@ --- description: Universal debugging command that adapts to any technology stack -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: dev:context-detection, dev:debugging-strategies, orchestration:error-recovery --- @@ -26,7 +26,7 @@ skills: dev:context-detection, dev:debugging-strategies, orchestration:error-rec - You MUST use TodoWrite to track debugging workflow. + You MUST use Tasks to track debugging workflow. Before starting, create todo list with all 6 phases: 0. Initialize (understand issue) @@ -44,7 +44,7 @@ skills: dev:context-detection, dev:debugging-strategies, orchestration:error-rec **You MUST:** - Use Task tool to delegate ALL debugging work - - Use TodoWrite to track investigation steps + - Use Tasks to track investigation steps - Document findings systematically - Trace root cause before fixing diff --git a/plugins/dev/commands/deep-research.md b/plugins/dev/commands/deep-research.md index 3f0fb88..74316bb 100644 --- a/plugins/dev/commands/deep-research.md +++ b/plugins/dev/commands/deep-research.md @@ -1,7 +1,7 @@ --- description: Deep research with convergence-based finalization and parallel exploration -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep -skills: dev:context-detection, orchestration:multi-model-validation, orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep +skills: dev:context-detection, orchestration:multi-model-validation, orchestration:task-orchestration --- @@ -31,7 +31,7 @@ skills: dev:context-detection, orchestration:multi-model-validation, orchestrati - You MUST use TodoWrite to track the 6-phase research pipeline. + You MUST use Tasks to track the 6-phase research pipeline. Before starting, create comprehensive todo list: 1. PHASE 0: Session initialization @@ -51,7 +51,7 @@ skills: dev:context-detection, orchestration:multi-model-validation, orchestrati **You MUST:** - Use Task tool to delegate ALL research to agents - - Use TodoWrite to track research pipeline + - Use Tasks to track research pipeline - Enforce convergence criteria between iterations - Use file-based communication between agents - Track iteration count and apply finalization criteria @@ -566,7 +566,7 @@ skills: dev:context-detection, orchestration:multi-model-validation, orchestrati - Iteration statistics - Link to full report - Mark ALL TodoWrite tasks as completed + Mark ALL task items as completed Final report generated, user informed @@ -579,7 +579,7 @@ skills: dev:context-detection, orchestration:multi-model-validation, orchestrati - AskUserQuestion (user input, approval gates) - Bash (model detection, file operations, git) - Read (read findings, check synthesis) - - TodoWrite (progress tracking) + - Tasks (progress tracking) - Glob (find finding files) - Grep (search for patterns) diff --git a/plugins/dev/commands/doc.md b/plugins/dev/commands/doc.md index 3f1986a..ac16225 100644 --- a/plugins/dev/commands/doc.md +++ b/plugins/dev/commands/doc.md @@ -1,6 +1,6 @@ --- description: Documentation command - generate, analyze, fix, or validate docs. Use for README, API docs, tutorials, changelogs. -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: dev:documentation-standards, orchestration:quality-gates --- @@ -27,7 +27,7 @@ skills: dev:documentation-standards, orchestration:quality-gates - You MUST use TodoWrite to track documentation workflow. + You MUST use Tasks to track documentation workflow. Before starting, create todo list based on action: - GENERATE: Detect type, gather context, generate, validate @@ -35,9 +35,9 @@ skills: dev:documentation-standards, orchestration:quality-gates - FIX: Analyze issues, apply fixes, validate improvements - VALIDATE: Check against best practices, generate report - **TodoWrite Ownership Rules:** - - You (the orchestrator) OWN the TodoWrite list exclusively - - Sub-agents (doc-writer, doc-analyzer, doc-fixer) MUST NOT modify TodoWrite + **Tasks Ownership Rules:** + - You (the orchestrator) OWN the Tasks list exclusively + - Sub-agents (doc-writer, doc-analyzer, doc-fixer) MUST NOT modify Tasks - Sub-agents report progress via their return messages only - Use 1-based phase numbering (Phase 1, 2, 3...) - Maintain exactly ONE todo in_progress at any time @@ -192,7 +192,7 @@ skills: dev:documentation-standards, orchestration:quality-gates Write documentation to {output_path} Return brief summary - IMPORTANT: Do NOT use TodoWrite - report progress via return message only." + IMPORTANT: Do NOT use Tasks - report progress via return message only." **If ANALYZE:** @@ -211,7 +211,7 @@ skills: dev:documentation-standards, orchestration:quality-gates Write report to ${SESSION_PATH}/analysis-report.md Return brief summary with score - IMPORTANT: Do NOT use TodoWrite - report progress via return message only." + IMPORTANT: Do NOT use Tasks - report progress via return message only." **If FIX:** @@ -234,7 +234,7 @@ skills: dev:documentation-standards, orchestration:quality-gates Return brief summary of changes - IMPORTANT: Do NOT use TodoWrite - report progress via return message only." + IMPORTANT: Do NOT use Tasks - report progress via return message only." **If VALIDATE:** @@ -253,7 +253,7 @@ skills: dev:documentation-standards, orchestration:quality-gates Write validation report to ${SESSION_PATH}/validation-report.md Return PASS/FAIL with summary - IMPORTANT: Do NOT use TodoWrite - report progress via return message only." + IMPORTANT: Do NOT use Tasks - report progress via return message only." Mark PHASE 4 as completed diff --git a/plugins/dev/commands/feature.md b/plugins/dev/commands/feature.md index 886c658..f6c00d8 100644 --- a/plugins/dev/commands/feature.md +++ b/plugins/dev/commands/feature.md @@ -1,6 +1,6 @@ --- description: 7-phase feature development with multi-model validation and testing -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model-validation, orchestration:quality-gates, orchestration:model-tracking-protocol --- @@ -33,7 +33,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model - You MUST use TodoWrite to track full 7-phase lifecycle. + You MUST use Tasks to track full 7-phase lifecycle. Before starting, create comprehensive todo list: 1. PHASE 0: Session initialization @@ -54,7 +54,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model **You MUST:** - Use Task tool to delegate ALL work to agents - - Use TodoWrite to track full lifecycle + - Use Tasks to track full lifecycle - Enforce quality gates between phases - Respect iteration limits - Use file-based communication @@ -593,7 +593,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model - Provide recommendations for future sessions Present comprehensive summary to user (see completion_message template) - Mark ALL TodoWrite tasks as completed + Mark ALL task items as completed Report generated successfully @@ -606,7 +606,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:multi-model - AskUserQuestion (user input, model selection with multiSelect) - Bash (git commands, test execution, quality checks) - Read (read files, review outputs) - - TodoWrite (progress tracking) + - Tasks (progress tracking) - Glob (find files) - Grep (search patterns) diff --git a/plugins/dev/commands/help.md b/plugins/dev/commands/help.md index b8472c8..3e0c7a9 100644 --- a/plugins/dev/commands/help.md +++ b/plugins/dev/commands/help.md @@ -1,6 +1,6 @@ --- description: Show dev plugin help, detected stack, and available commands -allowed-tools: Task, TodoWrite, Bash, Read, Glob, Grep +allowed-tools: Task, TaskCreate, TaskUpdate, TaskList, TaskGet, Bash, Read, Glob, Grep skills: dev:context-detection --- diff --git a/plugins/dev/commands/implement.md b/plugins/dev/commands/implement.md index f12c7cb..16cd647 100644 --- a/plugins/dev/commands/implement.md +++ b/plugins/dev/commands/implement.md @@ -1,7 +1,7 @@ --- description: Universal implementation command that adapts to any technology stack -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep -skills: dev:context-detection, dev:universal-patterns, orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep +skills: dev:context-detection, dev:universal-patterns, orchestration:task-orchestration --- @@ -25,7 +25,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:todowrite-o - You MUST use TodoWrite to track workflow. + You MUST use Tasks to track workflow. Before starting, create todo list with all 6 phases: 0. Initialize (detect stack) @@ -43,7 +43,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:todowrite-o **You MUST:** - Use Task tool to delegate ALL work to agents - - Use TodoWrite to track workflow + - Use Tasks to track workflow - Use AskUserQuestion for approval gates - Detect stack before implementation @@ -301,7 +301,7 @@ skills: dev:context-detection, dev:universal-patterns, orchestration:todowrite-o - Be clear about detected stack and mode - - Show progress through phases using TodoWrite + - Show progress through phases using Tasks - Provide actionable summaries - Report quality check results clearly - Ask for user approval at key decision points diff --git a/plugins/dev/commands/interview.md b/plugins/dev/commands/interview.md index b5380bb..54c8c2d 100644 --- a/plugins/dev/commands/interview.md +++ b/plugins/dev/commands/interview.md @@ -1,7 +1,7 @@ --- description: Comprehensive specification interview with intelligent requirements elicitation -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep -skills: dev:context-detection, dev:universal-patterns, dev:api-design, dev:design-references, orchestration:quality-gates, orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep +skills: dev:context-detection, dev:universal-patterns, dev:api-design, dev:design-references, orchestration:quality-gates, orchestration:task-orchestration --- @@ -37,7 +37,7 @@ skills: dev:context-detection, dev:universal-patterns, dev:api-design, dev:desig - You MUST use TodoWrite to track the 6-phase interview workflow. + You MUST use Tasks to track the 6-phase interview workflow. Before starting, create comprehensive todo list: 1. PHASE 0: Session initialization (or resume) diff --git a/plugins/dev/commands/ui.md b/plugins/dev/commands/ui.md index 6e7a08e..8176424 100644 --- a/plugins/dev/commands/ui.md +++ b/plugins/dev/commands/ui.md @@ -1,6 +1,6 @@ --- description: UI design review using Gemini multimodal analysis for usability and accessibility -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation --- @@ -35,7 +35,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation - Use Task tool to delegate ALL design reviews to ui agent - Use Bash to check API keys and run Claudish - Use Read/Glob to find design references - - Use TodoWrite to track workflow progress + - Use Tasks to track workflow progress - Use AskUserQuestion for user input gates **You MUST NOT:** @@ -45,8 +45,8 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation - You MUST use TodoWrite to track orchestration workflow. - Initialize TodoWrite AFTER Phase 0.5 (Intent Detection) determines INTENT_MODE. + You MUST use Tasks to track orchestration workflow. + Initialize Tasks AFTER Phase 0.5 (Intent Detection) determines INTENT_MODE. **If INTENT_MODE === "REVIEW_AND_IMPLEMENT":** 1. Session Initialization @@ -171,7 +171,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation - Read (read design files, documentation) - Glob (find design references) - Grep (search for patterns) - - TodoWrite (track workflow progress) + - Tasks (track workflow progress) - AskUserQuestion (user input gates) @@ -187,7 +187,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation Generate session ID and create directories Initialize session-meta.json - Initialize TodoWrite with all workflow phases + Initialize Tasks with all workflow phases Session directory created @@ -225,7 +225,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation Store result: INTENT_MODE = "REVIEW_ONLY" | "REVIEW_AND_IMPLEMENT" - Initialize TodoWrite dynamically based on INTENT_MODE: + Initialize Tasks dynamically based on INTENT_MODE: If INTENT_MODE === "REVIEW_AND_IMPLEMENT": ``` @@ -253,7 +253,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation - INTENT_MODE determined, TodoWrite initialized with appropriate phases + INTENT_MODE determined, Tasks initialized with appropriate phases @@ -498,7 +498,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation - If INTENT_MODE === "REVIEW_AND_IMPLEMENT": Mark as "review_complete" (pending implementation) - Update TodoWrite: Mark "Present Results" as completed + TaskUpdate: Mark "Present Results" as completed User received actionable summary with link to full report @@ -515,7 +515,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation - Mark "Implementation Approval" as in_progress via TodoWrite + Mark "Implementation Approval" as in_progress via Tasks Extract planned changes from review: - Top 3-5 actionable issues @@ -562,7 +562,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation "Implementation skipped. Review document saved at: ${SESSION_PATH}/reviews/design-review/gemini.md" - Mark "Implementation Approval" as completed via TodoWrite + Mark "Implementation Approval" as completed via Tasks User explicitly approved, declined, or chose review-only @@ -579,7 +579,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation - Mark "Execute Implementation" as in_progress via TodoWrite + Mark "Execute Implementation" as in_progress via Tasks Read review findings from ${SESSION_PATH}/reviews/design-review/gemini.md @@ -672,7 +672,7 @@ skills: dev:ui-analyse, dev:ui-implement, orchestration:multi-model-validation Update session-meta.json with status "completed" - Mark "Execute Implementation" as completed via TodoWrite + Mark "Execute Implementation" as completed via Tasks diff --git a/plugins/dev/skills/discipline/verification-before-completion/SKILL.md b/plugins/dev/skills/discipline/verification-before-completion/SKILL.md index 3657b24..ebca74d 100644 --- a/plugins/dev/skills/discipline/verification-before-completion/SKILL.md +++ b/plugins/dev/skills/discipline/verification-before-completion/SKILL.md @@ -78,7 +78,7 @@ Test output: ## Enforcement Mechanism -### TodoWrite Integration +### Tasks Integration When marking a todo as `completed`: 1. **BEFORE** changing status to `completed`, gather fresh evidence diff --git a/plugins/dev/skills/frontend/react-typescript/SKILL.md b/plugins/dev/skills/frontend/react-typescript/SKILL.md index b2afd54..bc91a86 100644 --- a/plugins/dev/skills/frontend/react-typescript/SKILL.md +++ b/plugins/dev/skills/frontend/react-typescript/SKILL.md @@ -536,7 +536,7 @@ function TodoForm() { ```typescript import { useOptimistic } from 'react' -function TodoList({ initialTodos }: { initialTodos: Todo[] }) { +function TaskList({ initialTodos }: { initialTodos: Todo[] }) { const [optimisticTodos, addOptimisticTodo] = useOptimistic( initialTodos, (state, newTodo: string) => [ diff --git a/plugins/dev/skills/frontend/tanstack-query/SKILL.md b/plugins/dev/skills/frontend/tanstack-query/SKILL.md index a249661..84b3589 100644 --- a/plugins/dev/skills/frontend/tanstack-query/SKILL.md +++ b/plugins/dev/skills/frontend/tanstack-query/SKILL.md @@ -589,7 +589,7 @@ const { data } = usePost(42, { staleTime: 10_000 }) **Layer 1: Component-Level** - Specific user feedback: ```typescript -function TodoList() { +function TaskList() { const { data, error, isError, isLoading } = useQuery({ queryKey: ['todos'], queryFn: fetchTodos, @@ -632,7 +632,7 @@ import { ErrorBoundary } from 'react-error-boundary' )} > - + )} @@ -645,7 +645,7 @@ import { ErrorBoundary } from 'react-error-boundary' ```typescript import { useSuspenseQuery } from '@tanstack/react-query' -function TodoList() { +function TaskList() { // data is NEVER undefined (type-safe) const { data } = useSuspenseQuery({ queryKey: ['todos'], @@ -659,7 +659,7 @@ function TodoList() { function App() { return ( }> - + ) } @@ -1059,7 +1059,7 @@ import { renderWithClient } from '@/test/utils' import { screen } from '@testing-library/react' test('displays todos', async () => { - renderWithClient() + renderWithClient() // Wait for data to load expect(await screen.findByText('Test todo')).toBeInTheDocument() @@ -1076,7 +1076,7 @@ test('shows error state', async () => { }) ) - renderWithClient() + renderWithClient() expect(await screen.findByText(/failed/i)).toBeInTheDocument() }) diff --git a/plugins/dev/skills/planning/brainstorming/SKILL.md b/plugins/dev/skills/planning/brainstorming/SKILL.md index 6eca14c..bd2cd09 100644 --- a/plugins/dev/skills/planning/brainstorming/SKILL.md +++ b/plugins/dev/skills/planning/brainstorming/SKILL.md @@ -15,7 +15,10 @@ dependencies: - superpowers:writing-plans tools: - Task - - TodoWrite + - TaskCreate + - TaskUpdate + - TaskList + - TaskGet - Read - Write - Edit @@ -69,7 +72,7 @@ Turn ideas into validated designs through collaborative AI dialogue with resilie This skill improves upon v1.0 by addressing critical reliability gaps: **Key v2.0 Improvements:** -- **No AskUserQuestion dependency**: Uses Task + TodoWrite for structured interaction +- **No AskUserQuestion dependency**: Uses Task + Tasks for structured interaction - **Fallback chains**: 3+ models per role ensures completion even if some fail - **Explicit parallelism**: Documented Task call patterns for parallel execution - **Defined algorithms**: Consensus matrix and confidence scoring are mathematically specified @@ -124,7 +127,7 @@ export OPENROUTER_API_KEY=your-key **How to Ask Users (Without AskUserQuestion)**: ```typescript -// Pattern: Use TodoWrite to track questions, Read/Write for presentation +// Pattern: Use Tasks to track questions, Read/Write for presentation // 1. Write question to temp file await Write({ diff --git a/plugins/frontend/agents/api-analyst.md b/plugins/frontend/agents/api-analyst.md index fb33221..ae5057b 100644 --- a/plugins/frontend/agents/api-analyst.md +++ b/plugins/frontend/agents/api-analyst.md @@ -1,7 +1,7 @@ --- name: api-analyst description: Use this agent when you need to understand or verify API documentation, including data types, request/response formats, authentication requirements, and usage patterns. This agent should be invoked proactively when:\n\n\nContext: User is implementing a new API integration\nuser: "I need to fetch user data from the /api/users endpoint"\nassistant: "Let me use the api-documentation-analyzer agent to check the correct way to call this endpoint"\n\n\n\n\nContext: User encounters an API error\nuser: "I'm getting a 400 error when creating a tenant"\nassistant: "I'll use the api-documentation-analyzer agent to verify the correct request format and required fields"\n\n\n\n\nContext: Replacing mock API with real implementation\nuser: "We need to replace the mockUserApi with the actual backend API"\nassistant: "Let me use the api-documentation-analyzer agent to understand the real API structure before implementing the replacement"\n\n\n\n\nContext: User is unsure about data types\nuser: "What format should the date fields be in when creating a user?"\nassistant: "I'll use the api-documentation-analyzer agent to check the exact data type requirements"\n\n -tools: Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TodoWrite, WebSearch, BashOutput, KillShell, AskUserQuestion, Skill, SlashCommand, ListMcpResourcesTool, ReadMcpResourceTool, mcp__Tenant_Management_Portal_API__read_project_oas_in5g91, mcp__Tenant_Management_Portal_API__read_project_oas_ref_resources_in5g91, mcp__Tenant_Management_Portal_API__refresh_project_oas_in5g91 +tools: Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TaskCreate, TaskUpdate, TaskList, TaskGet, WebSearch, BashOutput, KillShell, AskUserQuestion, Skill, SlashCommand, ListMcpResourcesTool, ReadMcpResourceTool, mcp__Tenant_Management_Portal_API__read_project_oas_in5g91, mcp__Tenant_Management_Portal_API__read_project_oas_ref_resources_in5g91, mcp__Tenant_Management_Portal_API__refresh_project_oas_in5g91 color: yellow --- diff --git a/plugins/frontend/agents/architect.md b/plugins/frontend/agents/architect.md index 0a380e6..9f2ad46 100644 --- a/plugins/frontend/agents/architect.md +++ b/plugins/frontend/agents/architect.md @@ -3,7 +3,7 @@ name: architect description: Use this agent when you need to plan, architect, or create a comprehensive development roadmap for a React-based frontend application. This agent should be invoked when:\n\n\nContext: User wants to start building a new admin dashboard for multi-tenant management.\nuser: "I need to create an admin dashboard for managing users and tenants in a SaaS application"\nassistant: "I'm going to use the Task tool to launch the frontend-architect-planner agent to create a comprehensive development plan for your admin dashboard."\n\n\n\n\nContext: User wants to refactor an existing application with a new tech stack.\nuser: "We need to migrate our admin panel to use Vite, TanStack Router, and TanStack Query"\nassistant: "Let me use the frontend-architect-planner agent to create a migration and architecture plan for your tech stack upgrade."\n\n\n\n\nContext: User needs architectural guidance for a complex React application.\nuser: "How should I structure a multi-tenant admin dashboard with TypeScript and Tailwind?"\nassistant: "I'll invoke the frontend-architect-planner agent to design the architecture and create a structured implementation plan."\n\n\n\nThis agent is specifically designed for frontend architecture planning, not for writing actual code implementation. It creates structured plans, architectures, and step-by-step guides that can be saved to AI-DOCS and referenced by other agents during implementation. ultrathink to to get the best results. model: opus color: purple -tools: TodoWrite, Read, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Glob, Grep, Bash --- ## CRITICAL: External Model Proxy Mode (Optional) @@ -64,8 +64,8 @@ You are an elite Frontend Architecture Specialist with deep expertise in modern You architect frontend applications by creating comprehensive, step-by-step implementation plans. You do NOT write implementation code directly - instead, you create detailed architectural blueprints and actionable plans that other agents or developers will follow. -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to create and maintain a todo list throughout your planning workflow. This provides visibility and ensures systematic completion of all planning phases. +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to create and maintain a todo list throughout your planning workflow. This provides visibility and ensures systematic completion of all planning phases. ## Your Expertise Areas @@ -83,10 +83,10 @@ You MUST use the TodoWrite tool to create and maintain a todo list throughout yo ### STEP 0: Initialize Todo List (MANDATORY FIRST STEP) -Before starting any planning work, you MUST create a todo list using the TodoWrite tool: +Before starting any planning work, you MUST create a task list using the Tasks system: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "Perform gap analysis and ask clarifying questions" status: "in_progress" activeForm: "Performing gap analysis and asking clarifying questions" @@ -196,16 +196,16 @@ Before any planning or architecture work, you MUST: **After Gaps Are Clarified:** -4. **Update TodoWrite**: Mark "Perform gap analysis" as completed, mark "Complete requirements analysis" as in_progress +4. **TaskUpdate**: Mark "Perform gap analysis" as completed, mark "Complete requirements analysis" as in_progress 5. Analyze the user's complete requirements thoroughly 6. Identify core features, user roles, and data entities 7. Define success criteria and constraints 8. Document all requirements and assumptions -9. **Update TodoWrite**: Mark "Complete requirements analysis" as completed +9. **TaskUpdate**: Mark "Complete requirements analysis" as completed ### Phase 2: Architecture Design -**Before starting**: Update TodoWrite to mark "Design architecture and component hierarchy" as in_progress +**Before starting**: TaskUpdate to mark "Design architecture and component hierarchy" as in_progress 1. Design the project structure following React best practices 2. Plan the component hierarchy and composition strategy 3. Define routing architecture using TanStack Router patterns @@ -213,37 +213,37 @@ Before any planning or architecture work, you MUST: 5. Plan state management approach (local vs server state) 6. Define TypeScript types and interfaces structure 7. Plan testing strategy and coverage approach -8. **Update TodoWrite**: Mark "Design architecture" as completed +8. **TaskUpdate**: Mark "Design architecture" as completed ### Phase 3: Implementation Planning -**Before starting**: Update TodoWrite to mark "Create implementation roadmap and phases" as in_progress +**Before starting**: TaskUpdate to mark "Create implementation roadmap and phases" as in_progress 1. Break down the architecture into logical implementation phases 2. Create a step-by-step implementation roadmap 3. Define dependencies between tasks 4. Identify potential challenges and mitigation strategies 5. Specify tooling setup and configuration needs -6. **Update TodoWrite**: Mark "Create implementation roadmap" as completed +6. **TaskUpdate**: Mark "Create implementation roadmap" as completed ### Phase 4: Documentation Creation -**Before starting**: Update TodoWrite to mark "Generate documentation in AI-DOCS folder" as in_progress +**Before starting**: TaskUpdate to mark "Generate documentation in AI-DOCS folder" as in_progress 1. Create comprehensive documentation in the AI-DOCS folder 2. Generate structured TODO lists for claude-code-todo.md 3. Write clear, actionable instructions for each implementation step 4. Include code structure examples (not full implementation) 5. Document architectural decisions and rationale -6. **Update TodoWrite**: Mark "Generate documentation" as completed +6. **TaskUpdate**: Mark "Generate documentation" as completed ### Phase 5: User Validation -**Before starting**: Update TodoWrite to mark "Present plan and seek user validation" as in_progress +**Before starting**: TaskUpdate to mark "Present plan and seek user validation" as in_progress 1. Present your plan in clear, digestible sections 2. Highlight key decisions and trade-offs 3. Ask for specific feedback on the plan 4. Wait for user approval before proceeding to next phase 5. Iterate based on feedback -6. **Update TodoWrite**: Mark "Present plan and seek user validation" as completed when plan is approved +6. **TaskUpdate**: Mark "Present plan and seek user validation" as completed when plan is approved ## Your Output Standards diff --git a/plugins/frontend/agents/cleaner.md b/plugins/frontend/agents/cleaner.md index afcc07e..5f1bead 100644 --- a/plugins/frontend/agents/cleaner.md +++ b/plugins/frontend/agents/cleaner.md @@ -1,7 +1,7 @@ --- name: cleaner description: Use this agent when the user has approved an implementation and is satisfied with the results, and you need to clean up all temporary files, scripts, test files, documentation, and artifacts created during the development process. This agent should be invoked after implementation is complete and before final delivery.\n\nExamples:\n\n\nContext: User has just completed implementing a new feature and is happy with it.\nuser: "Great! The payment processing feature is working perfectly. Now I need to clean everything up."\nassistant: "I'll use the project-cleaner agent to remove all temporary files, test scripts, and implementation documentation that were created during development, then provide you with a summary of the final deliverables."\n\n\n\n\nContext: User signals completion and approval of a multi-phase refactoring effort.\nuser: "The code refactoring is done and all tests pass. Can you clean up the project?"\nassistant: "I'm going to use the project-cleaner agent to identify and remove all temporary refactoring scripts, intermediate documentation, and unused test files that were part of the iteration."\n\n -tools: Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TodoWrite, WebSearch, BashOutput, KillShell +tools: Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TaskCreate, TaskUpdate, TaskList, TaskGet, WebSearch, BashOutput, KillShell color: yellow --- diff --git a/plugins/frontend/agents/css-developer.md b/plugins/frontend/agents/css-developer.md index 1b0c7da..b18ad25 100644 --- a/plugins/frontend/agents/css-developer.md +++ b/plugins/frontend/agents/css-developer.md @@ -1,7 +1,7 @@ --- name: css-developer description: Use this agent when you need CSS architecture guidance, want to ensure CSS changes don't break existing styles, or need to understand the application's CSS patterns and rules. This agent maintains CSS knowledge and provides strict guidelines for UI development.\n\nExamples:\n\n- Context: UI developer needs to understand existing CSS architecture before making changes\nuser: "What CSS patterns are used for form inputs in this application?"\nassistant: "Let me consult the css-developer agent to understand the CSS architecture for form inputs"\n\n\n- Context: Need to make global CSS changes without breaking existing styles\nuser: "I want to update the button styles globally, how should I approach this?"\nassistant: "Let me use the css-developer agent to analyze existing button styles and provide safe change guidelines"\n\n\n- Context: Want to understand Tailwind CSS patterns in the codebase\nuser: "What Tailwind utilities are commonly used for layout in this project?"\nassistant: "I'll invoke the css-developer agent to document and explain the layout patterns"\n -tools: TodoWrite, Read, Write, Edit, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Glob, Grep, Bash skills: code-analysis:developer-detective color: blue --- @@ -549,7 +549,7 @@ UI Developer should consult you when: Before any work, create todo list: ``` -TodoWrite with: +TaskCreate: - content: "Analyze codebase CSS patterns and architecture" status: "in_progress" activeForm: "Analyzing CSS patterns" diff --git a/plugins/frontend/agents/designer.md b/plugins/frontend/agents/designer.md index 37b8d32..b0d8c01 100644 --- a/plugins/frontend/agents/designer.md +++ b/plugins/frontend/agents/designer.md @@ -2,7 +2,7 @@ name: designer description: Use this agent when you need to review and validate that an implemented UI component matches its reference design with DOM inspection and computed CSS analysis. This agent acts as a senior UX/UI designer reviewing implementation quality. Trigger this agent in these scenarios:\n\n\nContext: Developer has just implemented a new component based on design specifications.\nuser: "I've finished implementing the UserProfile component. Can you validate it against the Figma design?"\nassistant: "I'll use the designer agent to review your implementation against the design reference and provide detailed feedback."\n\n\n\n\nContext: Developer suspects their component doesn't match the design specifications.\nuser: "I think the colors in my form might be off from the design. Can you check?"\nassistant: "Let me use the designer agent to perform a comprehensive design review of your form implementation against the reference design, including colors, spacing, and layout."\n\n\n\n\nContext: Code review process after implementing a UI feature.\nuser: "Here's my implementation of the CreateDialog component"\nassistant: "Great! Now I'll use the designer agent to validate your implementation against the design specifications to ensure visual fidelity."\n\n\n\nUse this agent proactively when:\n- A component has been freshly implemented or significantly modified\n- Working with designs from Figma, Figma Make, or other design tools\n- Design fidelity is critical to the project requirements\n- Before submitting a PR for UI-related changes\n- After UI Developer has made implementation changes color: purple -tools: TodoWrite, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Bash --- ## CRITICAL: External Model Proxy Mode (Optional) @@ -707,7 +707,7 @@ Adapt your analysis and recommendations to match the project's stack. - Reference exact file paths and line numbers - Suggest specific Tailwind classes or CSS properties - Calculate objective design fidelity scores -- Use TodoWrite to track review progress +- Use Tasks to track review progress **❌ YOU SHOULD NOT:** - Write or modify any code files (no Write, no Edit tools) diff --git a/plugins/frontend/agents/developer.md b/plugins/frontend/agents/developer.md index 672a683..e1a036e 100644 --- a/plugins/frontend/agents/developer.md +++ b/plugins/frontend/agents/developer.md @@ -2,7 +2,7 @@ name: developer description: Use this agent when you need to implement TypeScript frontend features, components, or refactorings in a Vite-based project. Examples: (1) User says 'Create a user profile card component with avatar, name, and bio fields' - Use this agent to implement the component following project patterns and best practices. (2) User says 'Add form validation to the login page' - Use this agent to implement validation logic while reusing existing form components. (3) User says 'I've finished the authentication flow, can you review the implementation?' - While a code-review agent might be better, this agent can also provide implementation feedback and suggestions. (4) After user describes a new feature from documentation or planning docs - Proactively use this agent to scaffold and implement the feature using existing patterns. (5) User says 'The dashboard needs a new analytics widget' - Use this agent to create the widget while maintaining consistency with existing dashboard components. color: green -tools: TodoWrite, Write, Edit, Read, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Write, Edit, Read, Bash, Glob, Grep --- ## CRITICAL: External Model Proxy Mode (Optional) @@ -68,10 +68,10 @@ You are an expert TypeScript frontend developer specializing in building clean, ## Core Development Principles -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to create and maintain a todo list throughout your implementation workflow. This provides visibility into your progress and ensures systematic completion of all implementation tasks. +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to create and maintain a todo list throughout your implementation workflow. This provides visibility into your progress and ensures systematic completion of all implementation tasks. -**Before starting any implementation**, create a todo list that includes: +**Before starting any implementation**, create a task list that includes: 1. All features/tasks from the provided documentation or plan 2. Quality check tasks (formatting, linting, type checking, testing) 3. Any research or exploration tasks needed @@ -115,24 +115,24 @@ You MUST use the TodoWrite tool to create and maintain a todo list throughout yo Before presenting any code, you MUST perform these checks in order: 1. **Code Formatting**: Run Biome.js formatter on all modified files - - Add to TodoWrite: "Run Biome.js formatter on modified files" + - TaskCreate: "Run Biome.js formatter on modified files" - Mark as completed after running successfully 2. **Linting**: Run Biome.js linter and fix all errors and warnings - - Add to TodoWrite: "Run Biome.js linter and fix all errors" + - TaskCreate: "Run Biome.js linter and fix all errors" - Mark as completed after all issues are resolved 3. **Type Checking**: Run TypeScript compiler (`tsc --noEmit`) and resolve all type errors - - Add to TodoWrite: "Run TypeScript type checking and fix errors" + - TaskCreate: "Run TypeScript type checking and fix errors" - Mark as completed after all type errors are resolved 4. **Testing**: Run relevant tests with Vitest if they exist for modified areas - - Add to TodoWrite: "Run Vitest tests for modified areas" + - TaskCreate: "Run Vitest tests for modified areas" - Mark as completed after all tests pass If any check fails, fix the issues before presenting code to the user. Never deliver code with linting errors, type errors, or formatting inconsistencies. -**Track all quality checks in your TodoWrite list** to ensure nothing is missed. +**Track all quality checks in your task list** to ensure nothing is missed. ## Refactoring Protocol @@ -157,22 +157,22 @@ When you identify the need for significant refactoring: 1. **Understand Requirements**: Carefully analyze the instruction or documentation provided -2. **Create Todo List** (MANDATORY): Use TodoWrite to create a comprehensive task list: +2. **Create Todo List** (MANDATORY): Use Tasks to create a comprehensive task list: - Break down all implementation tasks from requirements/plan - Add quality check tasks (formatting, linting, type checking, testing) - Include any research or exploration tasks - Mark the first task as "in_progress" 3. **Survey Existing Code**: Identify relevant existing components, utilities, and patterns - - Update TodoWrite as you complete exploration + - TaskUpdate as you complete exploration 4. **Plan Structure**: Design the implementation to fit naturally into existing architecture 5. **Implement Incrementally**: Build features step-by-step, testing as you go - - **Before starting each task**: Mark it as "in_progress" in TodoWrite - - **After completing each task**: Mark it as "completed" in TodoWrite immediately + - **Before starting each task**: Mark it as "in_progress" in task list + - **After completing each task**: Mark it as "completed" in task list immediately - Keep only ONE task as "in_progress" at any time - - Add new tasks to TodoWrite if additional work is discovered + - Add new tasks to task list if additional work is discovered 6. **Verify Quality**: Run all mandatory checks - Create specific todos for each quality check if not already present diff --git a/plugins/frontend/agents/plan-reviewer.md b/plugins/frontend/agents/plan-reviewer.md index 08023ac..484838d 100644 --- a/plugins/frontend/agents/plan-reviewer.md +++ b/plugins/frontend/agents/plan-reviewer.md @@ -3,7 +3,7 @@ name: plan-reviewer description: Use this agent to review architecture plans with external AI models before implementation begins. This agent provides multi-model perspective on architectural decisions, helping identify issues early when they're cheaper to fix. Examples:\n\n1. After architect creates a plan:\nuser: 'The architecture plan is complete. I want external models to review it for potential issues'\nassistant: 'I'll use the Task tool to launch plan-reviewer agents in parallel with different AI models to get independent perspectives on the architecture plan.'\n\n2. Before starting implementation:\nuser: 'Can we get a second opinion on this architecture from GPT-5 Codex?'\nassistant: 'I'm launching the plan-reviewer agent with PROXY_MODE for external AI review of the architecture plan.'\n\n3. Multi-model validation:\nuser: 'I want Grok and Codex to both review the plan'\nassistant: 'I'll launch two plan-reviewer agents in parallel - one with PROXY_MODE for Grok and one for Codex - to get diverse perspectives on the architecture.' model: opus color: blue -tools: TodoWrite, Bash, Read +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Bash, Read --- ## CRITICAL: External Model Proxy Mode (Required) @@ -159,11 +159,11 @@ Then proceed with normal review as defined below. You are an expert software architect specializing in React, TypeScript, and modern frontend development. When reviewing architecture plans, you focus on: -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to track your review progress: +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to track your review progress: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "Read and understand the architecture plan" status: "in_progress" activeForm: "Reading and understanding the architecture plan" @@ -184,7 +184,7 @@ TodoWrite with the following items: ## Review Framework ### 1. Architectural Issues -**Update TodoWrite: Mark "Identify architectural issues" as in_progress** +**TaskUpdate: Mark "Identify architectural issues" as in_progress** Check for: - Design flaws or anti-patterns @@ -195,10 +195,10 @@ Check for: - Inappropriate use of patterns - Over-engineering or under-engineering -**Update TodoWrite: Mark as completed, move to next** +**TaskUpdate: Mark as completed, move to next** ### 2. Missing Considerations -**Update TodoWrite: Mark "Evaluate missing considerations" as in_progress** +**TaskUpdate: Mark "Evaluate missing considerations" as in_progress** Identify gaps in: - Edge cases not addressed @@ -211,10 +211,10 @@ Identify gaps in: - State management complexity - Data flow patterns -**Update TodoWrite: Mark as completed, move to next** +**TaskUpdate: Mark as completed, move to next** ### 3. Alternative Approaches -**Update TodoWrite: Mark "Suggest alternative approaches" as in_progress** +**TaskUpdate: Mark "Suggest alternative approaches" as in_progress** Suggest: - Better patterns or architectures @@ -225,7 +225,7 @@ Suggest: - Better library choices - Performance optimizations -**Update TodoWrite: Mark as completed, move to next** +**TaskUpdate: Mark as completed, move to next** ### 4. Technology Choices diff --git a/plugins/frontend/agents/reviewer.md b/plugins/frontend/agents/reviewer.md index 0c614ea..eaa85b7 100644 --- a/plugins/frontend/agents/reviewer.md +++ b/plugins/frontend/agents/reviewer.md @@ -3,7 +3,7 @@ name: reviewer description: Use this agent when you have completed writing or modifying a logical chunk of code and need comprehensive review against simplicity principles, AEI documentation requirements, OWASP security standards, and production-readiness criteria. Examples:\n\n1. After implementing a new feature:\nuser: 'I've just finished implementing the user authentication module with JWT tokens'\nassistant: 'Let me use the Task tool to launch the senior-code-reviewer agent to perform a comprehensive review of your authentication implementation against our coding standards, security requirements, and the AEI documentation.'\n\n2. Before committing significant changes:\nuser: 'I refactored the payment processing service to use the new gateway API'\nassistant: 'I'll invoke the senior-code-reviewer agent using the Task tool to validate your refactoring follows our simplicity principles, matches existing patterns, and meets OWASP security standards.'\n\n3. When preparing for pull request:\nuser: 'Can you review the database migration scripts I just created?'\nassistant: 'I'm launching the senior-code-reviewer agent via the Task tool to examine your migration scripts for security vulnerabilities, performance implications, and alignment with our established patterns.'\n\n4. Proactive review after code generation:\nuser: 'Please create a REST API endpoint for product catalog search'\nassistant: 'Here is the implementation: [code provided]\nNow let me use the Task tool to invoke the senior-code-reviewer agent to ensure this code meets our standards for simplicity, security, and testability before you proceed.' model: opus color: red -tools: TodoWrite, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Bash --- ## CRITICAL: External Model Proxy Mode (Optional) @@ -62,12 +62,12 @@ You are a Senior Code Reviewer with 15+ years of experience in software architec ## Your Review Framework -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to create and maintain a todo list throughout your review process. This ensures systematic, thorough coverage of all review criteria and provides visibility into review progress. +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to create and maintain a todo list throughout your review process. This ensures systematic, thorough coverage of all review criteria and provides visibility into review progress. -**Before starting any review**, create a todo list with all review steps: +**Before starting any review**, create a task list with all review steps: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "Verify AEI documentation alignment" status: "in_progress" activeForm: "Verifying AEI documentation alignment" @@ -104,7 +104,7 @@ When reviewing code, you will: - Validate that established patterns and approaches already present in the codebase are followed - Identify any deviations from documented architectural decisions - Confirm the implementation uses the cleanest, most obvious approach possible - - **Update TodoWrite**: Mark "Verify AEI documentation alignment" as completed, mark next item as in_progress + - **TaskUpdate**: Mark "Verify AEI documentation alignment" as completed, mark next item as in_progress 2. **Assess Code Simplicity** - Evaluate if the solution is the simplest possible implementation that meets requirements @@ -112,7 +112,7 @@ When reviewing code, you will: - Check for clear, self-documenting code that minimizes cognitive load - Verify that abstractions are justified and add genuine value - Ensure naming conventions are intuitive and reveal intent - - **Update TodoWrite**: Mark "Assess code simplicity" as completed, mark next item as in_progress + - **TaskUpdate**: Mark "Assess code simplicity" as completed, mark next item as in_progress 3. **Conduct Multi-Tier Issue Analysis** @@ -157,7 +157,7 @@ Systematically check for: - Insecure dependencies and known CVEs - Insufficient logging and monitoring - Server-side request forgery (SSRF) - - **Update TodoWrite**: Mark "Conduct security review" as completed, mark next item as in_progress + - **TaskUpdate**: Mark "Conduct security review" as completed, mark next item as in_progress 5. **Performance & Resource Optimization** @@ -169,7 +169,7 @@ Evaluate: - Resource cleanup and disposal (connections, file handles, streams) - Async/await usage and thread management - Unnecessary object creation or copying - - **Update TodoWrite**: Mark "Evaluate performance" as completed, mark next item as in_progress + - **TaskUpdate**: Mark "Evaluate performance" as completed, mark next item as in_progress 6. **Testability Assessment** @@ -181,7 +181,7 @@ Verify: - Test coverage exists for critical paths - Edge cases and error scenarios are testable - Integration points have clear contracts - - **Update TodoWrite**: Mark "Assess testability" as completed, mark next item as in_progress + - **TaskUpdate**: Mark "Assess testability" as completed, mark next item as in_progress 7. **Maintainability & Supportability** @@ -192,7 +192,7 @@ Check for: - Code readability and self-documentation - Consistent patterns with existing codebase - Future extensibility without major rewrites - - **Update TodoWrite**: Mark "Check maintainability" as completed, mark next item as in_progress + - **TaskUpdate**: Mark "Check maintainability" as completed, mark next item as in_progress ## Output Format diff --git a/plugins/frontend/agents/test-architect.md b/plugins/frontend/agents/test-architect.md index 0e33f68..7d32508 100644 --- a/plugins/frontend/agents/test-architect.md +++ b/plugins/frontend/agents/test-architect.md @@ -3,7 +3,7 @@ name: test-architect description: Use this agent when you need comprehensive test coverage analysis and implementation. Specifically use this agent when: (1) You've completed implementing a feature and need unit and integration tests written, (2) Existing tests are failing and you need a root cause analysis to determine if it's a test issue, dependency issue, or implementation bug, (3) You need test quality review and improvements based on modern best practices, (4) You're starting a new module and need a test strategy. Examples:\n\n\nContext: User has just implemented a new authentication service and needs comprehensive test coverage.\nuser: "I've finished implementing the UserAuthService class with login, logout, and token refresh methods. Can you create the necessary tests?"\nassistant: "I'll use the vitest-test-architect agent to analyze your implementation, extract requirements, and create comprehensive unit and integration tests."\n\n\n\n\nContext: User has failing tests after refactoring and needs analysis.\nuser: "I refactored the payment processing module and now 5 tests are failing. Can you help figure out what's wrong?"\nassistant: "I'll engage the vitest-test-architect agent to analyze the failing tests, determine the root cause, and provide a detailed report."\n\n\n\n\nContext: Proactive use after code implementation.\nuser: "Here's the new API endpoint handler for user registration:"\n[code provided]\nassistant: "I see you've implemented a new feature. Let me use the vitest-test-architect agent to ensure we have proper test coverage for this."\n\n model: opus color: orange -tools: TodoWrite, Read, Write, Edit, Glob, Grep, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Glob, Grep, Bash --- ## CRITICAL: External Model Proxy Mode (Optional) @@ -62,12 +62,12 @@ You are a Senior Test Engineer with deep expertise in TypeScript, Vitest, and mo ## Core Responsibilities -**CRITICAL: Task Management with TodoWrite** -You MUST use the TodoWrite tool to create and maintain a todo list throughout your testing workflow. This ensures systematic test coverage, tracks progress, and provides visibility into the testing process. +**CRITICAL: Task Management with Tasks** +You MUST use the Tasks system to create and maintain a todo list throughout your testing workflow. This ensures systematic test coverage, tracks progress, and provides visibility into the testing process. -**Before starting any testing work**, create a todo list that includes: +**Before starting any testing work**, create a task list that includes: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "Analyze requirements and extract testing needs" status: "in_progress" activeForm: "Analyzing requirements and extracting testing needs" @@ -101,7 +101,7 @@ Add specific test implementation tasks as needed based on the features being tes - Identify all implemented features that need test coverage - Map features to appropriate test types (unit vs integration) - Prioritize testing based on feature criticality and complexity - - **Update TodoWrite**: Mark "Analyze requirements" as completed, mark "Design test strategy" as in_progress + - **TaskUpdate**: Mark "Analyze requirements" as completed, mark "Design test strategy" as in_progress 2. **Test Architecture & Implementation** - Write clear, maintainable tests using Vitest and TypeScript @@ -112,8 +112,8 @@ Add specific test implementation tasks as needed based on the features being tes - Mock external dependencies appropriately using `vi.mock()` and `vi.spyOn()` - Keep tests isolated and independent - no shared state between tests - Aim for tests that are self-documenting through clear naming and structure - - **Update TodoWrite**: Mark test strategy as completed, mark test implementation tasks as in_progress one at a time - - **Update TodoWrite**: Mark each test implementation task as completed when tests are written + - **TaskUpdate**: Mark test strategy as completed, mark test implementation tasks as in_progress one at a time + - **TaskUpdate**: Mark each test implementation task as completed when tests are written 3. **Test Quality Standards & Philosophy** @@ -158,7 +158,7 @@ Add specific test implementation tasks as needed based on the features being tes When tests fail, follow this systematic approach to determine root cause and provide appropriate feedback: - **IMPORTANT**: Add failure analysis tasks to TodoWrite when failures occur: + **IMPORTANT**: Add failure analysis tasks to task list when failures occur: ``` - content: "Analyze test failure: [test name]" status: "in_progress" @@ -178,7 +178,7 @@ Add specific test implementation tasks as needed based on the features being tes - Check for async/await issues or race conditions - Validate test data and setup - **IF TEST IS FLAWED**: Fix the test and re-run (don't blame implementation) - - **Update TodoWrite**: Add findings to current analysis task + - **TaskUpdate**: Add findings to current analysis task **Step 2: Check External Dependencies** - Verify required environment variables are set @@ -193,7 +193,7 @@ Add specific test implementation tasks as needed based on the features being tes - Identify specific implementation issues causing failures - Categorize bugs by severity (Critical / Major / Minor) - Document expected vs actual behavior with code examples - - **Update TodoWrite**: Mark analysis as completed, mark feedback preparation as in_progress + - **TaskUpdate**: Mark analysis as completed, mark feedback preparation as in_progress **Step 4: Categorize Failure and Provide Structured Feedback** @@ -293,7 +293,7 @@ Add specific test implementation tasks as needed based on the features being tes 6. **Comprehensive Reporting** - **Update TodoWrite**: Add "Generate comprehensive failure analysis report" task when implementation issues are found + **TaskUpdate**: Add "Generate comprehensive failure analysis report" task when implementation issues are found When implementation issues are found, provide a structured report: @@ -349,30 +349,30 @@ Add specific test implementation tasks as needed based on the features being tes ## Workflow -**Remember**: Create a TodoWrite list BEFORE starting, and update it throughout the workflow! +**Remember**: Create a task list BEFORE starting, and update it throughout the workflow! 1. **Request and read relevant documentation files** - - Update TodoWrite: Mark analysis as in_progress + - TaskUpdate: Mark analysis as in_progress 2. **Analyze implemented code to understand features** - - Update TodoWrite: Mark as completed when done + - TaskUpdate: Mark as completed when done 3. **Design test strategy (unit vs integration breakdown)** - - Update TodoWrite: Mark as in_progress, then completed + - TaskUpdate: Mark as in_progress, then completed 4. **Implement tests following best practices** - - Update TodoWrite: Mark each test implementation task as in_progress, then completed + - TaskUpdate: Mark each test implementation task as in_progress, then completed 5. **Run tests and analyze results** - - Update TodoWrite: Mark "Run all tests" as in_progress + - TaskUpdate: Mark "Run all tests" as in_progress 6. **If failures occur, execute the Failure Analysis Protocol** - - Update TodoWrite: Add specific failure analysis tasks + - TaskUpdate: Add specific failure analysis tasks 7. **Generate comprehensive report if implementation issues found** - - Update TodoWrite: Track report generation + - TaskUpdate: Track report generation 8. **Suggest test coverage improvements and next steps** - - Update TodoWrite: Mark all tasks as completed when workflow is done + - TaskUpdate: Mark all tasks as completed when workflow is done Always ask for clarification if requirements are ambiguous. Your goal is practical, maintainable test coverage that catches real bugs without creating maintenance burden. diff --git a/plugins/frontend/agents/tester.md b/plugins/frontend/agents/tester.md index 83e0ac1..25db1c3 100644 --- a/plugins/frontend/agents/tester.md +++ b/plugins/frontend/agents/tester.md @@ -1,7 +1,7 @@ --- name: tester description: Use this agent when you need to manually test a website's user interface by interacting with elements, verifying visual feedback, and checking console logs. Examples:\n\n- Example 1:\n user: "I just updated the checkout flow on localhost:3000. Can you test it?"\n assistant: "I'll launch the ui-manual-tester agent to manually test your checkout flow, interact with the elements, and verify everything works correctly."\n \n- Example 2:\n user: "Please verify that the login form validation is working on staging.example.com"\n assistant: "I'm using the ui-manual-tester agent to navigate to the staging site, test the login form validation, and report back on the results."\n \n- Example 3:\n user: "Check if the modal dialog closes properly when clicking the X button"\n assistant: "Let me use the ui-manual-tester agent to test the modal dialog interaction and verify the close functionality."\n \n- Example 4 (Proactive):\n assistant: "I've just implemented the new navigation menu. Now let me use the ui-manual-tester agent to verify all the links work and the menu displays correctly."\n \n- Example 5 (Proactive):\n assistant: "I've finished updating the form submission logic. I'll now use the ui-manual-tester agent to test the form with various inputs and ensure validation works as expected." -tools: Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TodoWrite, WebSearch, BashOutput, KillShell, AskUserQuestion, Skill, SlashCommand, mcp__chrome-devtools__click, mcp__chrome-devtools__close_page, mcp__chrome-devtools__drag, mcp__chrome-devtools__emulate_cpu, mcp__chrome-devtools__emulate_network, mcp__chrome-devtools__evaluate_script, mcp__chrome-devtools__fill, mcp__chrome-devtools__fill_form, mcp__chrome-devtools__get_console_message, mcp__chrome-devtools__get_network_request, mcp__chrome-devtools__handle_dialog, mcp__chrome-devtools__hover, mcp__chrome-devtools__list_console_messages, mcp__chrome-devtools__list_network_requests, mcp__chrome-devtools__list_pages, mcp__chrome-devtools__navigate_page, mcp__chrome-devtools__navigate_page_history, mcp__chrome-devtools__new_page, mcp__chrome-devtools__performance_analyze_insight, mcp__chrome-devtools__performance_start_trace, mcp__chrome-devtools__performance_stop_trace, mcp__chrome-devtools__resize_page, mcp__chrome-devtools__select_page, mcp__chrome-devtools__take_screenshot, mcp__chrome-devtools__take_snapshot, mcp__chrome-devtools__upload_file, mcp__chrome-devtools__wait_for +tools: Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TaskCreate, TaskUpdate, TaskList, TaskGet, WebSearch, BashOutput, KillShell, AskUserQuestion, Skill, SlashCommand, mcp__chrome-devtools__click, mcp__chrome-devtools__close_page, mcp__chrome-devtools__drag, mcp__chrome-devtools__emulate_cpu, mcp__chrome-devtools__emulate_network, mcp__chrome-devtools__evaluate_script, mcp__chrome-devtools__fill, mcp__chrome-devtools__fill_form, mcp__chrome-devtools__get_console_message, mcp__chrome-devtools__get_network_request, mcp__chrome-devtools__handle_dialog, mcp__chrome-devtools__hover, mcp__chrome-devtools__list_console_messages, mcp__chrome-devtools__list_network_requests, mcp__chrome-devtools__list_pages, mcp__chrome-devtools__navigate_page, mcp__chrome-devtools__navigate_page_history, mcp__chrome-devtools__new_page, mcp__chrome-devtools__performance_analyze_insight, mcp__chrome-devtools__performance_start_trace, mcp__chrome-devtools__performance_stop_trace, mcp__chrome-devtools__resize_page, mcp__chrome-devtools__select_page, mcp__chrome-devtools__take_screenshot, mcp__chrome-devtools__take_snapshot, mcp__chrome-devtools__upload_file, mcp__chrome-devtools__wait_for skills: code-analysis:tester-detective color: pink --- diff --git a/plugins/frontend/agents/ui-developer.md b/plugins/frontend/agents/ui-developer.md index 184ea21..420ac3c 100644 --- a/plugins/frontend/agents/ui-developer.md +++ b/plugins/frontend/agents/ui-developer.md @@ -2,7 +2,7 @@ name: ui-developer description: Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n\nContext: Designer has reviewed implementation and found visual discrepancies.\nuser: "The designer found several color and spacing issues in the UserProfile component"\nassistant: "I'll use the ui-developer agent to fix all the design discrepancies identified by the designer."\n\n\n\n\nContext: Need to implement a new component from Figma design.\nuser: "Can you implement this Figma design for the ProductCard component?"\nassistant: "I'll use the ui-developer agent to create a pixel-perfect implementation of the ProductCard from the Figma design."\n\n\n\n\nContext: Component needs responsive design improvements.\nuser: "The navigation menu doesn't work well on mobile devices"\nassistant: "Let me use the ui-developer agent to implement proper responsive behavior for the navigation menu across all breakpoints."\n\n\n\nUse this agent proactively when:\n- Designer has identified visual/UX discrepancies that need fixing\n- New UI components need to be implemented from design references\n- Existing components need responsive design improvements\n- Accessibility issues need to be addressed (ARIA, keyboard navigation, etc.)\n- Design system components need to be created or refactored color: blue -tools: TodoWrite, Write, Edit, Read, Bash +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Write, Edit, Read, Bash --- ## CRITICAL: External Model Proxy Mode (Optional) @@ -558,7 +558,7 @@ export function UserCard({ user }: UserCardProps) { **STEP 1: Create Todo List** -Use TodoWrite to track your implementation: +Use Tasks to track your implementation: ``` - content: "Read and analyze designer feedback or design reference" status: "in_progress" diff --git a/plugins/frontend/commands/implement-ui.md b/plugins/frontend/commands/implement-ui.md index 02f0371..0e7a43d 100644 --- a/plugins/frontend/commands/implement-ui.md +++ b/plugins/frontend/commands/implement-ui.md @@ -1,6 +1,6 @@ --- description: Implement UI components from scratch with design reference, intelligent validation, and adaptive agent switching -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- ## Mission @@ -15,7 +15,7 @@ Implement new UI components from scratch based on a design reference (Figma, scr - Use Task tool to delegate ALL work to agents - Use Bash to run git commands (status, diff) - Use Read/Glob/Grep to understand context -- Use TodoWrite to track workflow progress +- Use Tasks to track workflow progress - Use AskUserQuestion to gather inputs and preferences - Coordinate agent workflows with smart switching logic @@ -81,10 +81,10 @@ styling patterns, and the best location for the new component. ### PHASE 0: Initialize Workflow Todo List (MANDATORY FIRST STEP) -**BEFORE** starting, create a global workflow todo list using TodoWrite: +**BEFORE** starting, create a global workflow todo list using Tasks: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "PHASE 1: Gather user inputs (design reference, component description, preferences)" status: "in_progress" activeForm: "PHASE 1: Gathering user inputs" @@ -220,8 +220,8 @@ Store the user's choice as `manual_validation_enabled` (boolean). **Step 7: Validate Inputs** -- **Update TodoWrite**: Mark "PHASE 1: Gather user inputs" as completed -- **Update TodoWrite**: Mark "PHASE 1: Validate inputs" as in_progress +- **TaskUpdate**: Mark "PHASE 1: Gather user inputs" as completed +- **TaskUpdate**: Mark "PHASE 1: Validate inputs" as in_progress **Validate Design Reference:** - If contains "figma.com" → Figma design @@ -244,7 +244,7 @@ Store the user's choice as `manual_validation_enabled` (boolean). If any validation fails, re-ask for that specific input. -- **Update TodoWrite**: Mark "PHASE 1: Validate inputs" as completed +- **TaskUpdate**: Mark "PHASE 1: Validate inputs" as completed ### PHASE 1.5: Task Analysis & Decomposition @@ -252,7 +252,7 @@ If any validation fails, re-ask for that specific input. **Step 1: Launch Architect for Task Analysis** -- **Update TodoWrite**: Mark "PHASE 1.5: Analyze and decompose implementation tasks" as in_progress +- **TaskUpdate**: Mark "PHASE 1.5: Analyze and decompose implementation tasks" as in_progress Use Task tool with `subagent_type: frontend:architect`: @@ -410,13 +410,13 @@ If user says "Yes": - Store task plan for execution - Proceed to PHASE 2 -- **Update TodoWrite**: Mark "PHASE 1.5: Analyze and decompose implementation tasks" as completed +- **TaskUpdate**: Mark "PHASE 1.5: Analyze and decompose implementation tasks" as completed ### PHASE 2: Multi-Task Parallel Implementation **CRITICAL: Execute tasks in rounds based on dependencies. Tasks in same round run IN PARALLEL.** -- **Update TodoWrite**: Mark "PHASE 2: Multi-task parallel implementation" as in_progress +- **TaskUpdate**: Mark "PHASE 2: Multi-task parallel implementation" as in_progress **Execution Strategy:** @@ -533,13 +533,13 @@ All three execute in parallel, each working on different files. - If more rounds exist, repeat Step 1 for next round - If all rounds complete, proceed to PHASE 3 -- **Update TodoWrite**: Mark "PHASE 2: Multi-task parallel implementation" as completed +- **TaskUpdate**: Mark "PHASE 2: Multi-task parallel implementation" as completed ### PHASE 3: Per-Task Validation Loops **CRITICAL: Each task gets its own isolated validation loop. Changes to Task 1 won't break Task 2.** -- **Update TodoWrite**: Mark "PHASE 3: Per-task validation and fixing loops" as in_progress +- **TaskUpdate**: Mark "PHASE 3: Per-task validation and fixing loops" as in_progress **For EACH task from the decomposition plan (in execution order):** @@ -879,7 +879,7 @@ Set `current_issues_count` = total consolidated issue count. IF designer assessment is "PASS": - Set `design_fidelity_achieved = true` - Log: "✅ Automated design fidelity validation passed! Component appears to match design reference." -- **Update TodoWrite**: Mark "PHASE 3: Quality gate - ensure design fidelity achieved" as completed +- **TaskUpdate**: Mark "PHASE 3: Quality gate - ensure design fidelity achieved" as completed - **DO NOT exit loop yet** - proceed to Step 3.3.5 for user validation (conditional based on user preference) **Step 3.3.5: User Manual Validation Gate** (Conditional based on user preference) @@ -1275,13 +1275,13 @@ IF `iteration_count < max_iterations` AND NOT `design_fidelity_achieved`: **End of Loop** -- **Update TodoWrite**: Mark "PHASE 3: Start validation and iterative fixing loop" as completed +- **TaskUpdate**: Mark "PHASE 3: Start validation and iterative fixing loop" as completed ### PHASE 4: Final Report & Completion **Step 1: Generate Comprehensive Implementation Report** -- **Update TodoWrite**: Mark "PHASE 4: Generate final implementation report" as in_progress +- **TaskUpdate**: Mark "PHASE 4: Generate final implementation report" as in_progress Create a detailed summary including: @@ -1394,11 +1394,11 @@ npm run dev [Any suggestions for improvement, enhancement, or next steps] ``` -- **Update TodoWrite**: Mark "PHASE 4: Generate final implementation report" as completed +- **TaskUpdate**: Mark "PHASE 4: Generate final implementation report" as completed **Step 2: Present Results to User** -- **Update TodoWrite**: Mark "PHASE 4: Present results and complete handoff" as in_progress +- **TaskUpdate**: Mark "PHASE 4: Present results and complete handoff" as in_progress Present the summary clearly and offer next actions: @@ -1429,7 +1429,7 @@ Would you like to: 4. Review specific issues ``` -- **Update TodoWrite**: Mark "PHASE 4: Present results and complete handoff" as completed +- **TaskUpdate**: Mark "PHASE 4: Present results and complete handoff" as completed **Congratulations! UI implementation workflow completed successfully!** diff --git a/plugins/frontend/commands/implement.md b/plugins/frontend/commands/implement.md index 853a418..2f15365 100644 --- a/plugins/frontend/commands/implement.md +++ b/plugins/frontend/commands/implement.md @@ -1,6 +1,6 @@ --- description: Full-cycle feature implementation with multi-agent orchestration and quality gates -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- ## Mission @@ -15,7 +15,7 @@ Orchestrate a complete feature implementation workflow using specialized agents - Use Task tool to delegate ALL implementation work to agents - Use Bash to run git commands (status, diff, log) - Use Read/Glob/Grep to understand context -- Use TodoWrite to track workflow progress +- Use Tasks to track workflow progress - Use AskUserQuestion for user approval gates - Coordinate agent workflows and feedback loops @@ -482,10 +482,10 @@ Proceeding to workflow initialization... ### STEP 0.1: Initialize Global Workflow Todo List (MANDATORY SECOND STEP) -**BEFORE** starting any phase, you MUST create a global workflow todo list using TodoWrite to track the entire implementation lifecycle: +**BEFORE** starting any phase, you MUST create a global workflow todo list using Tasks to track the entire implementation lifecycle: ``` -TodoWrite with the following items: +TaskCreate with the following items: - content: "PHASE 1: Launch architect for architecture planning" status: "in_progress" activeForm: "PHASE 1: Launching architect for architecture planning" @@ -823,14 +823,14 @@ Call this function at these phase transitions: 9. **After PHASE 6 completes**: `update_session_phase "phase6" "completed"` -**Note**: These calls happen AFTER the TodoWrite updates and BEFORE moving to the next phase. +**Note**: These calls happen AFTER the Tasks updates and BEFORE moving to the next phase. --- ### PHASE 1: Architecture Planning (architect) 1. **Launch Planning Agent**: - - **Update TodoWrite**: Ensure "PHASE 1: Launch architect" is marked as in_progress + - **TaskUpdate**: Ensure "PHASE 1: Launch architect" is marked as in_progress - Use Task tool with `subagent_type: frontend:architect` - **CRITICAL**: Do NOT read large input files yourself - pass file paths to agent - Provide concise prompt following this template: @@ -871,7 +871,7 @@ Call this function at these phase transitions: - Agent will perform gap analysis and ask clarifying questions - Agent will create comprehensive plan in ${SESSION_PATH}/implementation-plan.md - Agent will return brief status summary ONLY (not full plan) - - **Update TodoWrite**: Mark "PHASE 1: Launch architect" as completed + - **TaskUpdate**: Mark "PHASE 1: Launch architect" as completed 2. **Present Plan to User**: - Show the brief status summary from agent @@ -889,7 +889,7 @@ Call this function at these phase transitions: ``` 3. **User Approval Gate**: - - **Update TodoWrite**: Mark "PHASE 1: User approval gate" as in_progress + - **TaskUpdate**: Mark "PHASE 1: User approval gate" as in_progress - Use AskUserQuestion to ask: "Are you satisfied with this architecture plan?" - Options: * "Yes, proceed to implementation" @@ -899,16 +899,16 @@ Call this function at these phase transitions: 4. **Feedback Loop**: - IF user selects "No, I have feedback": * Collect specific feedback - * **Update TodoWrite**: Add "PHASE 1 - Iteration X: Re-run planner with feedback" task + * **TaskUpdate**: Add "PHASE 1 - Iteration X: Re-run planner with feedback" task * Re-run architect with feedback * Repeat approval gate - IF user selects "Get AI review first": - * **Update TodoWrite**: Mark "PHASE 1: User approval gate" as completed + * **TaskUpdate**: Mark "PHASE 1: User approval gate" as completed * **Proceed to Phase 1.5** (multi-model plan review) * After PHASE 1.5 completes, continue to PHASE 2 - IF user selects "Yes, proceed to implementation": - * **Update TodoWrite**: Mark "PHASE 1: User approval gate" as completed - * **Update TodoWrite**: Mark all PHASE 1.5 tasks as completed with note "(Skipped - user chose direct implementation)" + * **TaskUpdate**: Mark "PHASE 1: User approval gate" as completed + * **TaskUpdate**: Mark all PHASE 1.5 tasks as completed with note "(Skipped - user chose direct implementation)" * **Skip PHASE 1.5** and proceed directly to PHASE 2 - **DO NOT proceed without user approval** @@ -928,9 +928,9 @@ Call this function at these phase transitions: **IMPORTANT**: This step is only reached if user selected "Get AI review first" in PHASE 1 approval gate. -**Update TodoWrite**: Mark "PHASE 1.5: Ask user about plan review preference" as completed (already decided in PHASE 1) +**TaskUpdate**: Mark "PHASE 1.5: Ask user about plan review preference" as completed (already decided in PHASE 1) -**Update TodoWrite**: Mark "PHASE 1.5: Run multi-model plan review" as in_progress +**TaskUpdate**: Mark "PHASE 1.5: Run multi-model plan review" as in_progress **1. Load saved preferences from `.claude/settings.json`:** @@ -1178,7 +1178,7 @@ Each reviewer will return a brief verdict. **DO NOT read the review files yourse #### Step 4: Launch Consolidation Agent -**Update TodoWrite**: Mark "PHASE 1.5: Consolidate and present multi-model feedback" as in_progress +**TaskUpdate**: Mark "PHASE 1.5: Consolidate and present multi-model feedback" as in_progress **CRITICAL**: The orchestrator does NOT consolidate reviews - a consolidation agent does this work. @@ -1250,13 +1250,13 @@ ${plan_review_models.map(model => ` - ${SESSION_PATH}/reviews/plan-review/${mo Please review the consolidated report to see detailed findings and recommendations. ``` -**Update TodoWrite**: Mark "PHASE 1.5: Consolidate and present multi-model feedback" as completed +**TaskUpdate**: Mark "PHASE 1.5: Consolidate and present multi-model feedback" as completed --- #### Step 7: Ask User About Plan Revision -**Update TodoWrite**: Mark "PHASE 1.5: User decision on plan revision" as in_progress +**TaskUpdate**: Mark "PHASE 1.5: User decision on plan revision" as in_progress Use **AskUserQuestion**: @@ -1284,7 +1284,7 @@ Options: **IF "Yes - Revise the plan":** 1. **Launch architect agent** to revise plan: - - **Update TodoWrite**: Add "PHASE 1.5: Architect revising plan based on multi-model feedback" + - **TaskUpdate**: Add "PHASE 1.5: Architect revising plan based on multi-model feedback" - Use Task tool with `subagent_type: frontend:architect` - **CRITICAL**: Do NOT read review files yourself - pass paths to architect - Provide concise prompt following this template: @@ -1346,7 +1346,7 @@ Options: - If no, proceed 4. **Once user approves revised plan:** - - **Update TodoWrite**: Mark "PHASE 1.5: User decision on plan revision" as completed + - **TaskUpdate**: Mark "PHASE 1.5: User decision on plan revision" as completed - Proceed to PHASE 2 (Implementation) **IF "No - Proceed with current plan as-is":** @@ -1355,7 +1355,7 @@ Options: 2. **Document acknowledged issues** (for transparency in final report): - Which issues were identified but not addressed - User's rationale for proceeding anyway (if provided) -3. **Update TodoWrite**: Mark "PHASE 1.5: User decision on plan revision" as completed +3. **TaskUpdate**: Mark "PHASE 1.5: User decision on plan revision" as completed 4. Proceed to PHASE 2 (Implementation) **IF "Let me review first":** @@ -1379,7 +1379,7 @@ Options: Skipping plan review and proceeding to implementation. ``` -- **Update TodoWrite**: Mark PHASE 1.5 todos as "Skipped - External AI unavailable" +- **TaskUpdate**: Mark PHASE 1.5 todos as "Skipped - External AI unavailable" - Continue to PHASE 2 **If some models fail but others succeed:** @@ -1452,7 +1452,7 @@ Similar to code review models in PHASE 3, support configuration in `.claude/sett #### Step 1: Load Code Review Preferences and Present Selection -**Update TodoWrite**: Mark "PHASE 1.6: Configure external code reviewers" as in_progress +**TaskUpdate**: Mark "PHASE 1.6: Configure external code reviewers" as in_progress **1. Load saved preferences from `.claude/settings.json`:** @@ -1640,7 +1640,7 @@ Update PHASE 3 todos: - "PHASE 3: Analyze review results" ``` -**Update TodoWrite**: Mark "PHASE 1.6: Configure external code reviewers" as completed +**TaskUpdate**: Mark "PHASE 1.6: Configure external code reviewers" as completed **Log summary**: ``` @@ -1659,7 +1659,7 @@ These reviewers will analyze your implementation in PHASE 3 after the developer ### PHASE 2: Implementation (developer) 1. **Launch Implementation Agent**: - - **Update TodoWrite**: Mark "PHASE 2: Launch developer" as in_progress + - **TaskUpdate**: Mark "PHASE 2: Launch developer" as in_progress - Use Task tool with `subagent_type: frontend:developer` - Provide: * Path to approved plan documentation in ${SESSION_PATH}/ @@ -1671,10 +1671,10 @@ These reviewers will analyze your implementation in PHASE 3 after the developer - Agent implements features following the plan - Agent should document decisions and patterns used - If agent encounters blocking issues, it should report them and request guidance - - **Update TodoWrite**: Mark "PHASE 2: Launch developer" as completed when implementation is done + - **TaskUpdate**: Mark "PHASE 2: Launch developer" as completed when implementation is done 3. **Get Manual Testing Instructions** (NEW STEP): - - **Update TodoWrite**: Mark "PHASE 2: Get manual testing instructions from implementation agent" as in_progress + - **TaskUpdate**: Mark "PHASE 2: Get manual testing instructions from implementation agent" as in_progress - **Launch developer agent** using Task tool with: * Context: "Implementation is complete. Now prepare manual UI testing instructions." * Request: "Create comprehensive, step-by-step manual testing instructions for the implemented features." @@ -1687,7 +1687,7 @@ These reviewers will analyze your implementation in PHASE 3 after the developer - **Success criteria** (what indicates the feature works correctly) * Format: Clear numbered steps that a manual tester can follow without deep page analysis - Agent returns structured testing guide - - **Update TodoWrite**: Mark "PHASE 2: Get manual testing instructions" as completed + - **TaskUpdate**: Mark "PHASE 2: Get manual testing instructions" as completed - Save testing instructions for use by tester agent ### PHASE 2.5: Workflow-Specific Validation (Design Validation OR Test-Driven Loop) @@ -1728,18 +1728,18 @@ These reviewers will analyze your implementation in PHASE 3 after the developer This phase runs ONLY if Figma design links are detected in the feature request or architecture plan. It ensures pixel-perfect UI implementation before code review. **1. Detect Figma Design Links**: - - **Update TodoWrite**: Mark "PHASE 2.5: Detect Figma design links" as in_progress + - **TaskUpdate**: Mark "PHASE 2.5: Detect Figma design links" as in_progress - Use Grep to search for Figma URLs in: * Original feature request (`$ARGUMENTS`) * Architecture plan files (${SESSION_PATH}/*.md) - Figma URL pattern: `https://(?:www\.)?figma\.com/(?:file|design)/[a-zA-Z0-9]+/[^\s?]+(?:\?[^\s]*)?(?:node-id=[0-9-]+)?` - - **Update TodoWrite**: Mark "PHASE 2.5: Detect Figma design links" as completed + - **TaskUpdate**: Mark "PHASE 2.5: Detect Figma design links" as completed **2. Skip Phase if No Figma Links**: - IF no Figma URLs found: * Log: "No Figma design references found. Skipping PHASE 2.5 (Design Fidelity Validation)." - * **Update TodoWrite**: Mark "PHASE 2.5: Run design fidelity validation" as completed with note "Skipped - no design references" - * **Update TodoWrite**: Mark "PHASE 2.5: Quality gate" as completed with note "Skipped - no design references" + * **TaskUpdate**: Mark "PHASE 2.5: Run design fidelity validation" as completed with note "Skipped - no design references" + * **TaskUpdate**: Mark "PHASE 2.5: Quality gate" as completed with note "Skipped - no design references" * Proceed directly to PHASE 3 (Triple Review Loop) **3. Parse Design References** (if Figma links found): @@ -1769,7 +1769,7 @@ This phase runs ONLY if Figma design links are detected in the feature request o - Store user's choice as `manual_validation_enabled` for use in validation loop **6. Run Iterative Design Fidelity Validation Loop**: - - **Update TodoWrite**: Mark "PHASE 2.5: Run design fidelity validation" as in_progress + - **TaskUpdate**: Mark "PHASE 2.5: Run design fidelity validation" as in_progress - For EACH component with a Figma design reference: **Loop (max 3 iterations per component):** @@ -2049,8 +2049,8 @@ This phase runs ONLY if Figma design links are detected in the feature request o * Final assessment (PASS/NEEDS IMPROVEMENT) **6. Quality Gate - All Components Validated**: - - **Update TodoWrite**: Mark "PHASE 2.5: Run design fidelity validation" as completed - - **Update TodoWrite**: Mark "PHASE 2.5: Quality gate - ensure UI matches design" as in_progress + - **TaskUpdate**: Mark "PHASE 2.5: Run design fidelity validation" as completed + - **TaskUpdate**: Mark "PHASE 2.5: Quality gate - ensure UI matches design" as in_progress - IF all components passed design validation (PASS assessment): * Log: "✅ Automated design validation passed for all components" * **DO NOT mark quality gate as completed yet** - proceed to Step 7 for user validation (conditional based on user preference) @@ -2065,7 +2065,7 @@ This phase runs ONLY if Figma design links are detected in the feature request o IF `manual_validation_enabled` is FALSE (user chose "Fully automated"): - Log: "✅ Automated design validation passed for all components! Skipping manual validation per user preference." -- **Update TodoWrite**: Mark "PHASE 2.5: Quality gate" as completed +- **TaskUpdate**: Mark "PHASE 2.5: Quality gate" as completed - Proceed to PHASE 3 (Triple Review Loop) - Skip the rest of this step @@ -2127,7 +2127,7 @@ Options: **If user selects "Yes - All components look perfect":** - Log: "✅ User approved all UI components! Design implementation verified by human review." -- **Update TodoWrite**: Mark "PHASE 2.5: Quality gate" as completed +- **TaskUpdate**: Mark "PHASE 2.5: Quality gate" as completed - Proceed to PHASE 3 (Triple Review Loop) **If user selects "No - I found issues":** @@ -2232,7 +2232,7 @@ Options: **End of Step 7 (User Manual Validation Gate)** - - **Update TodoWrite**: Mark "PHASE 2.5: Quality gate" as completed + - **TaskUpdate**: Mark "PHASE 2.5: Quality gate" as completed **Design Fidelity Validation Summary** (to be included in final report): ```markdown @@ -2288,7 +2288,7 @@ Options: **1. Launch Test-Architect** -- **Update TodoWrite**: Mark "PHASE 2.5: Launch test-architect" as in_progress +- **TaskUpdate**: Mark "PHASE 2.5: Launch test-architect" as in_progress - Use Task tool with `subagent_type: frontend:test-architect` - Provide clear context: ``` @@ -2344,7 +2344,7 @@ Test-architect will return one of four categories: **IF tests revealed implementation issues:** -a. **Update TodoWrite**: Add iteration task: +a. **TaskUpdate**: Add iteration task: ``` - content: "PHASE 2.5 - Iteration X: Fix implementation based on test failures" status: "in_progress" @@ -2380,7 +2380,7 @@ c. **Re-launch Developer** with test feedback: d. **Re-run Tests** after developer fixes: - Re-launch test-architect to run tests again - Provide: "Re-run existing tests to verify fixes" - - **Update TodoWrite**: Mark iteration as completed + - **TaskUpdate**: Mark iteration as completed e. **Loop Until Tests Pass**: - IF still failing: Repeat step 3 (add new iteration) @@ -2389,7 +2389,7 @@ e. **Loop Until Tests Pass**: **4. Quality Gate: Ensure All Tests Pass** -- **Update TodoWrite**: Mark "PHASE 2.5: Quality gate - ensure all tests pass" as in_progress +- **TaskUpdate**: Mark "PHASE 2.5: Quality gate - ensure all tests pass" as in_progress - Verify test-architect output shows `ALL_TESTS_PASS` - Log test summary: ```markdown @@ -2406,7 +2406,7 @@ e. **Loop Until Tests Pass**: **Next Step**: Proceeding to code review (PHASE 3) ``` -- **Update TodoWrite**: Mark "PHASE 2.5: Quality gate" as completed +- **TaskUpdate**: Mark "PHASE 2.5: Quality gate" as completed - **Proceed to PHASE 3** **Test-Driven Feedback Loop Summary** (to be included in final report): @@ -2471,7 +2471,7 @@ e. **Loop Until Tests Pass**: * This array contains OpenRouter model IDs (e.g., `["x-ai/grok-code-fast-1", "openai/gpt-4o"]`) * IF array is empty: Only Claude Sonnet will review (user chose to skip external reviewers) * Store as `external_review_models` for consistency in orchestration - - **Update TodoWrite**: Mark "PHASE 3: Launch reviewers in parallel" as in_progress + - **TaskUpdate**: Mark "PHASE 3: Launch reviewers in parallel" as in_progress * If API_FOCUSED: Update todo text to "Launch X code reviewers in parallel (Claude + {external_review_models.length} external models)" * If UI_FOCUSED or MIXED: Update todo text to "Launch X reviewers in parallel (Claude + {external_review_models.length} external models + UI tester)" - Run `git status` to identify all unstaged changes @@ -2591,8 +2591,8 @@ e. **Loop Until Tests Pass**: 3. **Collect and Analyze Review Results** (Workflow-Adaptive): - **IF API_FOCUSED**: Wait for (1 + external_review_models.length) code reviewers to complete (Claude Sonnet + external models) - **IF UI_FOCUSED or MIXED**: Wait for (1 + external_review_models.length + 1) reviewers to complete (Claude Sonnet + external models + UI tester) - - **Update TodoWrite**: Mark "PHASE 3: Launch reviewers" as completed - - **Update TodoWrite**: Mark "PHASE 3: Analyze review results" as in_progress + - **TaskUpdate**: Mark "PHASE 3: Launch reviewers" as completed + - **TaskUpdate**: Mark "PHASE 3: Analyze review results" as in_progress - **Claude Sonnet Reviewer Feedback**: Document comprehensive findings and recommendations - **For EACH external model** in `external_review_models`: * Document that model's findings and recommendations (via OpenRouter) @@ -2608,17 +2608,17 @@ e. **Loop Until Tests Pass**: - Automated analysis findings (patterns, best practices) - **IF UI_FOCUSED or MIXED**: UI testing findings (runtime behavior, user experience, console errors) * **IF UI_FOCUSED or MIXED**: Cross-reference: UI bugs may reveal code issues, console errors may indicate missing error handling - - **Update TodoWrite**: Mark "PHASE 3: Analyze review results" as completed + - **TaskUpdate**: Mark "PHASE 3: Analyze review results" as completed 4. **Review Feedback Loop** (Workflow-Adaptive): - - **Update TodoWrite**: Mark "PHASE 3: Quality gate - ensure all reviewers approved" as in_progress + - **TaskUpdate**: Mark "PHASE 3: Quality gate - ensure all reviewers approved" as in_progress - IF **ANY** reviewer identifies issues: * Document all feedback clearly from ALL reviewers (2 or 3 depending on workflow) * Categorize and prioritize the combined feedback: - **Code issues** (from reviewer and codex) - **UI/runtime issues** (from tester) - **Console errors** (from tester) - * **Update TodoWrite**: Add "PHASE 3 - Iteration X: Fix issues and re-run reviewers" task + * **TaskUpdate**: Add "PHASE 3 - Iteration X: Fix issues and re-run reviewers" task * **CRITICAL**: Do NOT fix issues yourself - delegate to developer agent * **Launch developer agent** using Task tool with: - Original plan reference (path to ${SESSION_PATH}) @@ -2639,7 +2639,7 @@ e. **Loop Until Tests Pass**: - IF **ALL** reviewers approve (2 or 3 depending on workflow): * **IF API_FOCUSED**: Document that dual code review passed (code review + automated analysis) * **IF UI_FOCUSED or MIXED**: Document that triple review passed (code review + automated analysis + manual UI testing) - * **Update TodoWrite**: Mark "PHASE 3: Quality gate - ensure all reviewers approved" as completed + * **TaskUpdate**: Mark "PHASE 3: Quality gate - ensure all reviewers approved" as completed * Proceed to Phase 4 - **Track loop iterations** (document how many review cycles occurred and feedback from each reviewer) @@ -2651,8 +2651,8 @@ e. **Loop Until Tests Pass**: **For API_FOCUSED workflows:** - **SKIP THIS PHASE ENTIRELY** - All testing completed in PHASE 2.5-B (Test-Driven Feedback Loop) -- **Update TodoWrite**: Mark "PHASE 4: Launch test-architect" as completed with note: "Skipped - API_FOCUSED workflow completed testing in PHASE 2.5" -- **Update TodoWrite**: Mark "PHASE 4: Quality gate - ensure all tests pass" as completed with note: "Already verified in PHASE 2.5" +- **TaskUpdate**: Mark "PHASE 4: Launch test-architect" as completed with note: "Skipped - API_FOCUSED workflow completed testing in PHASE 2.5" +- **TaskUpdate**: Mark "PHASE 4: Quality gate - ensure all tests pass" as completed with note: "Already verified in PHASE 2.5" - Log: "✅ PHASE 4 skipped - API_FOCUSED workflow. All tests already written, executed, and passing from PHASE 2.5." - **Proceed directly to PHASE 5** @@ -2668,7 +2668,7 @@ e. **Loop Until Tests Pass**: --- 1. **Launch Testing Agent**: - - **Update TodoWrite**: Mark "PHASE 4: Launch test-architect" as in_progress + - **TaskUpdate**: Mark "PHASE 4: Launch test-architect" as in_progress - Use Task tool with `subagent_type: frontend:test-architect` - Provide: * Implemented code (reference to files) @@ -2683,12 +2683,12 @@ e. **Loop Until Tests Pass**: 2. **Test Results Analysis**: - Agent writes tests and executes them - Analyzes test results - - **Update TodoWrite**: Mark "PHASE 4: Launch test-architect" as completed - - **Update TodoWrite**: Mark "PHASE 4: Quality gate - ensure all tests pass" as in_progress + - **TaskUpdate**: Mark "PHASE 4: Launch test-architect" as completed + - **TaskUpdate**: Mark "PHASE 4: Quality gate - ensure all tests pass" as in_progress 3. **Test Feedback Loop** (Inner Loop): - IF tests fail due to implementation bugs: - * **Update TodoWrite**: Add "PHASE 4 - Iteration X: Fix implementation bugs and re-test" task + * **TaskUpdate**: Add "PHASE 4 - Iteration X: Fix implementation bugs and re-test" task * Document the test failures and root cause analysis * **CRITICAL**: Do NOT fix bugs yourself - delegate to developer agent * **Launch developer agent** using Task tool with: @@ -2701,11 +2701,11 @@ e. **Loop Until Tests Pass**: * After code review approval, re-run test-architect * Repeat until all tests pass - IF tests fail due to test issues (not implementation): - * **Update TodoWrite**: Add "PHASE 4 - Iteration X: Fix test issues" task + * **TaskUpdate**: Add "PHASE 4 - Iteration X: Fix test issues" task * **Launch test-architect agent** using Task tool to fix the test code * Re-run tests after test fixes - IF all tests pass: - * **Update TodoWrite**: Mark "PHASE 4: Quality gate - ensure all tests pass" as completed + * **TaskUpdate**: Mark "PHASE 4: Quality gate - ensure all tests pass" as completed * Proceed to Phase 5 - **Track loop iterations** (document how many test-fix cycles occurred) @@ -2714,7 +2714,7 @@ e. **Loop Until Tests Pass**: ### PHASE 5: User Review & Project Cleanup 1. **User Final Review Gate**: - - **Update TodoWrite**: Mark "PHASE 5: User approval gate - present implementation for final review" as in_progress + - **TaskUpdate**: Mark "PHASE 5: User approval gate - present implementation for final review" as in_progress - Present the completed implementation to the user: * Summary of what was implemented * All code review approvals received (reviewer + codex) @@ -2730,7 +2730,7 @@ e. **Loop Until Tests Pass**: - IF user not satisfied: * Collect specific feedback on what issues exist - * **Update TodoWrite**: Add "PHASE 5 - Validation Iteration X: User reported issues - running debug flow" task + * **TaskUpdate**: Add "PHASE 5 - Validation Iteration X: User reported issues - running debug flow" task * **Classify issue type**: - **UI Issues**: Visual problems, layout issues, design discrepancies, responsive problems - **Functional Issues**: Bugs, incorrect behavior, missing functionality, errors, performance problems @@ -2741,7 +2741,7 @@ e. **Loop Until Tests Pass**: **UI Issue Debug Flow** (User reports visual/layout/design problems): 1. **Launch Designer Agent**: - - **Update TodoWrite**: Add "UI Debug Flow - Step 1: Designer analysis" task + - **TaskUpdate**: Add "UI Debug Flow - Step 1: Designer analysis" task - Use Task tool with `subagent_type: frontend:designer` - Provide: * User's specific UI feedback @@ -2753,10 +2753,10 @@ e. **Loop Until Tests Pass**: * Provide design guidance * Use browser-debugger skill if needed * Create detailed fix recommendations - - **Update TodoWrite**: Mark "UI Debug Flow - Step 1" as completed after designer returns + - **TaskUpdate**: Mark "UI Debug Flow - Step 1" as completed after designer returns 2. **Launch UI Developer Agent**: - - **Update TodoWrite**: Add "UI Debug Flow - Step 2: UI Developer fixes" task + - **TaskUpdate**: Add "UI Debug Flow - Step 2: UI Developer fixes" task - Use Task tool with `subagent_type: frontend:ui-developer` - Provide: * Designer's feedback and recommendations @@ -2768,10 +2768,10 @@ e. **Loop Until Tests Pass**: * Fix CSS/layout issues * Ensure responsive behavior * Run quality checks - - **Update TodoWrite**: Mark "UI Debug Flow - Step 2" as completed + - **TaskUpdate**: Mark "UI Debug Flow - Step 2" as completed 3. **Launch UI Developer Codex Agent (Optional)**: - - **Update TodoWrite**: Add "UI Debug Flow - Step 3: Codex UI review" task + - **TaskUpdate**: Add "UI Debug Flow - Step 3: Codex UI review" task - Use Task tool with `subagent_type: frontend:ui-developer-codex` - Provide: * Implementation after UI Developer fixes @@ -2781,10 +2781,10 @@ e. **Loop Until Tests Pass**: * Review implementation quality * Check design fidelity * Suggest improvements - - **Update TodoWrite**: Mark "UI Debug Flow - Step 3" as completed + - **TaskUpdate**: Mark "UI Debug Flow - Step 3" as completed 4. **Launch UI Manual Tester Agent**: - - **Update TodoWrite**: Add "UI Debug Flow - Step 4: Browser testing" task + - **TaskUpdate**: Add "UI Debug Flow - Step 4: Browser testing" task - Use Task tool with `subagent_type: frontend:tester` - Provide: * Implementation after fixes @@ -2795,7 +2795,7 @@ e. **Loop Until Tests Pass**: * Check responsive behavior * Verify visual regression * Report any remaining issues - - **Update TodoWrite**: Mark "UI Debug Flow - Step 4" as completed + - **TaskUpdate**: Mark "UI Debug Flow - Step 4" as completed 5. **Present UI Fix Results to User**: - Summary of issues fixed @@ -2812,12 +2812,12 @@ e. **Loop Until Tests Pass**: **Functional Issue Debug Flow** (User reports bugs/errors/incorrect behavior): 1. **Classify Architectural vs Implementation Issue**: - - **Update TodoWrite**: Add "Functional Debug Flow - Classify issue type" task + - **TaskUpdate**: Add "Functional Debug Flow - Classify issue type" task - Determine if this requires architectural changes or just implementation fixes - - **Update TodoWrite**: Mark classification task as completed + - **TaskUpdate**: Mark classification task as completed 2A. **IF Architectural Problem - Launch Architect Agent**: - - **Update TodoWrite**: Add "Functional Debug Flow - Step 1: Architect analysis" task + - **TaskUpdate**: Add "Functional Debug Flow - Step 1: Architect analysis" task - Use Task tool with `subagent_type: frontend:architect` - Provide: * User's functional issue description @@ -2828,15 +2828,15 @@ e. **Loop Until Tests Pass**: * Design architectural fix * Plan implementation approach * Identify affected components - - **Update TodoWrite**: Mark "Functional Debug Flow - Step 1" as completed + - **TaskUpdate**: Mark "Functional Debug Flow - Step 1" as completed - Store architect's plan for next step 2B. **IF Implementation Bug Only - Skip Architect**: - - **Update TodoWrite**: Add note "Functional Debug Flow: Implementation-only bug, architect not needed" + - **TaskUpdate**: Add note "Functional Debug Flow: Implementation-only bug, architect not needed" - Proceed directly to developer 3. **Launch Developer Agent**: - - **Update TodoWrite**: Add "Functional Debug Flow - Step 2: Developer implementation" task + - **TaskUpdate**: Add "Functional Debug Flow - Step 2: Developer implementation" task - Use Task tool with `subagent_type: frontend:developer` - Provide: * User's functional issue description @@ -2848,10 +2848,10 @@ e. **Loop Until Tests Pass**: * Add/update tests * Verify edge cases * Run quality checks - - **Update TodoWrite**: Mark "Functional Debug Flow - Step 2" as completed + - **TaskUpdate**: Mark "Functional Debug Flow - Step 2" as completed 4. **Launch Test Architect Agent**: - - **Update TodoWrite**: Add "Functional Debug Flow - Step 3: Test Architect testing" task + - **TaskUpdate**: Add "Functional Debug Flow - Step 3: Test Architect testing" task - Use Task tool with `subagent_type: frontend:test-architect` - Provide: * Implementation after fix @@ -2863,14 +2863,14 @@ e. **Loop Until Tests Pass**: * Verify coverage * Validate fix approach - **IF Tests FAIL**: - * **Update TodoWrite**: Add "Functional Debug Flow - Iteration: Tests failed, back to developer" task + * **TaskUpdate**: Add "Functional Debug Flow - Iteration: Tests failed, back to developer" task * Loop back to step 3 (Developer) with test failures * Repeat until tests pass - **IF Tests PASS**: Proceed to code review - - **Update TodoWrite**: Mark "Functional Debug Flow - Step 3" as completed + - **TaskUpdate**: Mark "Functional Debug Flow - Step 3" as completed 5. **Launch Code Reviewers in Parallel**: - - **Update TodoWrite**: Add "Functional Debug Flow - Step 4: Dual code review" task + - **TaskUpdate**: Add "Functional Debug Flow - Step 4: Dual code review" task 5A. **Launch Senior Code Reviewer**: - Use Task tool with `subagent_type: frontend:reviewer` @@ -2892,12 +2892,12 @@ e. **Loop Until Tests Pass**: - **Wait for BOTH reviews to complete** - **IF Issues Found in Reviews**: - * **Update TodoWrite**: Add "Functional Debug Flow - Iteration: Address review feedback" task + * **TaskUpdate**: Add "Functional Debug Flow - Iteration: Address review feedback" task * Launch Developer agent to address feedback * Re-run reviews after fixes * Repeat until approved - **IF Approved**: Proceed to present results - - **Update TodoWrite**: Mark "Functional Debug Flow - Step 4" as completed + - **TaskUpdate**: Mark "Functional Debug Flow - Step 4" as completed 6. **Present Functional Fix Results to User**: - Summary of bug fixed @@ -2914,30 +2914,30 @@ e. **Loop Until Tests Pass**: **Mixed Issue Debug Flow** (User reports both UI and functional problems): 1. **Separate Concerns**: - - **Update TodoWrite**: Add "Mixed Debug Flow - Separate UI and functional issues" task + - **TaskUpdate**: Add "Mixed Debug Flow - Separate UI and functional issues" task - Clearly identify which issues are UI vs functional - - **Update TodoWrite**: Mark separation task as completed + - **TaskUpdate**: Mark separation task as completed 2. **Run Functional Debug Flow FIRST**: - - **Update TodoWrite**: Add "Mixed Debug Flow - Track 1: Functional fixes" task + - **TaskUpdate**: Add "Mixed Debug Flow - Track 1: Functional fixes" task - Run complete Functional Issue Debug Flow (steps 1-6 above) - Logic must work before polishing UI - - **Update TodoWrite**: Mark "Mixed Debug Flow - Track 1" as completed + - **TaskUpdate**: Mark "Mixed Debug Flow - Track 1" as completed 3. **Run UI Debug Flow SECOND**: - - **Update TodoWrite**: Add "Mixed Debug Flow - Track 2: UI fixes" task + - **TaskUpdate**: Add "Mixed Debug Flow - Track 2: UI fixes" task - Run complete UI Issue Debug Flow (steps 1-5 above) - Polish and design after functionality works - - **Update TodoWrite**: Mark "Mixed Debug Flow - Track 2" as completed + - **TaskUpdate**: Mark "Mixed Debug Flow - Track 2" as completed 4. **Integration Verification**: - - **Update TodoWrite**: Add "Mixed Debug Flow - Integration testing" task + - **TaskUpdate**: Add "Mixed Debug Flow - Integration testing" task - Use Task tool with `subagent_type: frontend:tester` - Provide: * Both UI and functional fixes implemented * Instruction: "Verify UI and functionality work together end-to-end" - Tester will verify complete user flows - - **Update TodoWrite**: Mark "Mixed Debug Flow - Integration testing" as completed + - **TaskUpdate**: Mark "Mixed Debug Flow - Integration testing" as completed 5. **Present Combined Fix Results to User**: - Summary of ALL issues fixed (UI + functional) @@ -2951,24 +2951,24 @@ e. **Loop Until Tests Pass**: **After ALL Issues Resolved**: - IF user satisfied with ALL fixes: - * **Update TodoWrite**: Mark "PHASE 5: User approval gate - present implementation for final review" as completed - * **Update TodoWrite**: Add "PHASE 5 - Final: All validation loops completed, user approved" task + * **TaskUpdate**: Mark "PHASE 5: User approval gate - present implementation for final review" as completed + * **TaskUpdate**: Add "PHASE 5 - Final: All validation loops completed, user approved" task * Proceed to cleanup (step 3) - IF user has NEW issues: * Restart appropriate debug flow(s) - * **Update TodoWrite**: Add new iteration task + * **TaskUpdate**: Add new iteration task * Repeat until user satisfaction **DO NOT proceed to cleanup without explicit user approval of ALL aspects** - IF user satisfied on first review (no issues): - * **Update TodoWrite**: Mark "PHASE 5: User approval gate - present implementation for final review" as completed + * **TaskUpdate**: Mark "PHASE 5: User approval gate - present implementation for final review" as completed * Proceed to cleanup (step 3) **REMINDER**: You are orchestrating ONLY. You do NOT implement fixes yourself. Always use Task to delegate to specialized agents based on issue type. 3. **Launch Project Cleanup**: - - **Update TodoWrite**: Mark "PHASE 5: Launch cleaner to clean up temporary artifacts" as in_progress + - **TaskUpdate**: Mark "PHASE 5: Launch cleaner to clean up temporary artifacts" as in_progress - Use Task tool with `subagent_type: frontend:cleaner` - Provide context: * The implementation is complete and user-approved @@ -2985,13 +2985,13 @@ e. **Loop Until Tests Pass**: 4. **Cleanup Completion**: - Agent removes temporary files and provides cleanup summary - - **Update TodoWrite**: Mark "PHASE 5: Launch cleaner to clean up temporary artifacts" as completed + - **TaskUpdate**: Mark "PHASE 5: Launch cleaner to clean up temporary artifacts" as completed - Proceed to Phase 6 for final summary ### PHASE 6: Final Summary & Completion 1. **Generate Comprehensive Summary**: - - **Update TodoWrite**: Mark "PHASE 6: Generate comprehensive final summary" as in_progress + - **TaskUpdate**: Mark "PHASE 6: Generate comprehensive final summary" as in_progress Create a detailed summary including: **Implementation Summary:** @@ -3069,14 +3069,14 @@ e. **Loop Until Tests Pass**: - Lines added/removed: [from git diff --stat] - Files cleaned up by cleaner: [number] - - **Update TodoWrite**: Mark "PHASE 6: Generate comprehensive final summary" as completed + - **TaskUpdate**: Mark "PHASE 6: Generate comprehensive final summary" as completed 2. **User Handoff**: - - **Update TodoWrite**: Mark "PHASE 6: Present summary and complete user handoff" as in_progress + - **TaskUpdate**: Mark "PHASE 6: Present summary and complete user handoff" as in_progress - Present summary clearly - Provide next steps or recommendations - Offer to address any remaining concerns - - **Update TodoWrite**: Mark "PHASE 6: Present summary and complete user handoff" as completed + - **TaskUpdate**: Mark "PHASE 6: Present summary and complete user handoff" as completed - **Congratulations! All workflow phases completed successfully!** ## Orchestration Rules @@ -3295,7 +3295,7 @@ CORRECT BEHAVIOR: - Run git commands to understand changes - Read planning docs to gather context - Launch agents with Task tool -- Track progress with TodoWrite +- Track progress with Tasks - Manage quality gates with AskUserQuestion - Present summaries and results to user diff --git a/plugins/frontend/commands/import-figma.md b/plugins/frontend/commands/import-figma.md index 1aaf00f..064b26a 100644 --- a/plugins/frontend/commands/import-figma.md +++ b/plugins/frontend/commands/import-figma.md @@ -1,6 +1,6 @@ --- description: Intelligently clean up temporary artifacts and development files from the project -allowed-tools: Task, TodoWrite, Read, Write, Edit, Glob, Bash, AskUserQuestion, mcp__figma__get_design_context +allowed-tools: Task, TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Glob, Bash, AskUserQuestion, mcp__figma__get_design_context --- # Import Figma Make Component @@ -133,10 +133,10 @@ const MAX_ITERATIONS = 5 ### STEP 1: Initialize Todo Tracking -Use TodoWrite to create a comprehensive task list for tracking progress: +Use Tasks to create a comprehensive task list for tracking progress: ```typescript -TodoWrite({ +TaskCreate({ todos: [ { content: 'Discover project structure', status: 'completed', activeForm: 'Discovering project structure' }, { content: 'Read CLAUDE.md and extract Figma URL', status: 'in_progress', activeForm: 'Reading CLAUDE.md and extracting Figma URL' }, @@ -809,7 +809,7 @@ Check if project uses path alias (@/ or ~/) by reading tsconfig.json or vite.con - **All file paths must be absolute** when using tools (construct using projectRoot + relativePath) - **Use package manager from project** - detect pnpm/npm/yarn by checking lock files - Apply Biome formatting after all file creation/edits -- Keep user informed via TodoWrite updates throughout +- Keep user informed via task updates throughout - Use Task tool only for tester agent (no other agents) - Maximum 5 validation iterations before asking user - Always provide clear, actionable error messages diff --git a/plugins/frontend/commands/review.md b/plugins/frontend/commands/review.md index 07a1783..cc53b69 100644 --- a/plugins/frontend/commands/review.md +++ b/plugins/frontend/commands/review.md @@ -1,6 +1,6 @@ --- description: Multi-model code review orchestrator with parallel execution and consensus analysis -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- @@ -37,7 +37,7 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - Use Task tool to delegate ALL reviews to senior-code-reviewer agent - Use Bash to run git commands (status, diff, log) - Use Read/Glob/Grep to understand context - - Use TodoWrite to track workflow progress (all 5 phases) + - Use Tasks to track workflow progress (all 5 phases) - Use AskUserQuestion for user approval gates - Execute external reviews in PARALLEL (single message, multiple Task calls) @@ -76,10 +76,10 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - You MUST use the TodoWrite tool to create and maintain a todo list throughout + You MUST use the Tasks system to create and maintain a todo list throughout your orchestration workflow. - **Before starting**, create a todo list with all workflow phases: + **Before starting**, create a task list with all workflow phases: 1. PHASE 1: Ask user what to review 2. PHASE 1: Gather review target 3. PHASE 2: Present model selection options @@ -100,7 +100,7 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - Initialize session and TodoWrite with workflow tasks + Initialize session and Tasks with workflow tasks PHASE 1: Determine review target and gather context PHASE 2: Load saved model preferences and select AI models PHASE 3: Execute ALL reviews in parallel @@ -138,7 +138,7 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - Read (read review files) - Glob (expand file patterns) - Grep (search for patterns) - - TodoWrite (track workflow progress) + - Tasks (track workflow progress) - AskUserQuestion (user approval gates) @@ -477,7 +477,7 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep ``` - Initialize TodoWrite with 10 workflow tasks (detailed in todowrite_requirement) + Initialize Tasks with 10 workflow tasks (detailed in todowrite_requirement) @@ -753,7 +753,7 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - Mark PHASE 1 tasks as in_progress in TodoWrite + Mark PHASE 1 tasks as in_progress in task list Ask user what to review (3 options: unstaged/files/commits) Gather review target based on user selection: - Option 1: Run git diff for unstaged changes @@ -768,8 +768,8 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - Full git diff or file contents - Review instructions - Mark PHASE 1 tasks as completed in TodoWrite - Mark PHASE 2 tasks as in_progress in TodoWrite + Mark PHASE 1 tasks as completed in task list + Mark PHASE 2 tasks as in_progress in task list @@ -905,8 +905,8 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - Explain cost factors: review depth, model verbosity, code complexity Get user approval to proceed with costs - Mark PHASE 2 tasks as completed in TodoWrite - Mark PHASE 3 tasks as in_progress in TodoWrite + Mark PHASE 2 tasks as completed in task list + Mark PHASE 3 tasks as in_progress in task list @@ -988,8 +988,8 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep - Calculate `MODEL_DURATION=$((MODEL_END - MODEL_START))` - Count issues from review file: `ISSUES=$(grep -c "^### \|^## MAJOR\|^## MEDIUM\|^## MINOR" review.md || echo 0)` - Mark PHASE 3 tasks as completed in TodoWrite - Mark PHASE 4 tasks as in_progress in TodoWrite + Mark PHASE 3 tasks as completed in task list + Mark PHASE 4 tasks as in_progress in task list @@ -1011,7 +1011,7 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep Read all review files using Read tool (${SESSION_PATH}/reviews/*.md) - Mark read task as completed in TodoWrite + Mark read task as completed in task list Parse issues from each review (critical/medium/low severity) Normalize issue descriptions for comparison: - Extract category (Security/Performance/Type Safety/etc.) @@ -1086,8 +1086,8 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep This accumulates historical data across all review sessions in `ai-docs/llm-performance.json`. - Mark PHASE 4 tasks as completed in TodoWrite - Mark PHASE 5 task as in_progress in TodoWrite + Mark PHASE 4 tasks as completed in task list + Mark PHASE 5 task as in_progress in task list @@ -1190,7 +1190,7 @@ allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep Present summary to user (under 50 lines excluding stats table) - Mark PHASE 5 task as completed in TodoWrite + Mark PHASE 5 task as completed in task list @@ -1688,7 +1688,7 @@ for each issue: ✅ Parallel execution achieves 3-5x speedup on external reviews ✅ Graceful degradation works (embedded-only path functional) ✅ Clear error messages and recovery options for all failure scenarios - ✅ TodoWrite tracking shows progress through all 5 phases + ✅ task tracking shows progress through all 5 phases ✅ Consensus algorithm uses simplified keyword-based approach with confidence levels diff --git a/plugins/frontend/skills/api-integration/SKILL.md b/plugins/frontend/skills/api-integration/SKILL.md index 06d3b15..f22ba1c 100644 --- a/plugins/frontend/skills/api-integration/SKILL.md +++ b/plugins/frontend/skills/api-integration/SKILL.md @@ -385,8 +385,8 @@ export function useCreateTodo() { } // 4. Component -// src/features/todos/TodoList.tsx -export function TodoList() { +// src/features/todos/TaskList.tsx +export function TaskList() { const { data: todos } = useQuery(todosQueryOptions()) const createTodo = useCreateTodo() diff --git a/plugins/frontend/skills/react-patterns/SKILL.md b/plugins/frontend/skills/react-patterns/SKILL.md index 63111d2..a645b8b 100644 --- a/plugins/frontend/skills/react-patterns/SKILL.md +++ b/plugins/frontend/skills/react-patterns/SKILL.md @@ -133,7 +133,7 @@ function TodoForm() { ```typescript import { useOptimistic } from 'react' -function TodoList({ initialTodos }: { initialTodos: Todo[] }) { +function TaskList({ initialTodos }: { initialTodos: Todo[] }) { const [optimisticTodos, addOptimisticTodo] = useOptimistic( initialTodos, (state, newTodo: string) => [ diff --git a/plugins/frontend/skills/tanstack-query/SKILL.md b/plugins/frontend/skills/tanstack-query/SKILL.md index 63cf793..7dd85da 100644 --- a/plugins/frontend/skills/tanstack-query/SKILL.md +++ b/plugins/frontend/skills/tanstack-query/SKILL.md @@ -345,7 +345,7 @@ const { data } = usePost(42, { staleTime: 10_000 }) **Layer 1: Component-Level** - Specific user feedback: ```typescript -function TodoList() { +function TaskList() { const { data, error, isError, isLoading } = useQuery({ queryKey: ['todos'], queryFn: fetchTodos, @@ -388,7 +388,7 @@ import { ErrorBoundary } from 'react-error-boundary' )} > - + )} @@ -401,7 +401,7 @@ import { ErrorBoundary } from 'react-error-boundary' ```typescript import { useSuspenseQuery } from '@tanstack/react-query' -function TodoList() { +function TaskList() { // data is NEVER undefined (type-safe) const { data } = useSuspenseQuery({ queryKey: ['todos'], @@ -415,7 +415,7 @@ function TodoList() { function App() { return ( }> - + ) } @@ -815,7 +815,7 @@ import { renderWithClient } from '@/test/utils' import { screen } from '@testing-library/react' test('displays todos', async () => { - renderWithClient() + renderWithClient() // Wait for data to load expect(await screen.findByText('Test todo')).toBeInTheDocument() @@ -832,7 +832,7 @@ test('shows error state', async () => { }) ) - renderWithClient() + renderWithClient() expect(await screen.findByText(/failed/i)).toBeInTheDocument() }) diff --git a/plugins/frontend/skills/ui-implementer/SKILL.md b/plugins/frontend/skills/ui-implementer/SKILL.md index d5d8b54..0f61680 100644 --- a/plugins/frontend/skills/ui-implementer/SKILL.md +++ b/plugins/frontend/skills/ui-implementer/SKILL.md @@ -1,7 +1,7 @@ --- name: ui-implementer description: Implements UI components from scratch based on design references (Figma, screenshots, mockups) with intelligent validation and adaptive agent switching. Use when user provides a design and wants pixel-perfect UI implementation with design fidelity validation. Triggers automatically when user mentions Figma links, design screenshots, or wants to implement UI from designs. -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep --- # UI Implementer @@ -49,7 +49,7 @@ This Skill implements the same workflow as the `/implement-ui` command. Follow t Create a global todo list to track progress: ``` -TodoWrite with: +TaskCreate: - PHASE 1: Gather inputs (design reference, component description, preferences) - PHASE 1: Validate inputs and find target location - PHASE 2: Launch UI Developer for initial implementation diff --git a/plugins/instantly/agents/campaign-analyst.md b/plugins/instantly/agents/campaign-analyst.md index f6b40b4..d0f2f05 100644 --- a/plugins/instantly/agents/campaign-analyst.md +++ b/plugins/instantly/agents/campaign-analyst.md @@ -10,8 +10,8 @@ description: | (5) "What's my bounce rate across campaigns?" - deliverability health check model: sonnet color: cyan -tools: TodoWrite, Read, Write, Bash, AskUserQuestion -skills: instantly:campaign-metrics, orchestration:todowrite-orchestration +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, AskUserQuestion +skills: instantly:campaign-metrics, orchestration:task-orchestration --- @@ -71,7 +71,7 @@ skills: instantly:campaign-metrics, orchestration:todowrite-orchestration - You MUST use TodoWrite to track your analysis workflow: + You MUST use Tasks to track your analysis workflow: 1. Fetch campaign data via MCP 2. Calculate performance metrics 3. Identify patterns and trends @@ -146,7 +146,7 @@ skills: instantly:campaign-metrics, orchestration:todowrite-orchestration - Initialize TodoWrite with analysis phases + Initialize Tasks with analysis phases Mark PHASE 1 as in_progress Fetch campaign list via MCP get_campaign_summary Fetch detailed analytics via MCP get_campaign_analytics for target campaigns @@ -230,7 +230,7 @@ skills: instantly:campaign-metrics, orchestration:todowrite-orchestration Analyze my "SaaS Founders Q1" campaign performance - 1. Initialize TodoWrite with 5 phases + 1. Initialize Tasks with 5 phases 2. Fetch campaign data via MCP get_campaign_analytics for "SaaS Founders Q1" 3. Calculate metrics: - Sent: 2,500 | Opened: 1,125 (45%) | Replied: 175 (7%) @@ -252,7 +252,7 @@ skills: instantly:campaign-metrics, orchestration:todowrite-orchestration Compare my Agency Outreach and SaaS Founders campaigns - 1. Initialize TodoWrite with 5 phases + 1. Initialize Tasks with 5 phases 2. Fetch analytics for both campaigns via MCP 3. Build comparison matrix: | Metric | Agency Outreach | SaaS Founders | Winner | @@ -272,7 +272,7 @@ skills: instantly:campaign-metrics, orchestration:todowrite-orchestration Check the deliverability health across all my campaigns - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Fetch all campaign summaries 3. For each campaign, check: - Bounce rate (flag if >2%) diff --git a/plugins/instantly/agents/outreach-optimizer.md b/plugins/instantly/agents/outreach-optimizer.md index fc71d3d..bd2a23d 100644 --- a/plugins/instantly/agents/outreach-optimizer.md +++ b/plugins/instantly/agents/outreach-optimizer.md @@ -10,7 +10,7 @@ description: | (5) "Analyze my A/B test results" - statistical significance check model: sonnet color: orange -tools: TodoWrite, Read, Write, Bash, AskUserQuestion +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, AskUserQuestion skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration:multi-model-validation --- @@ -71,7 +71,7 @@ skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration - You MUST use TodoWrite to track optimization workflow: + You MUST use Tasks to track optimization workflow: 1. Analyze current performance 2. Identify optimization opportunities 3. Design A/B test or improvement @@ -160,7 +160,7 @@ skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration - Initialize TodoWrite with optimization phases + Initialize Tasks with optimization phases Mark PHASE 1 as in_progress Fetch campaign analytics via MCP Calculate current performance vs benchmarks @@ -264,7 +264,7 @@ skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration My open rate is 22%, help me improve it - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Fetch current campaign data via MCP 3. Analyze: 22% open rate (below 25-40% average benchmark) 4. Diagnose: Subject line is likely the issue @@ -294,7 +294,7 @@ skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration Good opens but terrible reply rate, what's wrong? - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Fetch analytics: 45% opens, 1.5% replies 3. Diagnose: Subject line works, body copy is the issue 4. Analyze current email body for issues: @@ -313,7 +313,7 @@ skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration Run a health check on my active campaigns - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Fetch all active campaign analytics 3. Check each against critical thresholds: - Bounce rate >5%: WARNING diff --git a/plugins/instantly/agents/sequence-builder.md b/plugins/instantly/agents/sequence-builder.md index 3d77824..d54ef3d 100644 --- a/plugins/instantly/agents/sequence-builder.md +++ b/plugins/instantly/agents/sequence-builder.md @@ -10,7 +10,7 @@ description: | (5) "Build a breakup sequence" - final follow-up sequence design model: sonnet color: green -tools: TodoWrite, Read, Write, Bash, AskUserQuestion +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, AskUserQuestion skills: instantly:sequence-best-practices, instantly:email-deliverability --- @@ -71,7 +71,7 @@ skills: instantly:sequence-best-practices, instantly:email-deliverability - You MUST use TodoWrite to track sequence building: + You MUST use Tasks to track sequence building: 1. Gather campaign context and ICP 2. Design sequence structure 3. Write email templates @@ -170,7 +170,7 @@ skills: instantly:sequence-best-practices, instantly:email-deliverability - Initialize TodoWrite with building phases + Initialize Tasks with building phases Mark PHASE 1 as in_progress Use AskUserQuestion to gather: - Target audience (ICP) @@ -267,7 +267,7 @@ skills: instantly:sequence-best-practices, instantly:email-deliverability Create a sequence for B2B SaaS targeting marketing directors - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Ask clarifying questions: - "What does your SaaS do?" - "What's your main value proposition?" @@ -298,7 +298,7 @@ skills: instantly:sequence-best-practices, instantly:email-deliverability Build a cold email sequence for my design agency targeting startup founders - 1. Initialize TodoWrite with 5 phases + 1. Initialize Tasks with 5 phases 2. Gather context via AskUserQuestion: - Services offered (UI/UX, branding, web design) - Key differentiator (speed, quality, startup experience) diff --git a/plugins/instantly/commands/ab-test.md b/plugins/instantly/commands/ab-test.md index 9c18527..7c914f4 100644 --- a/plugins/instantly/commands/ab-test.md +++ b/plugins/instantly/commands/ab-test.md @@ -4,8 +4,8 @@ description: | A/B testing workflow for email optimization. Design, run, and analyze A/B tests on subject lines, copy, and timing. Workflow: ANALYZE -> DESIGN TEST -> APPROVE -> IMPLEMENT -> MONITOR -allowed-tools: Task, AskUserQuestion, Read, TodoWrite -skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Read, TaskCreate, TaskUpdate, TaskList, TaskGet +skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration:task-orchestration --- @@ -39,7 +39,7 @@ skills: instantly:ab-testing-patterns, instantly:campaign-metrics, orchestration - Use TodoWrite to track: + Use Tasks to track: 1. Identify optimization opportunity 2. Design A/B test 3. Get user approval diff --git a/plugins/instantly/commands/analytics.md b/plugins/instantly/commands/analytics.md index 8b18795..0f08362 100644 --- a/plugins/instantly/commands/analytics.md +++ b/plugins/instantly/commands/analytics.md @@ -4,8 +4,8 @@ description: | Campaign performance analytics and reporting. Fetches data from Instantly MCP, calculates KPIs, identifies trends. Workflow: DATA FETCH -> METRICS CALCULATION -> PATTERN ANALYSIS -> REPORT -allowed-tools: Task, Bash, Read, TodoWrite, AskUserQuestion -skills: instantly:campaign-metrics, orchestration:todowrite-orchestration +allowed-tools: Task, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion +skills: instantly:campaign-metrics, orchestration:task-orchestration --- @@ -42,7 +42,7 @@ skills: instantly:campaign-metrics, orchestration:todowrite-orchestration - Use TodoWrite to track: + Use Tasks to track: 1. Parse user request 2. Launch campaign-analyst agent 3. Receive and present results @@ -81,7 +81,7 @@ skills: instantly:campaign-metrics, orchestration:todowrite-orchestration - Initialize TodoWrite + Initialize Tasks Parse arguments for campaign name or scope If no campaign specified, analyze all campaigns diff --git a/plugins/instantly/commands/leads.md b/plugins/instantly/commands/leads.md index b360ed1..5140383 100644 --- a/plugins/instantly/commands/leads.md +++ b/plugins/instantly/commands/leads.md @@ -4,8 +4,8 @@ description: | Lead management for Instantly campaigns. Add, import, move, and manage leads across campaigns. Workflow: IDENTIFY ACTION -> VALIDATE -> EXECUTE -> CONFIRM -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite -skills: instantly:email-deliverability, orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet +skills: instantly:email-deliverability, orchestration:task-orchestration --- diff --git a/plugins/instantly/commands/sequence.md b/plugins/instantly/commands/sequence.md index a3cdf7e..ff24b2d 100644 --- a/plugins/instantly/commands/sequence.md +++ b/plugins/instantly/commands/sequence.md @@ -4,8 +4,8 @@ description: | Create new cold email sequences for Instantly campaigns. Interactive workflow for designing multi-step email sequences. Workflow: CONTEXT GATHERING -> SEQUENCE DESIGN -> REVIEW -> CREATE -allowed-tools: Task, AskUserQuestion, Read, TodoWrite -skills: instantly:sequence-best-practices, orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Read, TaskCreate, TaskUpdate, TaskList, TaskGet +skills: instantly:sequence-best-practices, orchestration:task-orchestration --- @@ -43,7 +43,7 @@ skills: instantly:sequence-best-practices, orchestration:todowrite-orchestration - Use TodoWrite to track: + Use Tasks to track: 1. Gather campaign context 2. Launch sequence-builder agent 3. Present sequence for review diff --git a/plugins/instantly/commands/start.md b/plugins/instantly/commands/start.md index 8088dd8..2340ecf 100644 --- a/plugins/instantly/commands/start.md +++ b/plugins/instantly/commands/start.md @@ -4,8 +4,8 @@ description: | Interactive entry point for Instantly cold outreach workflows. Routes users to appropriate commands based on their goals. Workflow: GOAL DISCOVERY -> REFINEMENT -> ROUTING -> EXECUTION -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite -skills: orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet +skills: orchestration:task-orchestration --- @@ -51,7 +51,7 @@ skills: orchestration:todowrite-orchestration - Use TodoWrite to track workflow: + Use Tasks to track workflow: 1. Understand user goal 2. Route to appropriate command or workflow 3. Monitor execution (if multi-step) @@ -90,7 +90,7 @@ skills: orchestration:todowrite-orchestration Understand what the user wants to accomplish - Initialize TodoWrite with workflow phases + Initialize Tasks with workflow phases Mark PHASE 1 as in_progress Check if user provided arguments with clear intent If clear intent: Skip to routing (Phase 2) diff --git a/plugins/multimodel/commands/team.md b/plugins/multimodel/commands/team.md index 2c7bfc9..331d259 100644 --- a/plugins/multimodel/commands/team.md +++ b/plugins/multimodel/commands/team.md @@ -5,7 +5,7 @@ description: | collects independent votes (APPROVE/REJECT), and presents aggregated verdicts with performance tracking. Examples: "/team Review auth implementation", "/team --models grok,gemini Check API security", "/team --threshold unanimous Validate migration plan" -allowed-tools: Read, Write, Bash, Task, TodoWrite, Glob, Grep, AskUserQuestion +allowed-tools: Read, Write, Bash, Task, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep, AskUserQuestion model: sonnet args: - name: task @@ -45,7 +45,7 @@ args: - You MUST use TodoWrite to track the 5-phase workflow: + You MUST use Tasks to track the 5-phase workflow: 1. Setup and Configuration 2. User Confirmation 3. Parallel Execution diff --git a/plugins/multimodel/skills/batching-patterns/SKILL.md b/plugins/multimodel/skills/batching-patterns/SKILL.md index d0ba221..be90c13 100644 --- a/plugins/multimodel/skills/batching-patterns/SKILL.md +++ b/plugins/multimodel/skills/batching-patterns/SKILL.md @@ -52,7 +52,7 @@ Same tool type in one message = PARALLEL Task(A) + Task(B) + Task(C) → All run simultaneously Different tool types in one message = SEQUENTIAL (often) - TodoWrite(...) + Task(A) + Bash(...) → May run one at a time + TaskCreate(...) + Task(A) + Bash(...) → May run one at a time Separate messages = ALWAYS SEQUENTIAL Message 1: Task(A) → completes first @@ -118,20 +118,19 @@ Agents are independent when they: read same input but don't modify it, write to Rule: Different files = safe to batch. Same file = must be sequential. ``` -### TodoWrite Batching +### Tasks Batching ``` ❌ Individual Calls (5 round-trips): - TodoWrite([{ id: "1", content: "Step 1", status: "pending" }]) - TodoWrite([{ id: "2", content: "Step 2", status: "pending" }]) + TaskCreate({ id: "1", title: "Step 1", status: "pending" }) + TaskCreate({ id: "2", title: "Step 2", status: "pending" }) ... ✅ Single Call (1 round-trip): - TodoWrite([ - { id: "1", content: "Step 1", status: "pending" }, - { id: "2", content: "Step 2", status: "pending" }, - { id: "3", content: "Step 3", status: "pending" } - ]) + TaskCreate({ id: "1", title: "Step 1", status: "pending" }) + TaskCreate({ id: "2", title: "Step 2", status: "pending" }) + TaskCreate({ id: "3", title: "Step 3", status: "pending" }) + # All in same message = parallel execution ``` ### Bash Batching @@ -158,7 +157,7 @@ The canonical batching template from multi-agent-coordination: ``` Message 1: Preparation (Bash/Write only) - Create directories, write context files, validate inputs - - NO Task calls, NO TodoWrite + - NO Task calls, NO Tasks Message 2: Parallel Execution (Task only) - ALL agents in SINGLE message, ONLY Task calls @@ -193,21 +192,21 @@ Message 4: Present Results ``` ❌ Mixed Tools (sequential): - TodoWrite([...]) // Tool type A + TaskCreate({...}) // Tool type A Task(security-reviewer) // Tool type B Bash("echo 'starting'") // Tool type C Task(perf-reviewer) // Tool type B ✅ Separated (parallel execution): - Message 1: TodoWrite([...]) + Bash("echo 'starting'") // Preparation + Message 1: TaskCreate({...}) + Bash("echo 'starting'") // Preparation Message 2: Task(security-reviewer) + Task(perf-reviewer) // Execution (parallel) ``` -### Anti-Pattern 3: Individual TodoWrite Calls +### Anti-Pattern 3: Individual Tasks Calls ``` -❌ 5 separate TodoWrite calls = 5 round-trips -✅ 1 TodoWrite call with all items = 1 round-trip +❌ 5 separate TaskCreate calls across messages = 5 round-trips +✅ 5 TaskCreate calls in 1 message = 1 round-trip (parallel) ``` ### Anti-Pattern 4: Sequential File Reads @@ -291,7 +290,7 @@ Speedup = approximately N (for identical operations) - ✅ Launch ALL independent agents in a single message (biggest speedup) - ✅ Read all needed files in one message before processing - ✅ Run all independent searches (Grep + Glob) in parallel -- ✅ Create all TodoWrite items in a single call +- ✅ Create all task items in a single message - ✅ Use the same tool type for parallel operations - ✅ Check the dependency checklist before splitting across messages - ✅ Follow the 4-Message Pattern for multi-agent workflows @@ -301,7 +300,7 @@ Speedup = approximately N (for identical operations) - ❌ Launch agents in separate messages (forces sequential) - ❌ Mix tool types in execution messages (breaks parallelism) - ❌ Read files one at a time across separate messages -- ❌ Create individual TodoWrite calls for each item +- ❌ Create individual TaskCreate calls across separate messages - ❌ Batch operations that write to the same file - ❌ Batch operations where B needs A's output - ❌ Assume all operations can be batched (check dependencies) diff --git a/plugins/multimodel/skills/hierarchical-coordinator/SKILL.md b/plugins/multimodel/skills/hierarchical-coordinator/SKILL.md index cc1723e..f46e78d 100644 --- a/plugins/multimodel/skills/hierarchical-coordinator/SKILL.md +++ b/plugins/multimodel/skills/hierarchical-coordinator/SKILL.md @@ -142,7 +142,7 @@ Full Coordinator Workflow: Step 1: Initialize coordinator context Write ai-docs/coordinator-context.md (requirements, criteria, scope) -Step 2: Initialize TodoWrite (all phases visible upfront) +Step 2: Initialize Tasks (all phases visible upfront) [ ] PHASE 1: [Architecture/Planning] [ ] CHECKPOINT 1: Validate Phase 1 alignment [ ] PHASE 2: [Implementation] @@ -347,14 +347,14 @@ Total workflow corrections: Maximum 5 --- -## Shared State via TodoWrite +## Shared State via Tasks ### Cross-Agent State Management -TodoWrite serves as the coordinator's shared state mechanism. Beyond progress tracking, it carries context between phases: +Tasks serves as the coordinator's shared state mechanism. Beyond progress tracking, it carries context between phases: ``` -TodoWrite as Shared State: +Tasks as Shared State: Standard progress tracking: [ ] PHASE 1: Architecture planning @@ -373,7 +373,7 @@ Enhanced with coordinator state: Use prefixed entries to distinguish state types: ``` -TodoWrite State Prefixes: +Tasks State Prefixes: PHASE: - Standard phase tracking CHECKPOINT: - Coordinator validation point @@ -381,7 +381,7 @@ CONTEXT: - Shared context between agents DRIFT: - Drift detection result CORRECTION: - Corrective action applied -Example TodoWrite State: +Example Tasks State: [x] PHASE 1: Architecture planning [x] CHECKPOINT 1: ALIGNED (3/3 criteria met) @@ -504,7 +504,7 @@ Gate passes when ALL THREE dimensions are satisfied. PROCEED: All criteria met. Move to next phase. Log: "Gate N passed. Proceeding to Phase N+1." - Update TodoWrite: Mark CHECKPOINT N as completed. + TaskUpdate: Mark CHECKPOINT N as completed. RETRY: One or more criteria not met, but recoverable. @@ -815,7 +815,7 @@ Write: ai-docs/coordinator-context.md IN SCOPE: Pagination, cursor navigation, total count, page size OUT OF SCOPE: Sorting, filtering, search, new endpoints -TodoWrite: +Tasks: [ ] PHASE 1: Architecture planning [ ] CHECKPOINT 1: Validate architecture alignment [ ] PHASE 2: Implementation @@ -956,7 +956,7 @@ Write: ai-docs/coordinator-context.md IN SCOPE: SQL injection in auth module only OUT OF SCOPE: XSS, CSRF, other modules, general code quality -TodoWrite: +Tasks: [ ] PHASE 1: Gather auth module context [ ] CHECKPOINT 1: Validate context completeness [ ] PHASE 2a: Security reviewer (SQL injection focus) @@ -1035,7 +1035,7 @@ Write: ai-docs/coordinator-context.md IN SCOPE: Strategy pattern refactoring of payment providers OUT OF SCOPE: New payment providers, API changes, new features -TodoWrite: +Tasks: [ ] PHASE 1: Impact analysis [ ] CHECKPOINT 1: Validate analysis completeness [ ] PHASE 2: Interface design @@ -1184,7 +1184,7 @@ The hierarchical coordinator prevents goal drift through: - **Drift detection** (ALIGNED, MINOR_DRIFT, MAJOR_DRIFT, OFF_TRACK) - **Corrective actions** (specific guidance to fix drift before next phase) - **Phase gates** (formal proceed/retry/abort decisions) -- **Shared state** (TodoWrite + files for cross-agent context) +- **Shared state** (Tasks + files for cross-agent context) - **Escalation limits** (max re-runs and corrections before user intervention) The overhead is 2-6 minutes per workflow, but prevents 30-60 minutes of rework from undetected drift. Use this pattern for any workflow with 3+ agents where the final output must precisely match the original request. @@ -1196,4 +1196,4 @@ The overhead is 2-6 minutes per workflow, but prevents 30-60 minutes of rework f - `/implement` command multi-phase workflows - `/review` command validation patterns - quality-gates skill (extended with drift awareness) -- todowrite-orchestration skill (enhanced with coordinator state) +- task-orchestration skill (enhanced with coordinator state) diff --git a/plugins/multimodel/skills/model-tracking-protocol/SKILL.md b/plugins/multimodel/skills/model-tracking-protocol/SKILL.md index 86f0566..23c1889 100644 --- a/plugins/multimodel/skills/model-tracking-protocol/SKILL.md +++ b/plugins/multimodel/skills/model-tracking-protocol/SKILL.md @@ -933,17 +933,17 @@ fi verify_output_complete "$OUTPUT" || exit 1 ``` -### With `todowrite-orchestration` +### With `task-orchestration` Track progress through multi-model phases: ``` -TodoWrite: -1. Pre-launch setup (tracking protocol) -2. Launch models (validation patterns) -3. Collect results (tracking updates) -4. Consensus analysis (protocol requirement) -5. Present results (protocol template) +Tasks: +1. [~] Pre-launch setup (tracking protocol) +2. [ ] Launch models (validation patterns) +3. [ ] Collect results (tracking updates) +4. [ ] Consensus analysis (protocol requirement) +5. [ ] Present results (protocol template) ``` --- diff --git a/plugins/multimodel/skills/multi-agent-coordination/SKILL.md b/plugins/multimodel/skills/multi-agent-coordination/SKILL.md index 3cf4e30..7614a14 100644 --- a/plugins/multimodel/skills/multi-agent-coordination/SKILL.md +++ b/plugins/multimodel/skills/multi-agent-coordination/SKILL.md @@ -94,7 +94,7 @@ Message 1: Preparation (Bash Only) - Create workspace directories - Validate inputs - Write context files - - NO Task calls, NO TodoWrite + - NO Task calls, NO Tasks Message 2: Parallel Execution (Task Only) - Launch ALL agents in SINGLE message @@ -115,8 +115,8 @@ Message 4: Present Results ``` ❌ WRONG - Executes Sequentially: - await TodoWrite({...}); // Tool 1 - await Task({...}); // Tool 2 - waits for TodoWrite + await TaskCreate({...}); // Tool 1 + await Task({...}); // Tool 2 - waits for Tasks await Bash({...}); // Tool 3 - waits for Task await Task({...}); // Tool 4 - waits for Bash @@ -457,19 +457,19 @@ Step 3: User Validation Gate (quality-gates) - Collect feedback if issues found ``` -**multi-agent-coordination + todowrite-orchestration:** +**multi-agent-coordination + task-orchestration:** ``` Use Case: Multi-phase implementation workflow -Step 1: Initialize TodoWrite (todowrite-orchestration) +Step 1: Initialize Tasks (task-orchestration) - Create task list for all phases Step 2: Sequential Agent Delegation (multi-agent-coordination) - Phase 1: api-architect - Phase 2: backend-developer (depends on Phase 1) - Phase 3: test-architect (depends on Phase 2) - - Update TodoWrite after each phase + - TaskUpdate after each phase ``` --- @@ -656,7 +656,7 @@ Solution: Use 4-Message Pattern with ONLY Task calls in Message 2 ``` ❌ Wrong: - await TodoWrite({...}); + await TaskCreate({...}); await Task({...}); await Task({...}); diff --git a/plugins/multimodel/skills/multi-model-validation/SKILL.md b/plugins/multimodel/skills/multi-model-validation/SKILL.md index 7666df9..dd06a92 100644 --- a/plugins/multimodel/skills/multi-model-validation/SKILL.md +++ b/plugins/multimodel/skills/multi-model-validation/SKILL.md @@ -128,7 +128,7 @@ Task: "Debug this error, use different models" - Failure documentation format - Results presentation template - **orchestration:quality-gates** - Approval gates and severity classification -- **orchestration:todowrite-orchestration** - Progress tracking during execution +- **orchestration:task-orchestration** - Progress tracking during execution - **orchestration:error-recovery** - Handling failures and retries **Skill Integration:** @@ -444,7 +444,7 @@ Message 1: Preparation (Bash Only) - Validate inputs (check if claudish installed) - Write context files (code to review, design reference, etc.) - NO Task calls - - NO TodoWrite calls + - NO Tasks calls Message 2: Parallel Execution (Task Only) - Launch ALL AI models in SINGLE message @@ -1845,12 +1845,12 @@ Step 4: Consolidation (multi-model-validation) Apply consensus analysis ``` -**multi-model-validation + todowrite-orchestration:** +**multi-model-validation + task-orchestration:** ``` Use Case: Real-time progress tracking during parallel execution -Step 1: Initialize TodoWrite (todowrite-orchestration) +Step 1: Initialize Tasks (task-orchestration) Tasks: 1. Prepare workspace 2. Launch Claude review @@ -1860,7 +1860,7 @@ Step 1: Initialize TodoWrite (todowrite-orchestration) 6. Consolidate reviews 7. Present results -Step 2: Update Progress (todowrite-orchestration) +Step 2: Update Progress (task-orchestration) Mark tasks complete as models finish: - Claude completes → Mark task 2 complete - Grok completes → Mark task 3 complete @@ -2104,12 +2104,12 @@ Solution: Use ONLY Task calls in Message 2 ``` ❌ Wrong: Message 2: - TodoWrite({...}) + TaskCreate({...}) Task({...}) Task({...}) ✅ Correct: - Message 1: TodoWrite({...}) (separate message) + Message 1: TaskCreate({...}) (separate message) Message 2: Task({...}); Task({...}) (only Task) ``` diff --git a/plugins/multimodel/skills/task-orchestration/SKILL.md b/plugins/multimodel/skills/task-orchestration/SKILL.md new file mode 100644 index 0000000..f651e71 --- /dev/null +++ b/plugins/multimodel/skills/task-orchestration/SKILL.md @@ -0,0 +1,1424 @@ +--- +name: task-orchestration +description: Track progress in multi-phase workflows with Tasks system. Use when orchestrating 5+ phase commands, managing iteration loops, tracking parallel tasks, or providing real-time progress visibility. Trigger keywords - "phase tracking", "progress", "workflow", "multi-step", "multi-phase", "tasks", "tracking", "status". +version: 2.0.0 +tags: [orchestration, tasks, progress, tracking, workflow, multi-phase] +keywords: [phase-tracking, progress, workflow, multi-step, multi-phase, tasks, tracking, status, visibility] +plugin: multimodel +updated: 2026-01-31 +--- + +# Task Orchestration + +**Version:** 2.0.0 +**Purpose:** Patterns for using Tasks system in complex multi-phase workflows +**Status:** Production Ready + +## Overview + +Task orchestration is the practice of using the Tasks system (TaskCreate, TaskUpdate, TaskList, TaskGet) to provide **real-time progress visibility** in complex multi-phase workflows. It transforms opaque "black box" workflows into transparent, trackable processes where users can see: + +- What phase is currently executing +- How many phases remain +- Which tasks are pending, in-progress, or completed +- Overall progress percentage +- Iteration counts in loops +- Task dependencies and blocking relationships + +This skill provides battle-tested patterns for: +- **Phase initialization** (create complete task list before starting) +- **Task granularity** (how to break phases into trackable tasks) +- **Status transitions** (pending → in_progress → completed) +- **Real-time updates** (mark complete immediately, not batched) +- **Iteration tracking** (progress through loops) +- **Parallel task tracking** (multiple agents executing simultaneously) +- **Task dependencies** (blockedBy/blocks relationships) +- **Cross-session persistence** (resume work across sessions) + +Task orchestration is especially valuable for workflows with >5 phases or >10 minutes duration, where users need progress feedback. + +## Tasks System API + +The Tasks system provides 4 tools: + +**TaskCreate**: Create a new task +``` +TaskCreate: + subject: "PHASE 1: Gather requirements" + description: "Ask user for feature requirements" + activeForm: "Gathering requirements" + status: "pending" + blockedBy: ["prerequisite-task-id"] // Optional + owner: "agent-name" // Optional +``` + +**TaskUpdate**: Update task status or fields +``` +TaskUpdate: taskId="task-123", status="in_progress" +TaskUpdate: taskId="task-123", status="completed" +TaskUpdate: taskId="task-123", description="Updated description" +``` + +**TaskList**: View all tasks +``` +TaskList // Shows all tasks with statuses +``` + +**TaskGet**: Get specific task details +``` +TaskGet: taskId="task-123" +``` + +## Core Patterns + +### Pattern 1: Phase Initialization + +**Create Tasks BEFORE Starting:** + +Initialize Tasks as **step 0** of your workflow, before any actual work begins: + +``` +✅ CORRECT - Initialize First: + +Step 0: Initialize Tasks + TaskCreate: + subject: "PHASE 1: Gather user inputs" + activeForm: "Gathering inputs" + + TaskCreate: + subject: "PHASE 1: Validate inputs" + activeForm: "Validating inputs" + blockedBy: ["phase-1-gather-id"] + + TaskCreate: + subject: "PHASE 2: Select AI models" + activeForm: "Selecting models" + + TaskCreate: + subject: "PHASE 2: Estimate costs" + activeForm: "Estimating costs" + + TaskCreate: + subject: "PHASE 3: Launch parallel reviews" + activeForm: "Launching reviews" + blockedBy: ["phase-2-approve-id"] + + TaskCreate: + subject: "PHASE 4: Consolidate reviews" + activeForm: "Consolidating" + + TaskCreate: + subject: "PHASE 5: Present results" + activeForm: "Presenting" + +Step 1: Start actual work (PHASE 1) + TaskUpdate: taskId="phase-1-gather-id", status="in_progress" + ... do work ... + TaskUpdate: taskId="phase-1-gather-id", status="completed" + + TaskUpdate: taskId="phase-1-validate-id", status="in_progress" + ... do work ... + +❌ WRONG - Create During Workflow: + +Step 1: Do some work + ... work happens ... + TaskCreate: subject="Did some work", status="completed" + +Step 2: Do more work + ... work happens ... + TaskCreate: subject="Did more work", status="completed" + +Problem: User has no visibility into upcoming phases +``` + +**List All Phases Upfront:** + +When initializing, create **all tasks** in the workflow, not just the current phase: + +``` +✅ CORRECT - Complete Visibility: + +TaskCreate: subject="PHASE 1: Gather user inputs" +TaskCreate: subject="PHASE 1: Validate inputs" +TaskCreate: subject="PHASE 2: Architecture planning" +TaskCreate: subject="PHASE 3: Implementation" +TaskCreate: subject="PHASE 3: Run quality checks" +TaskCreate: subject="PHASE 4: Code review" +TaskCreate: subject="PHASE 5: User acceptance" +TaskCreate: subject="PHASE 6: Generate report" + +User sees: "8 tasks total, 0 complete, Phase 1 starting" + +❌ WRONG - Incremental Discovery: + +TaskCreate: subject="PHASE 1: Gather user inputs" +TaskCreate: subject="PHASE 1: Validate inputs" + +(User thinks workflow is 2 tasks, then surprised by 6 more phases) +``` + +**Why Initialize First:** + +1. **User expectation setting:** User knows workflow scope (8 phases, ~20 minutes) +2. **Progress visibility:** User can see % complete (3/8 = 37.5%) +3. **Time estimation:** User can estimate remaining time based on progress +4. **Transparency:** No hidden phases or surprises + +--- + +### Pattern 2: Task Granularity Guidelines + +**One Task Per Significant Operation:** + +Each task should represent a **significant operation** (1-5 minutes of work): + +``` +✅ CORRECT - Significant Operations: + +TaskCreate: subject="PHASE 1: Ask user for inputs", activeForm="Asking user" +TaskCreate: subject="PHASE 2: Generate architecture plan", activeForm="Generating plan" +TaskCreate: subject="PHASE 3: Implement feature", activeForm="Implementing" +TaskCreate: subject="PHASE 4: Run tests", activeForm="Running tests" +TaskCreate: subject="PHASE 5: Code review", activeForm="Reviewing" + +Each task = meaningful unit of work + +❌ WRONG - Too Granular: + +TaskCreate: subject="PHASE 1: Ask user question 1" +TaskCreate: subject="PHASE 1: Ask user question 2" +TaskCreate: subject="PHASE 1: Ask user question 3" +TaskCreate: subject="PHASE 2: Read file A" +TaskCreate: subject="PHASE 2: Read file B" +... (50 micro-tasks) + +Problem: Too many updates, clutters user interface +``` + +**Multi-Step Phases: Break Into 2-3 Sub-Tasks:** + +For complex phases (>5 minutes), break into 2-3 sub-tasks: + +``` +✅ CORRECT - Sub-Task Breakdown: + +PHASE 3: Implementation (15 min total) + → Sub-tasks: + TaskCreate: subject="PHASE 3: Implement core logic", activeForm="Implementing core" + TaskCreate: subject="PHASE 3: Add error handling", activeForm="Adding error handling" + TaskCreate: subject="PHASE 3: Write tests", activeForm="Writing tests" + +User sees progress within phase: "PHASE 3: 2/3 complete" + +❌ WRONG - Single Monolithic Task: + +TaskCreate: subject="PHASE 3: Implementation" + +Problem: User sees "in_progress" for 15 min with no updates +``` + +**Avoid Too Many Tasks:** + +Limit to **max 15-20 tasks** for readability: + +``` +✅ CORRECT - 12 Tasks (readable): + +10-phase workflow: + TaskCreate: subject="PHASE 1: Ask user" + TaskCreate: subject="PHASE 2: Plan architecture" + TaskCreate: subject="PHASE 2: Review plan" + TaskCreate: subject="PHASE 3: Implement core" + TaskCreate: subject="PHASE 3: Add error handling" + TaskCreate: subject="PHASE 3: Write tests" + TaskCreate: subject="PHASE 4: Test" + TaskCreate: subject="PHASE 5: Review code" + TaskCreate: subject="PHASE 5: Fix issues" + TaskCreate: subject="PHASE 6: Re-review" + TaskCreate: subject="PHASE 7: Accept" + TaskCreate: subject="PHASE 8: Document" + +Total: 12 tasks (clean, trackable) + +❌ WRONG - 50 Tasks (overwhelming): + +Every single action as separate task: + TaskCreate: subject="Read file 1" + TaskCreate: subject="Read file 2" + TaskCreate: subject="Write file 3" + ... (50 tasks) + +Problem: User overwhelmed, can't see forest for trees +``` + +**Guideline by Workflow Duration:** + +``` +Workflow Duration → Task Count: + +< 5 minutes: 3-5 tasks +5-15 minutes: 8-12 tasks +15-30 minutes: 12-18 tasks +> 30 minutes: 15-20 tasks (if more, group into phases) + +Example: + 5-minute workflow (3 phases): + TaskCreate: subject="PHASE 1: Prepare" + TaskCreate: subject="PHASE 2: Execute" + TaskCreate: subject="PHASE 3: Present" + Total: 3 tasks ✓ + + 20-minute workflow (6 phases): + TaskCreate: subject="PHASE 1: Ask user" + TaskCreate: subject="PHASE 2: Plan architecture" + TaskCreate: subject="PHASE 2: Review plan" + TaskCreate: subject="PHASE 3: Implement core" + TaskCreate: subject="PHASE 3: Add error handling" + TaskCreate: subject="PHASE 3: Write tests" + TaskCreate: subject="PHASE 4: Test" + TaskCreate: subject="PHASE 5: Review code" + TaskCreate: subject="PHASE 5: Fix issues" + TaskCreate: subject="PHASE 6: Re-review" + TaskCreate: subject="PHASE 7: Accept" + Total: 11 tasks ✓ +``` + +--- + +### Pattern 3: Status Transitions + +**Exactly ONE Task In Progress at a Time:** + +Maintain the invariant: **exactly one task in_progress** at any moment: + +``` +✅ CORRECT - One In-Progress: + +State at time T1: + [✓] PHASE 1: Ask user (completed) + [✓] PHASE 2: Plan (completed) + [→] PHASE 3: Implement (in_progress) ← Only one + [ ] PHASE 4: Test (pending) + [ ] PHASE 5: Review (pending) + +State at time T2 (after PHASE 3 completes): + [✓] PHASE 1: Ask user (completed) + [✓] PHASE 2: Plan (completed) + [✓] PHASE 3: Implement (completed) + [→] PHASE 4: Test (in_progress) ← Only one + [ ] PHASE 5: Review (pending) + +❌ WRONG - Multiple In-Progress: + +State: + [✓] PHASE 1: Ask user (completed) + [→] PHASE 2: Plan (in_progress) ← Two in-progress? + [→] PHASE 3: Implement (in_progress) ← Confusing! + [ ] PHASE 4: Test (pending) + +Problem: User confused about current phase +``` + +**Status Transition Sequence:** + +``` +Lifecycle of a Task: + +1. Created: pending + TaskCreate: subject="PHASE 1: Gather inputs", status="pending" + +2. Started: pending → in_progress + TaskUpdate: taskId="phase-1-id", status="in_progress" + +3. Completed: in_progress → completed + TaskUpdate: taskId="phase-1-id", status="completed" + +4. Next task: Mark next task as in_progress + TaskUpdate: taskId="phase-2-id", status="in_progress" + +Example Timeline: + +T=0s: TaskUpdate: taskId="task-1-id", status="in_progress" + [→] Task 1 (in_progress), [ ] Task 2 (pending) + +T=30s: TaskUpdate: taskId="task-1-id", status="completed" + TaskUpdate: taskId="task-2-id", status="in_progress" + [✓] Task 1 (completed), [→] Task 2 (in_progress) + +T=60s: TaskUpdate: taskId="task-2-id", status="completed" + [✓] Task 1 (completed), [✓] Task 2 (completed) +``` + +**NEVER Batch Completions:** + +Mark tasks completed **immediately** after finishing, not at end of phase: + +``` +✅ CORRECT - Immediate Updates: + +TaskUpdate: taskId="phase-1-ask-id", status="in_progress" +... do work (30s) ... +TaskUpdate: taskId="phase-1-ask-id", status="completed" ← Immediate + +TaskUpdate: taskId="phase-1-validate-id", status="in_progress" +... do work (20s) ... +TaskUpdate: taskId="phase-1-validate-id", status="completed" ← Immediate + +User sees real-time progress + +❌ WRONG - Batched Updates: + +TaskUpdate: taskId="phase-1-ask-id", status="in_progress" +... do work (30s) ... + +TaskUpdate: taskId="phase-1-validate-id", status="in_progress" +... do work (20s) ... + +(At end of PHASE 1, batch update both to completed) + +Problem: User doesn't see progress for 50s, thinks workflow is stuck +``` + +--- + +### Pattern 4: Real-Time Progress Tracking + +**TaskUpdate As Work Progresses:** + +Tasks should reflect **current state**, not past state: + +``` +✅ CORRECT - Real-Time Updates: + +T=0s: Initialize Tasks (8 tasks, all pending) +T=5s: TaskUpdate: taskId="phase-1-id", status="in_progress" +T=35s: TaskUpdate: taskId="phase-1-id", status="completed" + TaskUpdate: taskId="phase-2-id", status="in_progress" +T=90s: TaskUpdate: taskId="phase-2-id", status="completed" + TaskUpdate: taskId="phase-3-id", status="in_progress" +... + +User always sees accurate current state + +❌ WRONG - Delayed Updates: + +T=0s: Initialize Tasks +T=300s: Workflow completes +T=301s: Update all tasks to completed + +Problem: No progress visibility for 5 minutes +``` + +**Add New Tasks If Discovered During Execution:** + +If you discover additional work during execution, create new tasks: + +``` +Scenario: During implementation, realize refactoring needed + +Initial Tasks: + [✓] PHASE 1: Plan (completed) + [→] PHASE 2: Implement (in_progress) + [ ] PHASE 3: Test (pending) + [ ] PHASE 4: Review (pending) + +During PHASE 2, discover: + "Implementation requires refactoring legacy code" + +TaskUpdate: taskId="phase-2-id", status="completed" +TaskCreate: subject="PHASE 2: Refactor legacy code", activeForm="Refactoring" +TaskUpdate: taskId="new-refactor-id", status="in_progress" + +Updated Tasks: + [✓] PHASE 1: Plan + [✓] PHASE 2: Implement core logic + [→] PHASE 2: Refactor legacy code (in_progress) ← New task + [ ] PHASE 3: Test + [ ] PHASE 4: Review + +User sees: "Additional work discovered: refactoring. Total now 5 tasks." +``` + +**User Can See Current Progress at Any Time:** + +With real-time updates, user can check progress: + +``` +User checks at T=120s: + +TaskList shows: + [✓] PHASE 1: Ask user + [✓] PHASE 2: Plan architecture + [→] PHASE 3: Implement core logic (in_progress) + [ ] PHASE 3: Add error handling + [ ] PHASE 3: Write tests + [ ] PHASE 4: Code review + [ ] PHASE 5: Accept + +User sees: "3/7 tasks complete (42.8%), currently implementing core logic" +``` + +--- + +### Pattern 5: Iteration Loop Tracking + +**Create Task Per Iteration:** + +For iteration loops, create a task for each iteration: + +``` +✅ CORRECT - Iteration Tasks: + +Design Validation Loop (max 10 iterations): + +Initial Tasks: + TaskCreate: subject="Iteration 1/10: Designer validation" + TaskCreate: subject="Iteration 2/10: Designer validation" + TaskCreate: subject="Iteration 3/10: Designer validation" + ... (create all 10 upfront) + +Progress: + [✓] Iteration 1/10: Designer validation (NEEDS IMPROVEMENT) + [✓] Iteration 2/10: Designer validation (NEEDS IMPROVEMENT) + [→] Iteration 3/10: Designer validation (in_progress) + [ ] Iteration 4/10: Designer validation + ... + +User sees: "Iteration 3/10 in progress, 2 complete" + +❌ WRONG - Single Loop Task: + +TaskCreate: subject="Design validation loop" + +Problem: User sees "in_progress" for 10 minutes, no iteration visibility +``` + +**Mark Iteration Complete When Done:** + +``` +Iteration Lifecycle: + +Iteration 1: + TaskUpdate: taskId="iter-1-id", status="in_progress" + Run designer validation + If NEEDS IMPROVEMENT: Run developer fixes + TaskUpdate: taskId="iter-1-id", status="completed" + +Iteration 2: + TaskUpdate: taskId="iter-2-id", status="in_progress" + Run designer validation + If PASS: Exit loop early + TaskUpdate: taskId="iter-2-id", status="completed" + +Result: Loop exited after 2 iterations + [✓] Iteration 1/10 (completed) + [✓] Iteration 2/10 (completed) + [ ] Iteration 3/10 (not needed, loop exited) + ... + +User sees: "Loop completed in 2/10 iterations" +``` + +**Track Total Iterations vs Max Limit:** + +``` +Iteration Progress: + +Max: 10 iterations +Current: 5 + +TaskList shows: + [✓] Iteration 1/10 + [✓] Iteration 2/10 + [✓] Iteration 3/10 + [✓] Iteration 4/10 + [→] Iteration 5/10 + [ ] Iteration 6/10 + ... + +User sees: "Iteration 5/10 (50% through max)" + +Warning at Iteration 8: + "Iteration 8/10 - approaching max, may escalate to user if not PASS" +``` + +--- + +### Pattern 6: Parallel Task Tracking + +**Multiple Agents Executing Simultaneously:** + +When running agents in parallel, track each separately: + +``` +✅ CORRECT - Separate Tasks for Parallel Agents: + +Multi-Model Review (3 models in parallel): + +TaskCreate: subject="PHASE 1: Prepare review context" +TaskCreate: subject="PHASE 2: Claude review", owner="claude-agent" +TaskCreate: subject="PHASE 2: Grok review", owner="grok-agent" +TaskCreate: subject="PHASE 2: Gemini review", owner="gemini-agent" +TaskCreate: subject="PHASE 3: Consolidate reviews" + +Launch parallel reviews: + TaskUpdate: taskId="claude-review-id", status="in_progress" + TaskUpdate: taskId="grok-review-id", status="in_progress" + TaskUpdate: taskId="gemini-review-id", status="in_progress" + +State: + [✓] PHASE 1: Prepare review context + [→] PHASE 2: Claude review (in_progress) + [→] PHASE 2: Grok review (in_progress) + [→] PHASE 2: Gemini review (in_progress) + [ ] PHASE 3: Consolidate reviews + +Note: 3 tasks "in_progress" is OK for parallel execution + (Exception to "one in_progress" rule) + +As models complete: + [✓] PHASE 1: Prepare review context + [✓] PHASE 2: Claude review (completed) ← First to finish + [→] PHASE 2: Grok review (in_progress) + [→] PHASE 2: Gemini review (in_progress) + [ ] PHASE 3: Consolidate reviews + +User sees: "1/3 reviews complete, 2 in progress" + +❌ WRONG - Single Task for Parallel Work: + +TaskCreate: subject="PHASE 2: Run 3 reviews" + +Problem: No visibility into which reviews are complete +``` + +**Update As Each Agent Completes:** + +``` +Parallel Execution Timeline: + +T=0s: Launch 3 reviews in parallel + TaskUpdate: taskId="claude-id", status="in_progress" + TaskUpdate: taskId="grok-id", status="in_progress" + TaskUpdate: taskId="gemini-id", status="in_progress" + + [→] Claude review (in_progress) + [→] Grok review (in_progress) + [→] Gemini review (in_progress) + +T=60s: Claude completes first + TaskUpdate: taskId="claude-id", status="completed" + + [✓] Claude review (completed) + [→] Grok review (in_progress) + [→] Gemini review (in_progress) + +T=120s: Gemini completes + TaskUpdate: taskId="gemini-id", status="completed" + + [✓] Claude review (completed) + [→] Grok review (in_progress) + [✓] Gemini review (completed) + +T=180s: Grok completes + TaskUpdate: taskId="grok-id", status="completed" + + [✓] Claude review (completed) + [✓] Grok review (completed) + [✓] Gemini review (completed) + +User sees real-time completion updates +``` + +--- + +### Pattern 7: Task Dependencies + +**Use blockedBy for Phase Dependencies:** + +Track which tasks must complete before others can start: + +``` +✅ CORRECT - Dependency Tracking: + +TaskCreate: + subject: "PHASE 1: Gather requirements" + activeForm: "Gathering requirements" + // Returns taskId: "phase-1-id" + +TaskCreate: + subject: "PHASE 2: Design architecture" + activeForm: "Designing" + blockedBy: ["phase-1-id"] ← Blocks until PHASE 1 complete + +TaskCreate: + subject: "PHASE 3: Implementation" + activeForm: "Implementing" + blockedBy: ["phase-2-id"] ← Blocks until PHASE 2 complete + +When PHASE 1 completes: + TaskUpdate: taskId="phase-1-id", status="completed" + → PHASE 2 automatically unblocked + +Benefits: +- System prevents starting PHASE 2 before PHASE 1 complete +- User sees dependency chain +- Automatic unblocking when prerequisites complete +``` + +**Parallel Tasks with Shared Blocker:** + +Multiple tasks can depend on same prerequisite: + +``` +TaskCreate: + subject: "PHASE 1: Prepare context" + // Returns: "context-id" + +TaskCreate: + subject: "PHASE 2: Claude review" + owner: "claude-agent" + blockedBy: ["context-id"] + +TaskCreate: + subject: "PHASE 2: Grok review" + owner: "grok-agent" + blockedBy: ["context-id"] + +TaskCreate: + subject: "PHASE 2: Gemini review" + owner: "gemini-agent" + blockedBy: ["context-id"] + +When context preparation completes: + TaskUpdate: taskId="context-id", status="completed" + → All 3 reviews automatically unblocked and can start in parallel +``` + +**Complex Dependency Chains:** + +``` +Sequential with parallel phases: + +TaskCreate: subject="PHASE 1: Requirements" + → phase-1-id + +TaskCreate: subject="PHASE 2: Design" + blockedBy: ["phase-1-id"] + → phase-2-id + +TaskCreate: subject="PHASE 3: Implement Backend" + owner: "backend-developer" + blockedBy: ["phase-2-id"] + → backend-id + +TaskCreate: subject="PHASE 3: Implement Frontend" + owner: "frontend-developer" + blockedBy: ["phase-2-id"] + → frontend-id + +TaskCreate: subject="PHASE 4: Integration Tests" + blockedBy: ["backend-id", "frontend-id"] ← Waits for both + → integration-id + +Execution: +1. PHASE 1 completes → Unblocks PHASE 2 +2. PHASE 2 completes → Unblocks Backend + Frontend (parallel) +3. Both Backend + Frontend complete → Unblocks Integration Tests +``` + +--- + +### Pattern 8: Cross-Session Persistence + +**Resume Work Across Sessions:** + +Tasks persist across Claude Code sessions when using CLAUDE_CODE_TASK_LIST_ID: + +``` +Session 1 (Initial Implementation): + +# Set task list ID for this feature +export CLAUDE_CODE_TASK_LIST_ID=feature-auth +claude + +# Create tasks +TaskCreate: subject="PHASE 1: Design auth flow" +TaskCreate: subject="PHASE 2: Implement backend" +TaskCreate: subject="PHASE 3: Implement frontend" +TaskCreate: subject="PHASE 4: Testing" + +# Complete PHASE 1 +TaskUpdate: taskId="phase-1-id", status="in_progress" +... work ... +TaskUpdate: taskId="phase-1-id", status="completed" + +# Start PHASE 2 (not finished) +TaskUpdate: taskId="phase-2-id", status="in_progress" +... partial work ... +exit + +--- + +Session 2 (Resume Later): + +# Same task list ID +export CLAUDE_CODE_TASK_LIST_ID=feature-auth +claude + +# Tasks still visible! +TaskList shows: + [✓] PHASE 1: Design auth flow (completed) + [→] PHASE 2: Implement backend (in_progress) ← Resume here + [ ] PHASE 3: Implement frontend + [ ] PHASE 4: Testing + +# Continue where left off +... complete PHASE 2 ... +TaskUpdate: taskId="phase-2-id", status="completed" + +# Start PHASE 3 +TaskUpdate: taskId="phase-3-id", status="in_progress" +``` + +**Benefits:** + +- Work on large features across multiple sessions +- Never lose progress tracking +- Team members can see task status +- Clear handoff points between sessions + +**Best Practices:** + +``` +✅ Use meaningful task list IDs: + export CLAUDE_CODE_TASK_LIST_ID=feature-auth + export CLAUDE_CODE_TASK_LIST_ID=bug-payment-failure + export CLAUDE_CODE_TASK_LIST_ID=refactor-api + +❌ Avoid generic IDs: + export CLAUDE_CODE_TASK_LIST_ID=work + export CLAUDE_CODE_TASK_LIST_ID=tasks +``` + +--- + +## Integration with Other Skills + +**task-orchestration + multi-agent-coordination:** + +``` +Use Case: Multi-phase implementation workflow + +Step 1: Initialize Tasks (task-orchestration) + TaskCreate: subject="PHASE 1: Requirements" + TaskCreate: subject="PHASE 2: Architecture" + TaskCreate: subject="PHASE 3: Backend Implementation" + TaskCreate: subject="PHASE 4: Frontend Implementation" + TaskCreate: subject="PHASE 5: Testing" + ... (8 total phases) + +Step 2: Sequential Agent Delegation (multi-agent-coordination) + Phase 1: api-architect + TaskUpdate: taskId="phase-1-id", status="in_progress" + Delegate to api-architect + TaskUpdate: taskId="phase-1-id", status="completed" + + Phase 2: backend-developer + TaskUpdate: taskId="phase-2-id", status="in_progress" + Delegate to backend-developer + TaskUpdate: taskId="phase-2-id", status="completed" + + ... continue for all phases +``` + +**task-orchestration + multi-model-validation:** + +``` +Use Case: Multi-model review with progress tracking + +Step 1: Initialize Tasks (task-orchestration) + TaskCreate: subject="PHASE 1: Prepare context" + TaskCreate: subject="PHASE 2: Claude review", owner="claude" + TaskCreate: subject="PHASE 2: Grok review", owner="grok" + TaskCreate: subject="PHASE 2: Gemini review", owner="gemini" + TaskCreate: subject="PHASE 2: GPT-5 review", owner="gpt" + TaskCreate: subject="PHASE 2: DeepSeek review", owner="deepseek" + TaskCreate: subject="PHASE 3: Consolidate results" + +Step 2: Parallel Execution (multi-model-validation) + TaskUpdate: taskId="phase-1-id", status="in_progress" + ... prepare context ... + TaskUpdate: taskId="phase-1-id", status="completed" + + Launch all 5 models simultaneously + TaskUpdate: taskId="claude-id", status="in_progress" + TaskUpdate: taskId="grok-id", status="in_progress" + ... (all 5 in_progress) + + As each completes: TaskUpdate with status="completed" + +Step 3: Real-Time Visibility (task-orchestration) + User sees: "PHASE 2: 3/5 reviews complete..." +``` + +**task-orchestration + quality-gates:** + +``` +Use Case: Iteration loop with Tasks tracking + +Step 1: Initialize Tasks (task-orchestration) + TaskCreate: subject="Iteration 1/10: Designer validation" + TaskCreate: subject="Iteration 2/10: Designer validation" + TaskCreate: subject="Iteration 3/10: Designer validation" + ... (10 iterations) + +Step 2: Iteration Loop (quality-gates) + For i = 1 to 10: + TaskUpdate: taskId="iter-i-id", status="in_progress" + Run designer validation + If PASS: Exit loop + TaskUpdate: taskId="iter-i-id", status="completed" + +Step 3: Progress Visibility + User sees: "Iteration 5/10 complete, 5 remaining" +``` + +--- + +## Best Practices + +**Do:** +- ✅ Initialize Tasks BEFORE starting work (step 0) +- ✅ Create ALL phase tasks upfront (user sees complete scope) +- ✅ Use 8-15 tasks for typical workflows (readable) +- ✅ TaskUpdate to completed IMMEDIATELY after finishing (real-time) +- ✅ Keep exactly ONE task in_progress (except parallel tasks) +- ✅ Track iterations separately (Iteration 1/10, 2/10, ...) +- ✅ Update as work progresses (not batched at end) +- ✅ Create new tasks if discovered during execution +- ✅ Use blockedBy for dependencies +- ✅ Use owner field for parallel agent tracking +- ✅ Use CLAUDE_CODE_TASK_LIST_ID for cross-session work + +**Don't:** +- ❌ Create tasks during workflow (initialize first) +- ❌ Hide phases from user (create all upfront) +- ❌ Create too many tasks (>20 overwhelms user) +- ❌ Batch completions at end of phase (update real-time) +- ❌ Leave multiple tasks in_progress (pick one, except parallel) +- ❌ Use single task for loop (track iterations separately) +- ❌ Update only at start/end (update during execution) + +**Performance:** +- TaskUpdate overhead: <1s per update (negligible) +- User visibility benefit: Reduces perceived wait time 30-50% +- Workflow confidence: User knows progress, less likely to cancel + +--- + +## Examples + +### Example 1: 8-Phase Implementation Workflow + +**Scenario:** Full-cycle implementation with Tasks tracking + +**Execution:** + +``` +Step 0: Initialize Tasks + +TaskCreate: + subject: "PHASE 1: Ask user for requirements" + activeForm: "Asking user" + // Returns: "phase-1-id" + +TaskCreate: + subject: "PHASE 2: Generate architecture plan" + activeForm: "Generating plan" + blockedBy: ["phase-1-id"] + // Returns: "phase-2-id" + +TaskCreate: + subject: "PHASE 3: Implement core logic" + activeForm: "Implementing core" + blockedBy: ["phase-2-id"] + // Returns: "phase-3a-id" + +TaskCreate: + subject: "PHASE 3: Add error handling" + activeForm: "Adding error handling" + blockedBy: ["phase-3a-id"] + // Returns: "phase-3b-id" + +TaskCreate: + subject: "PHASE 3: Write tests" + activeForm: "Writing tests" + blockedBy: ["phase-3b-id"] + // Returns: "phase-3c-id" + +TaskCreate: + subject: "PHASE 4: Run test suite" + activeForm: "Running tests" + blockedBy: ["phase-3c-id"] + // Returns: "phase-4-id" + +TaskCreate: + subject: "PHASE 5: Code review" + activeForm: "Reviewing" + blockedBy: ["phase-4-id"] + // Returns: "phase-5-id" + +TaskCreate: + subject: "PHASE 6: Fix review issues" + activeForm: "Fixing issues" + blockedBy: ["phase-5-id"] + // Returns: "phase-6-id" + +TaskCreate: + subject: "PHASE 7: User acceptance" + activeForm: "User validating" + blockedBy: ["phase-6-id"] + // Returns: "phase-7-id" + +TaskCreate: + subject: "PHASE 8: Generate report" + activeForm: "Generating report" + blockedBy: ["phase-7-id"] + // Returns: "phase-8-id" + +User sees: "10 tasks, 0 complete, Phase 1 starting..." + +--- + +Step 1: PHASE 1 + +TaskUpdate: taskId="phase-1-id", status="in_progress" +... gather requirements (30s) ... +TaskUpdate: taskId="phase-1-id", status="completed" +→ Automatically unblocks PHASE 2 + +User sees: "1/10 tasks complete (10%)" + +--- + +Step 2: PHASE 2 + +TaskUpdate: taskId="phase-2-id", status="in_progress" +... generate plan (2 min) ... +TaskUpdate: taskId="phase-2-id", status="completed" +→ Automatically unblocks PHASE 3 + +User sees: "2/10 tasks complete (20%)" + +--- + +Step 3: PHASE 3 (3 sub-tasks) + +TaskUpdate: taskId="phase-3a-id", status="in_progress" +... implement core (3 min) ... +TaskUpdate: taskId="phase-3a-id", status="completed" +→ Automatically unblocks "Add error handling" + +User sees: "3/10 tasks complete (30%)" + +TaskUpdate: taskId="phase-3b-id", status="in_progress" +... add error handling (2 min) ... +TaskUpdate: taskId="phase-3b-id", status="completed" +→ Automatically unblocks "Write tests" + +User sees: "4/10 tasks complete (40%)" + +TaskUpdate: taskId="phase-3c-id", status="in_progress" +... write tests (3 min) ... +TaskUpdate: taskId="phase-3c-id", status="completed" +→ Automatically unblocks PHASE 4 + +User sees: "5/10 tasks complete (50%)" + +--- + +... continue through all phases ... + +--- + +Final State: + +TaskList shows: + [✓] PHASE 1: Ask user for requirements + [✓] PHASE 2: Generate architecture plan + [✓] PHASE 3: Implement core logic + [✓] PHASE 3: Add error handling + [✓] PHASE 3: Write tests + [✓] PHASE 4: Run test suite + [✓] PHASE 5: Code review + [✓] PHASE 6: Fix review issues + [✓] PHASE 7: User acceptance + [✓] PHASE 8: Generate report + +User sees: "10/10 tasks complete (100%). Workflow finished!" + +Total Duration: ~15 minutes +User Experience: Continuous progress updates every 1-3 minutes +``` + +--- + +### Example 2: Iteration Loop with Progress Tracking + +**Scenario:** Design validation with 10 max iterations + +**Execution:** + +``` +Step 0: Initialize Tasks + +TaskCreate: + subject: "PHASE 1: Gather design reference" + activeForm: "Gathering design" + // Returns: "phase-1-id" + +TaskCreate: + subject: "Iteration 1/10: Designer validation" + activeForm: "Designer validating (iter 1)" + blockedBy: ["phase-1-id"] + // Returns: "iter-1-id" + +TaskCreate: + subject: "Iteration 2/10: Designer validation" + activeForm: "Designer validating (iter 2)" + // Returns: "iter-2-id" + +TaskCreate: + subject: "Iteration 3/10: Designer validation" + activeForm: "Designer validating (iter 3)" + // Returns: "iter-3-id" + +... (create all 10 iterations) ... + +TaskCreate: + subject: "PHASE 3: User validation gate" + activeForm: "User validating" + // Returns: "phase-3-id" + +--- + +Step 1: PHASE 1 + +TaskUpdate: taskId="phase-1-id", status="in_progress" +... gather design (20s) ... +TaskUpdate: taskId="phase-1-id", status="completed" +→ Unblocks Iteration 1 + +--- + +Step 2: Iteration Loop + +Iteration 1: + TaskUpdate: taskId="iter-1-id", status="in_progress" + Designer: "NEEDS IMPROVEMENT - 5 issues" + Developer: Fix 5 issues + TaskUpdate: taskId="iter-1-id", status="completed" + User sees: "Iteration 1/10 complete, 5 issues fixed" + +Iteration 2: + TaskUpdate: taskId="iter-2-id", status="in_progress" + Designer: "NEEDS IMPROVEMENT - 3 issues" + Developer: Fix 3 issues + TaskUpdate: taskId="iter-2-id", status="completed" + User sees: "Iteration 2/10 complete, 3 issues fixed" + +Iteration 3: + TaskUpdate: taskId="iter-3-id", status="in_progress" + Designer: "NEEDS IMPROVEMENT - 1 issue" + Developer: Fix 1 issue + TaskUpdate: taskId="iter-3-id", status="completed" + User sees: "Iteration 3/10 complete, 1 issue fixed" + +Iteration 4: + TaskUpdate: taskId="iter-4-id", status="in_progress" + Designer: "PASS ✓" + TaskUpdate: taskId="iter-4-id", status="completed" + Exit loop (early exit) + User sees: "Loop completed in 4/10 iterations" + +--- + +Step 3: PHASE 3 + +TaskUpdate: taskId="phase-3-id", status="in_progress" +... user validates ... +TaskUpdate: taskId="phase-3-id", status="completed" + +--- + +Final State: + +TaskList shows: + [✓] PHASE 1: Gather design + [✓] Iteration 1/10 (5 issues fixed) + [✓] Iteration 2/10 (3 issues fixed) + [✓] Iteration 3/10 (1 issue fixed) + [✓] Iteration 4/10 (PASS) + [ ] Iteration 5/10 (not needed) + [ ] Iteration 6/10 (not needed) + ... (iterations 5-10 skipped) + [✓] PHASE 3: User validation + +User Experience: Clear iteration progress, early exit visible +``` + +--- + +### Example 3: Parallel Multi-Model Review + +**Scenario:** 5 AI models reviewing code in parallel + +**Execution:** + +``` +Step 0: Initialize Tasks + +TaskCreate: + subject: "PHASE 1: Prepare review context" + activeForm: "Preparing context" + // Returns: "phase-1-id" + +TaskCreate: + subject: "PHASE 2: Claude review" + owner: "claude-agent" + activeForm: "Claude reviewing" + blockedBy: ["phase-1-id"] + // Returns: "claude-id" + +TaskCreate: + subject: "PHASE 2: Grok review" + owner: "grok-agent" + activeForm: "Grok reviewing" + blockedBy: ["phase-1-id"] + // Returns: "grok-id" + +TaskCreate: + subject: "PHASE 2: Gemini review" + owner: "gemini-agent" + activeForm: "Gemini reviewing" + blockedBy: ["phase-1-id"] + // Returns: "gemini-id" + +TaskCreate: + subject: "PHASE 2: GPT-5 review" + owner: "gpt-agent" + activeForm: "GPT-5 reviewing" + blockedBy: ["phase-1-id"] + // Returns: "gpt-id" + +TaskCreate: + subject: "PHASE 2: DeepSeek review" + owner: "deepseek-agent" + activeForm: "DeepSeek reviewing" + blockedBy: ["phase-1-id"] + // Returns: "deepseek-id" + +TaskCreate: + subject: "PHASE 3: Consolidate reviews" + activeForm: "Consolidating" + blockedBy: ["claude-id", "grok-id", "gemini-id", "gpt-id", "deepseek-id"] + // Returns: "phase-3-id" + +TaskCreate: + subject: "PHASE 4: Present results" + activeForm: "Presenting" + blockedBy: ["phase-3-id"] + // Returns: "phase-4-id" + +--- + +Step 1: PHASE 1 + +TaskUpdate: taskId="phase-1-id", status="in_progress" +... prepare context (30s) ... +TaskUpdate: taskId="phase-1-id", status="completed" +→ Unblocks all 5 review tasks + +--- + +Step 2: PHASE 2 (Parallel Execution) + +Launch all 5 in parallel: + TaskUpdate: taskId="claude-id", status="in_progress" + TaskUpdate: taskId="grok-id", status="in_progress" + TaskUpdate: taskId="gemini-id", status="in_progress" + TaskUpdate: taskId="gpt-id", status="in_progress" + TaskUpdate: taskId="deepseek-id", status="in_progress" + +TaskList shows: + [✓] PHASE 1: Prepare context + [→] PHASE 2: Claude review (in_progress) + [→] PHASE 2: Grok review (in_progress) + [→] PHASE 2: Gemini review (in_progress) + [→] PHASE 2: GPT-5 review (in_progress) + [→] PHASE 2: DeepSeek review (in_progress) + [ ] PHASE 3: Consolidate reviews (blocked) + [ ] PHASE 4: Present results (blocked) + +Launch all 5 models (4-Message Pattern for parallel execution) + +As each completes: + +T=60s: Claude completes first + TaskUpdate: taskId="claude-id", status="completed" + User sees: "1/5 reviews complete" + +T=90s: Gemini completes + TaskUpdate: taskId="gemini-id", status="completed" + User sees: "2/5 reviews complete" + +T=120s: GPT-5 completes + TaskUpdate: taskId="gpt-id", status="completed" + User sees: "3/5 reviews complete" + +T=150s: Grok completes + TaskUpdate: taskId="grok-id", status="completed" + User sees: "4/5 reviews complete" + +T=180s: DeepSeek completes + TaskUpdate: taskId="deepseek-id", status="completed" + User sees: "5/5 reviews complete!" + → Automatically unblocks PHASE 3 + +--- + +Step 3: PHASE 3 + +TaskUpdate: taskId="phase-3-id", status="in_progress" +... consolidate reviews (30s) ... +TaskUpdate: taskId="phase-3-id", status="completed" +→ Automatically unblocks PHASE 4 + +--- + +Step 4: PHASE 4 + +TaskUpdate: taskId="phase-4-id", status="in_progress" +... present results (10s) ... +TaskUpdate: taskId="phase-4-id", status="completed" + +--- + +Final State: + +TaskList shows: + [✓] PHASE 1: Prepare review context + [✓] PHASE 2: Claude review + [✓] PHASE 2: Grok review + [✓] PHASE 2: Gemini review + [✓] PHASE 2: GPT-5 review + [✓] PHASE 2: DeepSeek review + [✓] PHASE 3: Consolidate reviews + [✓] PHASE 4: Present results + +User sees: "Multi-model review complete in 3 minutes" + +User Experience: + - Real-time progress as each model completes + - Clear visibility: "3/5 reviews complete" + - Automatic phase progression when all reviews done + - Reduces perceived wait time (user knows progress) +``` + +--- + +## Troubleshooting + +**Problem: User thinks workflow is stuck** + +Cause: No task updates for >1 minute + +Solution: TaskUpdate more frequently, or add sub-tasks + +``` +❌ Wrong: + [→] PHASE 3: Implementation (in_progress for 10 minutes) + +✅ Correct: + [✓] PHASE 3: Implement core logic (2 min) + [✓] PHASE 3: Add error handling (3 min) + [→] PHASE 3: Write tests (in_progress, 2 min so far) + +User sees progress every 2-3 minutes +``` + +--- + +**Problem: Too many tasks (>20), overwhelming** + +Cause: Too granular task breakdown + +Solution: Group micro-tasks into larger operations + +``` +❌ Wrong (25 tasks): + TaskCreate: subject="Read file 1" + TaskCreate: subject="Read file 2" + TaskCreate: subject="Write file 3" + ... (25 micro-tasks) + +✅ Correct (8 tasks): + TaskCreate: subject="PHASE 1: Gather inputs" (includes reading files) + TaskCreate: subject="PHASE 2: Process data" + ... (8 significant operations) +``` + +--- + +**Problem: Multiple tasks "in_progress" (not parallel execution)** + +Cause: Forgot to mark previous task as completed + +Solution: Always TaskUpdate to completed before starting next + +``` +❌ Wrong: + [→] PHASE 1: Ask user (in_progress) + [→] PHASE 2: Plan (in_progress) ← Both in_progress? + +✅ Correct: + TaskUpdate: taskId="phase-1-id", status="completed" + TaskUpdate: taskId="phase-2-id", status="in_progress" + + [✓] PHASE 1: Ask user (completed) + [→] PHASE 2: Plan (in_progress) ← Only one +``` + +--- + +## Summary + +Task orchestration provides real-time progress visibility through: + +- **Phase initialization** (create task list before starting with TaskCreate) +- **Appropriate granularity** (8-15 tasks, significant operations) +- **Real-time updates** (TaskUpdate to completed immediately) +- **Exactly one in_progress** (except parallel execution) +- **Iteration tracking** (separate task per iteration) +- **Parallel task tracking** (update as each completes with owner field) +- **Task dependencies** (blockedBy/blocks for automatic phase management) +- **Cross-session persistence** (CLAUDE_CODE_TASK_LIST_ID for resumable work) + +Master these patterns and users will always know: +- What's happening now +- What's coming next +- How much progress has been made +- How much remains +- Which tasks are blocked and why + +This transforms "black box" workflows into transparent, trackable processes. + +--- + +**Extracted From:** +- `/review` command (10-task initialization, phase-based tracking) +- `/implement` command (8-phase workflow with sub-tasks) +- `/validate-ui` command (iteration tracking, user feedback rounds) +- All multi-phase orchestration workflows diff --git a/plugins/multimodel/skills/todowrite-orchestration/SKILL.md b/plugins/multimodel/skills/todowrite-orchestration/SKILL.md deleted file mode 100644 index 7adc97e..0000000 --- a/plugins/multimodel/skills/todowrite-orchestration/SKILL.md +++ /dev/null @@ -1,985 +0,0 @@ ---- -name: todowrite-orchestration -description: Track progress in multi-phase workflows with TodoWrite. Use when orchestrating 5+ phase commands, managing iteration loops, tracking parallel tasks, or providing real-time progress visibility. Trigger keywords - "phase tracking", "progress", "workflow", "multi-step", "multi-phase", "todo", "tracking", "status". -version: 0.1.0 -tags: [orchestration, todowrite, progress, tracking, workflow, multi-phase] -keywords: [phase-tracking, progress, workflow, multi-step, multi-phase, todo, tracking, status, visibility] -plugin: multimodel -updated: 2026-01-20 ---- - -# TodoWrite Orchestration - -**Version:** 1.0.0 -**Purpose:** Patterns for using TodoWrite in complex multi-phase workflows -**Status:** Production Ready - -## Overview - -TodoWrite orchestration is the practice of using the TodoWrite tool to provide **real-time progress visibility** in complex multi-phase workflows. It transforms opaque "black box" workflows into transparent, trackable processes where users can see: - -- What phase is currently executing -- How many phases remain -- Which tasks are pending, in-progress, or completed -- Overall progress percentage -- Iteration counts in loops - -This skill provides battle-tested patterns for: -- **Phase initialization** (create complete task list before starting) -- **Task granularity** (how to break phases into trackable tasks) -- **Status transitions** (pending → in_progress → completed) -- **Real-time updates** (mark complete immediately, not batched) -- **Iteration tracking** (progress through loops) -- **Parallel task tracking** (multiple agents executing simultaneously) - -TodoWrite orchestration is especially valuable for workflows with >5 phases or >10 minutes duration, where users need progress feedback. - -## Core Patterns - -### Pattern 1: Phase Initialization - -**Create TodoWrite List BEFORE Starting:** - -Initialize TodoWrite as **step 0** of your workflow, before any actual work begins: - -``` -✅ CORRECT - Initialize First: - -Step 0: Initialize TodoWrite - TodoWrite: Create task list - - PHASE 1: Gather user inputs - - PHASE 1: Validate inputs - - PHASE 2: Select AI models - - PHASE 2: Estimate costs - - PHASE 2: Get user approval - - PHASE 3: Launch parallel reviews - - PHASE 3: Wait for all reviews - - PHASE 4: Consolidate reviews - - PHASE 5: Present results - -Step 1: Start actual work (PHASE 1) - Mark "PHASE 1: Gather user inputs" as in_progress - ... do work ... - Mark "PHASE 1: Gather user inputs" as completed - Mark "PHASE 1: Validate inputs" as in_progress - ... do work ... - -❌ WRONG - Create During Workflow: - -Step 1: Do some work - ... work happens ... - TodoWrite: Create task "Did some work" (completed) - -Step 2: Do more work - ... work happens ... - TodoWrite: Create task "Did more work" (completed) - -Problem: User has no visibility into upcoming phases -``` - -**List All Phases Upfront:** - -When initializing, include **all phases** in the task list, not just the current phase: - -``` -✅ CORRECT - Complete Visibility: - -TodoWrite Initial State: - [ ] PHASE 1: Gather user inputs - [ ] PHASE 1: Validate inputs - [ ] PHASE 2: Architecture planning - [ ] PHASE 3: Implementation - [ ] PHASE 3: Run quality checks - [ ] PHASE 4: Code review - [ ] PHASE 5: User acceptance - [ ] PHASE 6: Generate report - -User sees: "8 tasks total, 0 complete, Phase 1 starting" - -❌ WRONG - Incremental Discovery: - -TodoWrite Initial State: - [ ] PHASE 1: Gather user inputs - [ ] PHASE 1: Validate inputs - -(User thinks workflow is 2 tasks, then surprised by 6 more phases) -``` - -**Why Initialize First:** - -1. **User expectation setting:** User knows workflow scope (8 phases, ~20 minutes) -2. **Progress visibility:** User can see % complete (3/8 = 37.5%) -3. **Time estimation:** User can estimate remaining time based on progress -4. **Transparency:** No hidden phases or surprises - ---- - -### Pattern 2: Task Granularity Guidelines - -**One Task Per Significant Operation:** - -Each task should represent a **significant operation** (1-5 minutes of work): - -``` -✅ CORRECT - Significant Operations: - -Tasks: - - PHASE 1: Ask user for inputs (30s) - - PHASE 2: Generate architecture plan (2 min) - - PHASE 3: Implement feature (5 min) - - PHASE 4: Run tests (1 min) - - PHASE 5: Code review (3 min) - -Each task = meaningful unit of work - -❌ WRONG - Too Granular: - -Tasks: - - PHASE 1: Ask user question 1 - - PHASE 1: Ask user question 2 - - PHASE 1: Ask user question 3 - - PHASE 2: Read file A - - PHASE 2: Read file B - - PHASE 2: Write file C - - ... (50 micro-tasks) - -Problem: Too many updates, clutters user interface -``` - -**Multi-Step Phases: Break Into 2-3 Sub-Tasks:** - -For complex phases (>5 minutes), break into 2-3 sub-tasks: - -``` -✅ CORRECT - Sub-Task Breakdown: - -PHASE 3: Implementation (15 min total) - → Sub-tasks: - - PHASE 3: Implement core logic (5 min) - - PHASE 3: Add error handling (3 min) - - PHASE 3: Write tests (7 min) - -User sees progress within phase: "PHASE 3: 2/3 complete" - -❌ WRONG - Single Monolithic Task: - -PHASE 3: Implementation (15 min) - → No sub-tasks - -Problem: User sees "in_progress" for 15 min with no updates -``` - -**Avoid Too Many Tasks:** - -Limit to **max 15-20 tasks** for readability: - -``` -✅ CORRECT - 12 Tasks (readable): - -10-phase workflow: - - PHASE 1: Ask user - - PHASE 2: Plan (2 sub-tasks) - - PHASE 3: Implement (3 sub-tasks) - - PHASE 4: Test - - PHASE 5: Review (2 sub-tasks) - - PHASE 6: Fix issues - - PHASE 7: Re-review - - PHASE 8: Accept - -Total: 12 tasks (clean, trackable) - -❌ WRONG - 50 Tasks (overwhelming): - -Every single action as separate task: - - Read file 1 - - Read file 2 - - Write file 3 - - Run command 1 - - ... (50 tasks) - -Problem: User overwhelmed, can't see forest for trees -``` - -**Guideline by Workflow Duration:** - -``` -Workflow Duration → Task Count: - -< 5 minutes: 3-5 tasks -5-15 minutes: 8-12 tasks -15-30 minutes: 12-18 tasks -> 30 minutes: 15-20 tasks (if more, group into phases) - -Example: - 5-minute workflow (3 phases): - - PHASE 1: Prepare - - PHASE 2: Execute - - PHASE 3: Present - Total: 3 tasks ✓ - - 20-minute workflow (6 phases): - - PHASE 1: Ask user - - PHASE 2: Plan (2 sub-tasks) - - PHASE 3: Implement (3 sub-tasks) - - PHASE 4: Test - - PHASE 5: Review (2 sub-tasks) - - PHASE 6: Accept - Total: 11 tasks ✓ -``` - ---- - -### Pattern 3: Status Transitions - -**Exactly ONE Task In Progress at a Time:** - -Maintain the invariant: **exactly one task in_progress** at any moment: - -``` -✅ CORRECT - One In-Progress: - -State at time T1: - [✓] PHASE 1: Ask user (completed) - [✓] PHASE 2: Plan (completed) - [→] PHASE 3: Implement (in_progress) ← Only one - [ ] PHASE 4: Test (pending) - [ ] PHASE 5: Review (pending) - -State at time T2 (after PHASE 3 completes): - [✓] PHASE 1: Ask user (completed) - [✓] PHASE 2: Plan (completed) - [✓] PHASE 3: Implement (completed) - [→] PHASE 4: Test (in_progress) ← Only one - [ ] PHASE 5: Review (pending) - -❌ WRONG - Multiple In-Progress: - -State: - [✓] PHASE 1: Ask user (completed) - [→] PHASE 2: Plan (in_progress) ← Two in-progress? - [→] PHASE 3: Implement (in_progress) ← Confusing! - [ ] PHASE 4: Test (pending) - -Problem: User confused about current phase -``` - -**Status Transition Sequence:** - -``` -Lifecycle of a Task: - -1. Created: pending - (Task exists, not started yet) - -2. Started: pending → in_progress - (Mark as in_progress when starting work) - -3. Completed: in_progress → completed - (Mark as completed immediately after finishing) - -4. Next task: Mark next task as in_progress - (Continue to next task) - -Example Timeline: - -T=0s: [→] Task 1 (in_progress), [ ] Task 2 (pending) -T=30s: [✓] Task 1 (completed), [→] Task 2 (in_progress) -T=60s: [✓] Task 1 (completed), [✓] Task 2 (completed) -``` - -**NEVER Batch Completions:** - -Mark tasks completed **immediately** after finishing, not at end of phase: - -``` -✅ CORRECT - Immediate Updates: - -Mark "PHASE 1: Ask user" as in_progress -... do work (30s) ... -Mark "PHASE 1: Ask user" as completed ← Immediate - -Mark "PHASE 1: Validate inputs" as in_progress -... do work (20s) ... -Mark "PHASE 1: Validate inputs" as completed ← Immediate - -User sees real-time progress - -❌ WRONG - Batched Updates: - -Mark "PHASE 1: Ask user" as in_progress -... do work (30s) ... - -Mark "PHASE 1: Validate inputs" as in_progress -... do work (20s) ... - -(At end of PHASE 1, batch update both to completed) - -Problem: User doesn't see progress for 50s, thinks workflow is stuck -``` - ---- - -### Pattern 4: Real-Time Progress Tracking - -**Update TodoWrite As Work Progresses:** - -TodoWrite should reflect **current state**, not past state: - -``` -✅ CORRECT - Real-Time Updates: - -T=0s: Initialize TodoWrite (8 tasks, all pending) -T=5s: Mark "PHASE 1" as in_progress -T=35s: Mark "PHASE 1" as completed, "PHASE 2" as in_progress -T=90s: Mark "PHASE 2" as completed, "PHASE 3" as in_progress -... - -User always sees accurate current state - -❌ WRONG - Delayed Updates: - -T=0s: Initialize TodoWrite -T=300s: Workflow completes -T=301s: Update all tasks to completed - -Problem: No progress visibility for 5 minutes -``` - -**Add New Tasks If Discovered During Execution:** - -If you discover additional work during execution, add new tasks: - -``` -Scenario: During implementation, realize refactoring needed - -Initial TodoWrite: - [✓] PHASE 1: Plan - [→] PHASE 2: Implement - [ ] PHASE 3: Test - [ ] PHASE 4: Review - -During PHASE 2, discover: - "Implementation requires refactoring legacy code" - -Updated TodoWrite: - [✓] PHASE 1: Plan - [✓] PHASE 2: Implement core logic (completed) - [→] PHASE 2: Refactor legacy code (in_progress) ← New task added - [ ] PHASE 3: Test - [ ] PHASE 4: Review - -User sees: "Additional work discovered: refactoring. Total now 5 tasks." -``` - -**User Can See Current Progress at Any Time:** - -With real-time updates, user can check progress: - -``` -User checks at T=120s: - -TodoWrite State: - [✓] PHASE 1: Ask user - [✓] PHASE 2: Plan architecture - [→] PHASE 3: Implement core logic (in_progress) - [ ] PHASE 3: Add error handling - [ ] PHASE 3: Write tests - [ ] PHASE 4: Code review - [ ] PHASE 5: Accept - -User sees: "3/8 tasks complete (37.5%), currently implementing core logic" -``` - ---- - -### Pattern 5: Iteration Loop Tracking - -**Create Task Per Iteration:** - -For iteration loops, create a task for each iteration: - -``` -✅ CORRECT - Iteration Tasks: - -Design Validation Loop (max 10 iterations): - -Initial TodoWrite: - [ ] Iteration 1/10: Designer validation - [ ] Iteration 2/10: Designer validation - [ ] Iteration 3/10: Designer validation - ... (create all 10 upfront) - -Progress: - [✓] Iteration 1/10: Designer validation (NEEDS IMPROVEMENT) - [✓] Iteration 2/10: Designer validation (NEEDS IMPROVEMENT) - [→] Iteration 3/10: Designer validation (in_progress) - [ ] Iteration 4/10: Designer validation - ... - -User sees: "Iteration 3/10 in progress, 2 complete" - -❌ WRONG - Single Loop Task: - -TodoWrite: - [→] Design validation loop (in_progress) - -Problem: User sees "in_progress" for 10 minutes, no iteration visibility -``` - -**Mark Iteration Complete When Done:** - -``` -Iteration Lifecycle: - -Iteration 1: - Mark "Iteration 1/10" as in_progress - Run designer validation - If NEEDS IMPROVEMENT: Run developer fixes - Mark "Iteration 1/10" as completed - -Iteration 2: - Mark "Iteration 2/10" as in_progress - Run designer validation - If PASS: Exit loop early - Mark "Iteration 2/10" as completed - -Result: Loop exited after 2 iterations - [✓] Iteration 1/10 (completed) - [✓] Iteration 2/10 (completed) - [ ] Iteration 3/10 (not needed, loop exited) - ... - -User sees: "Loop completed in 2/10 iterations" -``` - -**Track Total Iterations vs Max Limit:** - -``` -Iteration Progress: - -Max: 10 iterations -Current: 5 - -TodoWrite State: - [✓] Iteration 1/10 - [✓] Iteration 2/10 - [✓] Iteration 3/10 - [✓] Iteration 4/10 - [→] Iteration 5/10 - [ ] Iteration 6/10 - ... - -User sees: "Iteration 5/10 (50% through max)" - -Warning at Iteration 8: - "Iteration 8/10 - approaching max, may escalate to user if not PASS" -``` - -**Clear Progress Visibility:** - -``` -Iteration Loop with TodoWrite: - -User Request: "Validate UI design" - -TodoWrite: - [✓] PHASE 1: Gather design reference - [✓] Iteration 1/10: Designer validation (5 issues found) - [✓] Iteration 2/10: Designer validation (3 issues found) - [✓] Iteration 3/10: Designer validation (1 issue found) - [→] Iteration 4/10: Designer validation (in_progress) - [ ] Iteration 5/10: Designer validation - ... - [ ] PHASE 3: User validation gate - -User sees: - - 4 iterations completed (40% through max) - - Issues reducing each iteration (5 → 3 → 1) - - Progress toward PASS -``` - ---- - -### Pattern 6: Parallel Task Tracking - -**Multiple Agents Executing Simultaneously:** - -When running agents in parallel, track each separately: - -``` -✅ CORRECT - Separate Tasks for Parallel Agents: - -Multi-Model Review (3 models in parallel): - -TodoWrite: - [✓] PHASE 1: Prepare review context - [→] PHASE 2: Claude review (in_progress) - [→] PHASE 2: Grok review (in_progress) - [→] PHASE 2: Gemini review (in_progress) - [ ] PHASE 3: Consolidate reviews - -Note: 3 tasks "in_progress" is OK for parallel execution - (Exception to "one in_progress" rule) - -As models complete: - [✓] PHASE 1: Prepare review context - [✓] PHASE 2: Claude review (completed) ← First to finish - [→] PHASE 2: Grok review (in_progress) - [→] PHASE 2: Gemini review (in_progress) - [ ] PHASE 3: Consolidate reviews - -User sees: "1/3 reviews complete, 2 in progress" - -❌ WRONG - Single Task for Parallel Work: - -TodoWrite: - [✓] PHASE 1: Prepare - [→] PHASE 2: Run 3 reviews (in_progress) - [ ] PHASE 3: Consolidate - -Problem: No visibility into which reviews are complete -``` - -**Update As Each Agent Completes:** - -``` -Parallel Execution Timeline: - -T=0s: Launch 3 reviews in parallel - [→] Claude review (in_progress) - [→] Grok review (in_progress) - [→] Gemini review (in_progress) - -T=60s: Claude completes first - [✓] Claude review (completed) - [→] Grok review (in_progress) - [→] Gemini review (in_progress) - -T=120s: Gemini completes - [✓] Claude review (completed) - [→] Grok review (in_progress) - [✓] Gemini review (completed) - -T=180s: Grok completes - [✓] Claude review (completed) - [✓] Grok review (completed) - [✓] Gemini review (completed) - -User sees real-time completion updates -``` - -**Progress Indicators During Long Parallel Tasks:** - -``` -For long-running parallel tasks (>2 minutes), show progress: - -T=0s: "Launching 5 AI model reviews (estimated 5 minutes)..." -T=60s: "1/5 reviews complete..." -T=120s: "2/5 reviews complete..." -T=180s: "4/5 reviews complete, 1 in progress..." -T=240s: "All reviews complete! Consolidating results..." - -TodoWrite mirrors this: - [✓] Claude review (1/5 complete) - [✓] Grok review (2/5 complete) - [→] Gemini review (in_progress) - [→] GPT-5 review (in_progress) - [→] DeepSeek review (in_progress) -``` - ---- - -## Integration with Other Skills - -**todowrite-orchestration + multi-agent-coordination:** - -``` -Use Case: Multi-phase implementation workflow - -Step 1: Initialize TodoWrite (todowrite-orchestration) - Create task list for all 8 phases - -Step 2: Sequential Agent Delegation (multi-agent-coordination) - Phase 1: api-architect - Mark PHASE 1 as in_progress - Delegate to api-architect - Mark PHASE 1 as completed - - Phase 2: backend-developer - Mark PHASE 2 as in_progress - Delegate to backend-developer - Mark PHASE 2 as completed - - ... continue for all phases -``` - -**todowrite-orchestration + multi-model-validation:** - -``` -Use Case: Multi-model review with progress tracking - -Step 1: Initialize TodoWrite (todowrite-orchestration) - [ ] PHASE 1: Prepare context - [ ] PHASE 2: Launch reviews (5 models) - [ ] PHASE 3: Consolidate results - -Step 2: Parallel Execution (multi-model-validation) - Mark "PHASE 2: Launch reviews" as in_progress - Launch all 5 models simultaneously - As each completes: Update progress (1/5, 2/5, ...) - Mark "PHASE 2: Launch reviews" as completed - -Step 3: Real-Time Visibility (todowrite-orchestration) - User sees: "PHASE 2: 3/5 reviews complete..." -``` - -**todowrite-orchestration + quality-gates:** - -``` -Use Case: Iteration loop with TodoWrite tracking - -Step 1: Initialize TodoWrite (todowrite-orchestration) - [ ] Iteration 1/10 - [ ] Iteration 2/10 - ... - -Step 2: Iteration Loop (quality-gates) - For i = 1 to 10: - Mark "Iteration i/10" as in_progress - Run designer validation - If PASS: Exit loop - Mark "Iteration i/10" as completed - -Step 3: Progress Visibility - User sees: "Iteration 5/10 complete, 5 remaining" -``` - ---- - -## Best Practices - -**Do:** -- ✅ Initialize TodoWrite BEFORE starting work (step 0) -- ✅ List ALL phases upfront (user sees complete scope) -- ✅ Use 8-15 tasks for typical workflows (readable) -- ✅ Mark completed IMMEDIATELY after finishing (real-time) -- ✅ Keep exactly ONE task in_progress (except parallel tasks) -- ✅ Track iterations separately (Iteration 1/10, 2/10, ...) -- ✅ Update as work progresses (not batched at end) -- ✅ Add new tasks if discovered during execution - -**Don't:** -- ❌ Create TodoWrite during workflow (initialize first) -- ❌ Hide phases from user (list all upfront) -- ❌ Create too many tasks (>20 overwhelms user) -- ❌ Batch completions at end of phase (update real-time) -- ❌ Leave multiple tasks in_progress (pick one) -- ❌ Use single task for loop (track iterations separately) -- ❌ Update only at start/end (update during execution) - -**Performance:** -- TodoWrite overhead: <1s per update (negligible) -- User visibility benefit: Reduces perceived wait time 30-50% -- Workflow confidence: User knows progress, less likely to cancel - ---- - -## Examples - -### Example 1: 8-Phase Implementation Workflow - -**Scenario:** Full-cycle implementation with TodoWrite tracking - -**Execution:** - -``` -Step 0: Initialize TodoWrite - TodoWrite: Create task list - [ ] PHASE 1: Ask user for requirements - [ ] PHASE 2: Generate architecture plan - [ ] PHASE 3: Implement core logic - [ ] PHASE 3: Add error handling - [ ] PHASE 3: Write tests - [ ] PHASE 4: Run test suite - [ ] PHASE 5: Code review - [ ] PHASE 6: Fix review issues - [ ] PHASE 7: User acceptance - [ ] PHASE 8: Generate report - - User sees: "10 tasks, 0 complete, Phase 1 starting..." - -Step 1: PHASE 1 - Mark "PHASE 1: Ask user" as in_progress - ... gather requirements (30s) ... - Mark "PHASE 1: Ask user" as completed - User sees: "1/10 tasks complete (10%)" - -Step 2: PHASE 2 - Mark "PHASE 2: Architecture plan" as in_progress - ... generate plan (2 min) ... - Mark "PHASE 2: Architecture plan" as completed - User sees: "2/10 tasks complete (20%)" - -Step 3: PHASE 3 (3 sub-tasks) - Mark "PHASE 3: Implement core" as in_progress - ... implement (3 min) ... - Mark "PHASE 3: Implement core" as completed - User sees: "3/10 tasks complete (30%)" - - Mark "PHASE 3: Add error handling" as in_progress - ... add error handling (2 min) ... - Mark "PHASE 3: Add error handling" as completed - User sees: "4/10 tasks complete (40%)" - - Mark "PHASE 3: Write tests" as in_progress - ... write tests (3 min) ... - Mark "PHASE 3: Write tests" as completed - User sees: "5/10 tasks complete (50%)" - -... continue through all phases ... - -Final State: - [✓] All 10 tasks completed - User sees: "10/10 tasks complete (100%). Workflow finished!" - -Total Duration: ~15 minutes -User Experience: Continuous progress updates every 1-3 minutes -``` - ---- - -### Example 2: Iteration Loop with Progress Tracking - -**Scenario:** Design validation with 10 max iterations - -**Execution:** - -``` -Step 0: Initialize TodoWrite - TodoWrite: Create task list - [ ] PHASE 1: Gather design reference - [ ] Iteration 1/10: Designer validation - [ ] Iteration 2/10: Designer validation - [ ] Iteration 3/10: Designer validation - [ ] Iteration 4/10: Designer validation - [ ] Iteration 5/10: Designer validation - ... (10 iterations total) - [ ] PHASE 3: User validation gate - -Step 1: PHASE 1 - Mark "PHASE 1: Gather design" as in_progress - ... gather design (20s) ... - Mark "PHASE 1: Gather design" as completed - -Step 2: Iteration Loop - Iteration 1: - Mark "Iteration 1/10" as in_progress - Designer: "NEEDS IMPROVEMENT - 5 issues" - Developer: Fix 5 issues - Mark "Iteration 1/10" as completed - User sees: "Iteration 1/10 complete, 5 issues fixed" - - Iteration 2: - Mark "Iteration 2/10" as in_progress - Designer: "NEEDS IMPROVEMENT - 3 issues" - Developer: Fix 3 issues - Mark "Iteration 2/10" as completed - User sees: "Iteration 2/10 complete, 3 issues fixed" - - Iteration 3: - Mark "Iteration 3/10" as in_progress - Designer: "NEEDS IMPROVEMENT - 1 issue" - Developer: Fix 1 issue - Mark "Iteration 3/10" as completed - User sees: "Iteration 3/10 complete, 1 issue fixed" - - Iteration 4: - Mark "Iteration 4/10" as in_progress - Designer: "PASS ✓" - Mark "Iteration 4/10" as completed - Exit loop (early exit) - User sees: "Loop completed in 4/10 iterations" - -Step 3: PHASE 3 - Mark "PHASE 3: User validation" as in_progress - ... user validates ... - Mark "PHASE 3: User validation" as completed - -Final State: - [✓] PHASE 1: Gather design - [✓] Iteration 1/10 (5 issues fixed) - [✓] Iteration 2/10 (3 issues fixed) - [✓] Iteration 3/10 (1 issue fixed) - [✓] Iteration 4/10 (PASS) - [ ] Iteration 5/10 (not needed) - ... - [✓] PHASE 3: User validation - -User Experience: Clear iteration progress, early exit visible -``` - ---- - -### Example 3: Parallel Multi-Model Review - -**Scenario:** 5 AI models reviewing code in parallel - -**Execution:** - -``` -Step 0: Initialize TodoWrite - TodoWrite: Create task list - [ ] PHASE 1: Prepare review context - [ ] PHASE 2: Claude review - [ ] PHASE 2: Grok review - [ ] PHASE 2: Gemini review - [ ] PHASE 2: GPT-5 review - [ ] PHASE 2: DeepSeek review - [ ] PHASE 3: Consolidate reviews - [ ] PHASE 4: Present results - -Step 1: PHASE 1 - Mark "PHASE 1: Prepare context" as in_progress - ... prepare (30s) ... - Mark "PHASE 1: Prepare context" as completed - -Step 2: PHASE 2 (Parallel Execution) - Mark all 5 reviews as in_progress: - [→] Claude review - [→] Grok review - [→] Gemini review - [→] GPT-5 review - [→] DeepSeek review - - Launch all 5 in parallel (4-Message Pattern) - - As each completes: - T=60s: Claude completes - [✓] Claude review - User sees: "1/5 reviews complete" - - T=90s: Gemini completes - [✓] Gemini review - User sees: "2/5 reviews complete" - - T=120s: GPT-5 completes - [✓] GPT-5 review - User sees: "3/5 reviews complete" - - T=150s: Grok completes - [✓] Grok review - User sees: "4/5 reviews complete" - - T=180s: DeepSeek completes - [✓] DeepSeek review - User sees: "5/5 reviews complete!" - -Step 3: PHASE 3 - Mark "PHASE 3: Consolidate" as in_progress - ... consolidate (30s) ... - Mark "PHASE 3: Consolidate" as completed - -Step 4: PHASE 4 - Mark "PHASE 4: Present results" as in_progress - ... present (10s) ... - Mark "PHASE 4: Present results" as completed - -Final State: - [✓] All 8 tasks completed - User sees: "Multi-model review complete in 3 minutes" - -User Experience: - - Real-time progress as each model completes - - Clear visibility: "3/5 reviews complete" - - Reduces perceived wait time (user knows progress) -``` - ---- - -## Troubleshooting - -**Problem: User thinks workflow is stuck** - -Cause: No TodoWrite updates for >1 minute - -Solution: Update TodoWrite more frequently, or add sub-tasks - -``` -❌ Wrong: - [→] PHASE 3: Implementation (in_progress for 10 minutes) - -✅ Correct: - [✓] PHASE 3: Implement core logic (2 min) - [✓] PHASE 3: Add error handling (3 min) - [→] PHASE 3: Write tests (in_progress, 2 min so far) - -User sees progress every 2-3 minutes -``` - ---- - -**Problem: Too many tasks (>20), overwhelming** - -Cause: Too granular task breakdown - -Solution: Group micro-tasks into larger operations - -``` -❌ Wrong (25 tasks): - [ ] Read file 1 - [ ] Read file 2 - [ ] Write file 3 - ... (25 micro-tasks) - -✅ Correct (8 tasks): - [ ] PHASE 1: Gather inputs (includes reading files) - [ ] PHASE 2: Process data - ... (8 significant operations) -``` - ---- - -**Problem: Multiple tasks "in_progress" (not parallel execution)** - -Cause: Forgot to mark previous task as completed - -Solution: Always mark completed before starting next - -``` -❌ Wrong: - [→] PHASE 1: Ask user (in_progress) - [→] PHASE 2: Plan (in_progress) ← Both in_progress? - -✅ Correct: - [✓] PHASE 1: Ask user (completed) - [→] PHASE 2: Plan (in_progress) ← Only one -``` - ---- - -## Summary - -TodoWrite orchestration provides real-time progress visibility through: - -- **Phase initialization** (create task list before starting) -- **Appropriate granularity** (8-15 tasks, significant operations) -- **Real-time updates** (mark completed immediately) -- **Exactly one in_progress** (except parallel execution) -- **Iteration tracking** (separate task per iteration) -- **Parallel task tracking** (update as each completes) - -Master these patterns and users will always know: -- What's happening now -- What's coming next -- How much progress has been made -- How much remains - -This transforms "black box" workflows into transparent, trackable processes. - ---- - -**Extracted From:** -- `/review` command (10-task initialization, phase-based tracking) -- `/implement` command (8-phase workflow with sub-tasks) -- `/validate-ui` command (iteration tracking, user feedback rounds) -- All multi-phase orchestration workflows diff --git a/plugins/nanobanana/agents/image-generator.md b/plugins/nanobanana/agents/image-generator.md index 56ce8dd..b79567e 100644 --- a/plugins/nanobanana/agents/image-generator.md +++ b/plugins/nanobanana/agents/image-generator.md @@ -3,7 +3,7 @@ name: image-generator description: Generate or edit images using Gemini with style templates and reference images model: sonnet color: green -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep skills: nanobanana:gemini-api, nanobanana:style-format --- @@ -29,7 +29,7 @@ skills: nanobanana:gemini-api, nanobanana:style-format - You MUST use TodoWrite to track generation workflow: + You MUST use Tasks to track generation workflow: **Before starting**, create todo list: 1. Parse generation request @@ -89,7 +89,7 @@ skills: nanobanana:gemini-api, nanobanana:style-format - Initialize TodoWrite + Initialize Tasks Identify operation type: - Generate: new image from text - Edit: modify existing image (--edit) diff --git a/plugins/nanobanana/agents/style-manager.md b/plugins/nanobanana/agents/style-manager.md index 874bdb1..2352b44 100644 --- a/plugins/nanobanana/agents/style-manager.md +++ b/plugins/nanobanana/agents/style-manager.md @@ -3,7 +3,7 @@ name: style-manager description: Manage image generation style templates (create, update, list, show, delete) model: sonnet color: green -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion skills: nanobanana:style-format --- @@ -29,7 +29,7 @@ skills: nanobanana:style-format - You MUST use TodoWrite to track style operations: + You MUST use Tasks to track style operations: **Before starting**, create todo list: 1. Validate operation request @@ -83,7 +83,7 @@ skills: nanobanana:style-format - Initialize TodoWrite + Initialize Tasks Determine operation (create/update/delete/list/show) Extract style name diff --git a/plugins/nanobanana/commands/edit.md b/plugins/nanobanana/commands/edit.md index 1b5893a..653c538 100644 --- a/plugins/nanobanana/commands/edit.md +++ b/plugins/nanobanana/commands/edit.md @@ -1,6 +1,6 @@ --- description: Edit existing images with natural language instructions -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: nanobanana:gemini-api --- @@ -17,7 +17,7 @@ skills: nanobanana:gemini-api - Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep + Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep Write, Edit diff --git a/plugins/nanobanana/commands/generate.md b/plugins/nanobanana/commands/generate.md index 3183b7d..5e61660 100644 --- a/plugins/nanobanana/commands/generate.md +++ b/plugins/nanobanana/commands/generate.md @@ -1,6 +1,6 @@ --- description: Generate images from text prompts with optional styles and aspect ratios -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: nanobanana:gemini-api --- @@ -17,7 +17,7 @@ skills: nanobanana:gemini-api - Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep + Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep Write, Edit diff --git a/plugins/nanobanana/commands/style.md b/plugins/nanobanana/commands/style.md index 14f2bf3..d46ab47 100644 --- a/plugins/nanobanana/commands/style.md +++ b/plugins/nanobanana/commands/style.md @@ -1,6 +1,6 @@ --- description: Manage image generation style templates (create, list, show, delete, update) -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: nanobanana:style-format --- @@ -17,7 +17,7 @@ skills: nanobanana:style-format - Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep + Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep Write, Edit diff --git a/plugins/seo/agents/analyst.md b/plugins/seo/agents/analyst.md index 22ff05d..52399ac 100644 --- a/plugins/seo/agents/analyst.md +++ b/plugins/seo/agents/analyst.md @@ -3,7 +3,7 @@ name: seo-analyst description: SERP analysis expert for search intent, competitive intelligence, and ranking opportunities model: sonnet color: purple -tools: TodoWrite, Read, Write, Bash, WebSearch, WebFetch, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, WebSearch, WebFetch, Glob, Grep skills: seo:serp-analysis, seo:keyword-cluster-builder --- @@ -162,7 +162,7 @@ skills: seo:serp-analysis, seo:keyword-cluster-builder - You MUST use TodoWrite to track your analysis workflow: + You MUST use Tasks to track your analysis workflow: 1. Gather keyword and context 2. Perform SERP analysis via WebSearch 3. Fetch and analyze top competitors via WebFetch @@ -278,7 +278,7 @@ skills: seo:serp-analysis, seo:keyword-cluster-builder - Initialize TodoWrite with analysis phases + Initialize Tasks with analysis phases Use WebSearch to fetch SERP for target keyword Note SERP features (featured snippets, PAA, images, videos, local pack) Extract top 10 organic results with titles, URLs, meta descriptions diff --git a/plugins/seo/agents/data-analyst.md b/plugins/seo/agents/data-analyst.md index a5932dd..484ab0f 100644 --- a/plugins/seo/agents/data-analyst.md +++ b/plugins/seo/agents/data-analyst.md @@ -4,7 +4,7 @@ description: Analytics specialist for GA4 and Google Search Console performance model: sonnet model-id: claude-sonnet-4-20250514 color: cyan -tools: TodoWrite, Read, Write, Bash, WebFetch +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Bash, WebFetch skills: seo:analytics-interpretation, seo:performance-correlation, seo:data-extraction-patterns --- diff --git a/plugins/seo/agents/editor.md b/plugins/seo/agents/editor.md index 1eaf44e..b51125d 100644 --- a/plugins/seo/agents/editor.md +++ b/plugins/seo/agents/editor.md @@ -3,7 +3,7 @@ name: seo-editor description: Senior SEO editor and quality gate for content approval with E-E-A-T scoring model: opus color: cyan -tools: TodoWrite, Read, Write, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Glob, Grep skills: seo:content-optimizer --- @@ -211,7 +211,7 @@ skills: seo:content-optimizer - You MUST use TodoWrite to track review workflow: + You MUST use Tasks to track review workflow: 1. Read content and original brief 2. Validate SEO technical requirements 3. Assess E-E-A-T signals diff --git a/plugins/seo/agents/researcher.md b/plugins/seo/agents/researcher.md index 7c75e85..f580596 100644 --- a/plugins/seo/agents/researcher.md +++ b/plugins/seo/agents/researcher.md @@ -3,7 +3,7 @@ name: seo-researcher description: Keyword research specialist for expansion, clustering, and content gap analysis model: sonnet color: blue -tools: TodoWrite, Read, Write, WebSearch, WebFetch, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, WebSearch, WebFetch, Glob, Grep skills: seo:keyword-cluster-builder, seo:content-brief --- @@ -162,7 +162,7 @@ skills: seo:keyword-cluster-builder, seo:content-brief - You MUST use TodoWrite to track research workflow: + You MUST use Tasks to track research workflow: 1. Gather seed keyword(s) 2. Expand to related terms 3. Classify intent for each term diff --git a/plugins/seo/agents/writer.md b/plugins/seo/agents/writer.md index 373f947..7bd21ed 100644 --- a/plugins/seo/agents/writer.md +++ b/plugins/seo/agents/writer.md @@ -3,7 +3,7 @@ name: seo-writer description: SEO content writer that creates optimized articles from briefs with E-E-A-T focus model: sonnet color: green -tools: TodoWrite, Read, Write, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Glob, Grep skills: seo:content-optimizer, seo:link-strategy --- @@ -171,7 +171,7 @@ skills: seo:content-optimizer, seo:link-strategy - You MUST use TodoWrite to track writing workflow: + You MUST use Tasks to track writing workflow: 1. Read and understand content brief 2. Create outline with keyword placement 3. Write introduction (hook + keyword) diff --git a/plugins/seo/commands/alternatives.md b/plugins/seo/commands/alternatives.md index 8de01a7..fd2a042 100644 --- a/plugins/seo/commands/alternatives.md +++ b/plugins/seo/commands/alternatives.md @@ -1,6 +1,6 @@ --- description: Parallel content generation orchestrator using multiple AI models for A/B testing and hybrid optimization -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: orchestration:multi-model-validation, orchestration:model-tracking-protocol, orchestration:quality-gates, seo:content-brief --- @@ -37,7 +37,7 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto - Use Task tool to delegate ALL content generation to seo-writer agent - Use Bash to prepare content briefs and manage session - Use Read/Glob/Grep to understand context - - Use TodoWrite to track workflow progress (all 5 phases) + - Use Tasks to track workflow progress (all 5 phases) - Use AskUserQuestion for user input and selection - Execute generation tasks in PARALLEL (single message, multiple Task calls) @@ -70,19 +70,19 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto Task: seo-writer PROXY_MODE: model-3 ... - - You MUST use TodoWrite to track workflow: + + You MUST use Tasks to track workflow: 1. PHASE 0: Initialize session 2. PHASE 1: Define content type and brief 3. PHASE 2: Select models and approve costs 4. PHASE 3: Generate alternatives in parallel 5. PHASE 4: Compare and score alternatives 6. PHASE 5: Present results and enable selection - + - Initialize session and TodoWrite + Initialize session and Tasks PHASE 1: Define content type (headline/meta/angle) and requirements PHASE 2: Select AI models and approve costs PHASE 3: Generate alternatives in parallel @@ -116,7 +116,7 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto - Read (read generated alternatives) - Glob (find alternative files) - Grep (search patterns) - - TodoWrite (track progress) + - Tasks (track progress) - AskUserQuestion (user input and selection) @@ -146,7 +146,7 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto Initialize session metadata - Initialize TodoWrite with 6 phases + Initialize Tasks with 6 phases diff --git a/plugins/seo/commands/audit.md b/plugins/seo/commands/audit.md index 5a1cc32..5bc3350 100644 --- a/plugins/seo/commands/audit.md +++ b/plugins/seo/commands/audit.md @@ -1,6 +1,6 @@ --- description: Technical SEO audit for crawlability, Core Web Vitals, schema markup, and on-page SEO -allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep, WebFetch +allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep, WebFetch skills: seo:technical-audit, seo:schema-markup, orchestration:error-recovery --- @@ -76,7 +76,7 @@ skills: seo:technical-audit, seo:schema-markup, orchestration:error-recovery Generate SESSION_PATH Create session directory - Initialize TodoWrite + Initialize Tasks diff --git a/plugins/seo/commands/brief.md b/plugins/seo/commands/brief.md index db97e4d..18b6d0c 100644 --- a/plugins/seo/commands/brief.md +++ b/plugins/seo/commands/brief.md @@ -1,6 +1,6 @@ --- description: Generate comprehensive content brief from keyword with multi-agent orchestration -allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: orchestration:multi-agent-coordination, seo:content-brief --- @@ -48,7 +48,7 @@ skills: orchestration:multi-agent-coordination, seo:content-brief Generate SESSION_PATH Create session directory - Initialize TodoWrite + Initialize Tasks diff --git a/plugins/seo/commands/optimize.md b/plugins/seo/commands/optimize.md index 083414a..41df83d 100644 --- a/plugins/seo/commands/optimize.md +++ b/plugins/seo/commands/optimize.md @@ -1,6 +1,6 @@ --- description: Optimize existing content for SEO with keyword density, meta tags, headings, and optional multi-model validation -allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: orchestration:quality-gates, orchestration:multi-model-validation, seo:content-optimizer --- @@ -75,7 +75,7 @@ skills: orchestration:quality-gates, orchestration:multi-model-validation, seo:c Generate SESSION_PATH with timestamp and keyword Create session directory - Initialize TodoWrite + Initialize Tasks diff --git a/plugins/seo/commands/performance.md b/plugins/seo/commands/performance.md index 965346c..53855bf 100644 --- a/plugins/seo/commands/performance.md +++ b/plugins/seo/commands/performance.md @@ -1,6 +1,6 @@ --- description: Content performance analysis combining GA4 and GSC data for optimization recommendations -allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TodoWrite, WebFetch +allowed-tools: Task, AskUserQuestion, Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, TaskGet, WebFetch skills: seo:analytics-interpretation, seo:performance-correlation, seo:data-extraction-patterns, orchestration:multi-agent-coordination --- @@ -77,7 +77,7 @@ skills: seo:analytics-interpretation, seo:performance-correlation, seo:data-extr Generate SESSION_PATH with timestamp and URL slug Create session directory Check analytics environment variables - Initialize TodoWrite with 5 phases + Initialize Tasks with 5 phases diff --git a/plugins/seo/commands/research.md b/plugins/seo/commands/research.md index 3c4ce5c..6e80fad 100644 --- a/plugins/seo/commands/research.md +++ b/plugins/seo/commands/research.md @@ -1,6 +1,6 @@ --- description: Comprehensive keyword research with multi-agent orchestration for clusters and recommendations -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: orchestration:multi-agent-coordination, orchestration:quality-gates, orchestration:error-recovery, seo:quality-gate --- @@ -10,7 +10,7 @@ skills: orchestration:multi-agent-coordination, orchestration:quality-gates, orc - Multi-agent coordination for keyword research - Session-based artifact management - User approval gates - - Progress tracking via TodoWrite + - Progress tracking via Tasks Orchestrate a comprehensive keyword research workflow using seo-analyst @@ -30,7 +30,7 @@ skills: orchestration:multi-agent-coordination, orchestration:quality-gates, orc **You MUST:** - Use Task tool to delegate to seo-analyst and seo-researcher agents - - Use TodoWrite to track workflow progress + - Use Tasks to track workflow progress - Use AskUserQuestion for approval gates - Coordinate between agents @@ -63,7 +63,7 @@ skills: orchestration:multi-agent-coordination, orchestration:quality-gates, orc - Initialize TodoWrite with phases: + Initialize Tasks with phases: 1. PHASE 0: Initialize session workspace 2. PHASE 1: Gather seed keyword and research goals 3. PHASE 2: Analyst performs SERP analysis @@ -86,7 +86,7 @@ skills: orchestration:multi-agent-coordination, orchestration:quality-gates, orc Generate SESSION_PATH with timestamp and keyword hash Create directory: $SESSION_PATH/ Initialize session-meta.json with keyword, timestamp, status - Initialize TodoWrite with 6 phases + Initialize Tasks with 6 phases SESSION_PATH directory exists and is writable diff --git a/plugins/seo/commands/review.md b/plugins/seo/commands/review.md index 4674c96..d902eb9 100644 --- a/plugins/seo/commands/review.md +++ b/plugins/seo/commands/review.md @@ -1,6 +1,6 @@ --- description: Multi-model content review orchestrator with parallel E-E-A-T validation and consensus analysis -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: orchestration:multi-model-validation, orchestration:model-tracking-protocol, orchestration:quality-gates, seo:content-optimizer --- @@ -38,7 +38,7 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto - Use Task tool to delegate ALL reviews to seo-editor agent - Use Bash to prepare review context and manage session - Use Read/Glob/Grep to understand content - - Use TodoWrite to track workflow progress (all 5 phases) + - Use Tasks to track workflow progress (all 5 phases) - Use AskUserQuestion for user approval gates - Execute external reviews in PARALLEL (single message, multiple Task calls) @@ -76,11 +76,11 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto vs 15-30 min). See Key Design Innovation section in knowledge base. - - You MUST use the TodoWrite tool to create and maintain a todo list throughout + + You MUST use the Tasks system to create and maintain a todo list throughout your orchestration workflow. - **Before starting**, create a todo list with all workflow phases: + **Before starting**, create a task list with all workflow phases: 1. PHASE 0: Initialize session 2. PHASE 1: Gather content to review 3. PHASE 2: Model selection and cost approval @@ -93,11 +93,11 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto - Mark tasks as "completed" immediately after finishing - Add new tasks if additional work discovered - Keep only ONE task as "in_progress" at a time - + - Initialize session and TodoWrite with workflow tasks + Initialize session and Tasks with workflow tasks PHASE 1: Gather content to review and create review context PHASE 2: Select AI models for review and get cost approval PHASE 3: Execute ALL reviews in parallel @@ -134,7 +134,7 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto - Read (read content and review files) - Glob (expand file patterns) - Grep (search for patterns) - - TodoWrite (track workflow progress) + - Tasks (track workflow progress) - AskUserQuestion (user approval gates) @@ -206,7 +206,7 @@ skills: orchestration:multi-model-validation, orchestration:model-tracking-proto ``` - Initialize TodoWrite with 6 workflow tasks: + Initialize Tasks with 6 workflow tasks: 1. Initialize session 2. Gather content to review 3. Select models and get approval diff --git a/plugins/seo/commands/start.md b/plugins/seo/commands/start.md index 958e589..626e7ca 100644 --- a/plugins/seo/commands/start.md +++ b/plugins/seo/commands/start.md @@ -1,7 +1,7 @@ --- description: Interactive SEO workflow entry point that routes to appropriate commands or agents -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite -skills: orchestration:todowrite-orchestration +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet +skills: orchestration:task-orchestration --- @@ -41,7 +41,7 @@ skills: orchestration:todowrite-orchestration - Use TodoWrite to track workflow: + Use Tasks to track workflow: 1. Understand user goal 2. Route to appropriate command or workflow 3. Monitor execution (if multi-step) @@ -67,7 +67,7 @@ skills: orchestration:todowrite-orchestration Understand what the user wants to accomplish - Initialize TodoWrite with workflow phases + Initialize Tasks with workflow phases Mark PHASE 1 as in_progress Check if user provided arguments with clear intent If clear intent: Skip to routing (Phase 2) @@ -408,7 +408,7 @@ skills: orchestration:todowrite-orchestration **Phase 1: Goal Discovery** - 1. Initialize TodoWrite with 5 phases + 1. Initialize Tasks with 5 phases 2. Mark PHASE 1 as in_progress 3. Ask: "What would you like to accomplish today?" 4. User selects: "Create new content" @@ -466,7 +466,7 @@ skills: orchestration:todowrite-orchestration **Phase 1: Goal Discovery** - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Mark PHASE 1 as in_progress 3. Parse arguments: "improve" detected -> Improve existing content 4. Mark PHASE 1 as completed @@ -527,7 +527,7 @@ skills: orchestration:todowrite-orchestration **Phase 1: Goal Discovery** - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Mark PHASE 1 as in_progress 3. Parse arguments: "performance" + URL detected -> Direct route 4. Mark PHASE 1 as completed @@ -589,7 +589,7 @@ skills: orchestration:todowrite-orchestration **Phase 1: Goal Discovery** - 1. Initialize TodoWrite + 1. Initialize Tasks 2. Mark PHASE 1 as in_progress 3. Parse arguments: "track" + "performance" detected -> Check performance goal 4. Mark PHASE 1 as completed diff --git a/plugins/video-editing/agents/timeline-builder.md b/plugins/video-editing/agents/timeline-builder.md index 5013810..3a4eca3 100644 --- a/plugins/video-editing/agents/timeline-builder.md +++ b/plugins/video-editing/agents/timeline-builder.md @@ -3,7 +3,7 @@ name: timeline-builder description: Create Final Cut Pro projects, timelines, and multicam sequences model: sonnet color: green -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep skills: video-editing:final-cut-pro, video-editing:ffmpeg-core --- @@ -28,7 +28,7 @@ skills: video-editing:final-cut-pro, video-editing:ffmpeg-core - You MUST use TodoWrite to track timeline building workflow: + You MUST use Tasks to track timeline building workflow: **Before starting**, create todo list: 1. Analyze source media files @@ -79,7 +79,7 @@ skills: video-editing:final-cut-pro, video-editing:ffmpeg-core - Initialize TodoWrite with timeline building tasks + Initialize Tasks with timeline building tasks Mark "Analyze source media" as in_progress List all input media files For each file, extract with ffprobe: duration, resolution, frame rate, codec diff --git a/plugins/video-editing/agents/transcriber.md b/plugins/video-editing/agents/transcriber.md index fc3a716..7550219 100644 --- a/plugins/video-editing/agents/transcriber.md +++ b/plugins/video-editing/agents/transcriber.md @@ -3,7 +3,7 @@ name: transcriber description: Transcribe audio/video with Whisper to SRT, VTT, JSON, or TXT model: sonnet color: orange -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep skills: video-editing:transcription, video-editing:ffmpeg-core --- @@ -28,7 +28,7 @@ skills: video-editing:transcription, video-editing:ffmpeg-core - You MUST use TodoWrite to track transcription workflow: + You MUST use Tasks to track transcription workflow: **Before starting**, create todo list: 1. Check Whisper installation @@ -79,7 +79,7 @@ skills: video-editing:transcription, video-editing:ffmpeg-core - Initialize TodoWrite with transcription tasks + Initialize Tasks with transcription tasks Mark "Check Whisper installation" as in_progress Verify Whisper is installed: whisper --help Check available models: whisper --list-models (if supported) diff --git a/plugins/video-editing/agents/video-processor.md b/plugins/video-editing/agents/video-processor.md index 1358e25..a5d4daf 100644 --- a/plugins/video-editing/agents/video-processor.md +++ b/plugins/video-editing/agents/video-processor.md @@ -3,7 +3,7 @@ name: video-processor description: Process video/audio files using FFmpeg (trim, concat, convert, extract) model: sonnet color: green -tools: TodoWrite, Read, Write, Edit, Bash, Glob, Grep +tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash, Glob, Grep skills: video-editing:ffmpeg-core --- @@ -28,7 +28,7 @@ skills: video-editing:ffmpeg-core - You MUST use TodoWrite to track processing workflow: + You MUST use Tasks to track processing workflow: **Before starting**, create todo list: 1. Validate input files exist and are valid @@ -81,7 +81,7 @@ skills: video-editing:ffmpeg-core - Initialize TodoWrite with all processing tasks + Initialize Tasks with all processing tasks Mark "Validate input files" as in_progress Check input files exist using Bash Run ffprobe to get media properties diff --git a/plugins/video-editing/commands/create-fcp-project.md b/plugins/video-editing/commands/create-fcp-project.md index c5ba1fb..640fb4a 100644 --- a/plugins/video-editing/commands/create-fcp-project.md +++ b/plugins/video-editing/commands/create-fcp-project.md @@ -1,6 +1,6 @@ --- description: Create Final Cut Pro FCPXML projects with timelines and markers -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: video-editing:final-cut-pro, video-editing:ffmpeg-core --- @@ -36,7 +36,7 @@ skills: video-editing:final-cut-pro, video-editing:ffmpeg-core - Track workflow with TodoWrite: + Track workflow with Tasks: 1. Analyze input clips 2. Configure project settings 3. Delegate to timeline-builder @@ -133,7 +133,7 @@ skills: video-editing:final-cut-pro, video-editing:ffmpeg-core - Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep + Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep Write, Edit diff --git a/plugins/video-editing/commands/transcribe.md b/plugins/video-editing/commands/transcribe.md index a1f51c3..a2d68a3 100644 --- a/plugins/video-editing/commands/transcribe.md +++ b/plugins/video-editing/commands/transcribe.md @@ -1,6 +1,6 @@ --- description: Transcribe audio/video to SRT, VTT, JSON, or TXT formats -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: video-editing:transcription --- @@ -36,7 +36,7 @@ skills: video-editing:transcription - Track workflow with TodoWrite: + Track workflow with Tasks: 1. Check Whisper installation 2. Validate input files 3. Determine quality settings @@ -139,7 +139,7 @@ skills: video-editing:transcription - Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep + Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep Write, Edit diff --git a/plugins/video-editing/commands/video-edit.md b/plugins/video-editing/commands/video-edit.md index 8b01988..0c4d333 100644 --- a/plugins/video-editing/commands/video-edit.md +++ b/plugins/video-editing/commands/video-edit.md @@ -1,6 +1,6 @@ --- description: Main video editing orchestrator with multi-agent coordination -allowed-tools: Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep +allowed-tools: Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep skills: video-editing:ffmpeg-core, video-editing:transcription, video-editing:final-cut-pro --- @@ -33,7 +33,7 @@ skills: video-editing:ffmpeg-core, video-editing:transcription, video-editing:fi **You MUST:** - Use Task tool to delegate ALL processing to agents - Use Bash for dependency checks (ffmpeg, whisper) - - Use TodoWrite to track workflow progress + - Use Tasks to track workflow progress - Use AskUserQuestion for user decisions **You MUST NOT:** @@ -153,7 +153,7 @@ skills: video-editing:ffmpeg-core, video-editing:transcription, video-editing:fi - Task, AskUserQuestion, Bash, Read, TodoWrite, Glob, Grep + Task, AskUserQuestion, Bash, Read, TaskCreate, TaskUpdate, TaskList, TaskGet, Glob, Grep Write, Edit From a1ce1f4b52df71cccfcf920a6b80a3d8cf5d0abd Mon Sep 17 00:00:00 2001 From: Jack Rudenko Date: Sat, 31 Jan 2026 14:07:15 +1100 Subject: [PATCH 3/3] fix: resolve TypeScript errors in claudeup-core tests - Remove unused 'key' variable (use _key) - Remove unused imports (beforeEach, readdir, stat) - Fix duplicate export conflicts in index.ts --- .../src/__tests__/integration/mcp-discovery.test.ts | 2 +- .../src/__tests__/integration/plugin-loading.test.ts | 4 ++-- .../src/__tests__/utils/fixture-loader.ts | 2 +- tools/claudeup-core/src/__tests__/utils/index.ts | 12 +++++++++++- 4 files changed, 15 insertions(+), 5 deletions(-) diff --git a/tools/claudeup-core/src/__tests__/integration/mcp-discovery.test.ts b/tools/claudeup-core/src/__tests__/integration/mcp-discovery.test.ts index 31e2785..d4bdd6d 100644 --- a/tools/claudeup-core/src/__tests__/integration/mcp-discovery.test.ts +++ b/tools/claudeup-core/src/__tests__/integration/mcp-discovery.test.ts @@ -205,7 +205,7 @@ describe('mcp-discovery integration', () => { const varPattern = /^\$\{(\w+)\}$/; const extractedVars: string[] = []; - for (const [key, value] of Object.entries(envVars!)) { + for (const [_key, value] of Object.entries(envVars!)) { const match = value.match(varPattern); if (match) { extractedVars.push(match[1]); diff --git a/tools/claudeup-core/src/__tests__/integration/plugin-loading.test.ts b/tools/claudeup-core/src/__tests__/integration/plugin-loading.test.ts index b47f0be..9c56907 100644 --- a/tools/claudeup-core/src/__tests__/integration/plugin-loading.test.ts +++ b/tools/claudeup-core/src/__tests__/integration/plugin-loading.test.ts @@ -7,8 +7,8 @@ * - Error handling for invalid plugins */ -import { describe, it, expect, beforeEach, afterEach } from 'vitest'; -import { readdir, readFile } from 'node:fs/promises'; +import { describe, it, expect, afterEach } from 'vitest'; +import { readFile } from 'node:fs/promises'; import { join } from 'node:path'; import { existsSync } from 'node:fs'; import { diff --git a/tools/claudeup-core/src/__tests__/utils/fixture-loader.ts b/tools/claudeup-core/src/__tests__/utils/fixture-loader.ts index ea5ae6b..7ee0b89 100644 --- a/tools/claudeup-core/src/__tests__/utils/fixture-loader.ts +++ b/tools/claudeup-core/src/__tests__/utils/fixture-loader.ts @@ -7,7 +7,7 @@ import { join, dirname } from 'node:path'; import { fileURLToPath } from 'node:url'; -import { readFile, readdir, stat } from 'node:fs/promises'; +import { readFile, readdir } from 'node:fs/promises'; import { existsSync } from 'node:fs'; // ESM-compatible __dirname diff --git a/tools/claudeup-core/src/__tests__/utils/index.ts b/tools/claudeup-core/src/__tests__/utils/index.ts index 36962ff..99465cf 100644 --- a/tools/claudeup-core/src/__tests__/utils/index.ts +++ b/tools/claudeup-core/src/__tests__/utils/index.ts @@ -6,4 +6,14 @@ export * from './fixture-loader.js'; export * from './isolated-env.js'; -export * from './parsers.js'; +// Re-export parsers explicitly to avoid duplicate interface conflicts +// (HookEntry, HooksConfig, PluginManifest are defined in both fixture-loader and parsers) +export { + parseFrontmatter, + validatePluginManifest, + validateAgentFrontmatter, + validateCommandFrontmatter, + validateSkillFrontmatter, + validateHooksConfig, + validateMcpConfig, +} from './parsers.js';