Skip to content

feat: integrate native task system for real-time orchestration#186

Merged
cahaseler merged 2 commits intomainfrom
feature/native-task-orchestration
Jan 23, 2026
Merged

feat: integrate native task system for real-time orchestration#186
cahaseler merged 2 commits intomainfrom
feature/native-task-orchestration

Conversation

@cahaseler
Copy link
Owner

Summary

  • Add guidance for using Claude Code's native task tools (TaskCreate, TaskUpdate, TaskList) during phase-based orchestration
  • Two-layer approach: native tasks for session coordination, markdown for persistence
  • Leverages new blockedBy dependency tracking (Claude Code v2.1.16)

Changes

  • commands/tasks.md - New "Real-Time Task Coordination" section with TaskUpdate calls
  • templates/tasks-template.md - Setup instructions and updated execution patterns

How it works

  1. At phase set start: Create native tasks with blockedBy dependencies
  2. During execution: TaskUpdate status as subagents dispatch/complete
  3. Use TaskList: See what's unblocked and ready to dispatch
  4. At checkpoints: Sync completed tasks back to markdown checkboxes

Benefits

  • Native blockedBy enforces TDD order automatically
  • TaskList shows exactly what's ready vs. blocked
  • Status visible in Claude Code's UI
  • Markdown update at checkpoints preserves state across sessions

Test plan

  • Verify documentation is clear and actionable
  • Test with actual phase-based task execution

🤖 Generated with Claude Code

Add guidance for using Claude Code's native task tools (TaskCreate,
TaskUpdate, TaskList) during phase execution:

- Native tasks = session coordination layer (real-time tracking)
- Markdown tasks.md = persistent record (survives compactions)

Key changes to commands/tasks.md:
- New "Real-Time Task Coordination" section explaining two-layer approach
- TaskUpdate calls in sequential phase execution flow
- TaskList usage for parallel phase dependency tracking

Key changes to templates/tasks-template.md:
- "Real-Time Coordination" section in Orchestration Model
- Setup instructions for creating tasks with blockedBy dependencies
- Updated sequential/parallel execution to use native task status
- Checkpoint sync instructions for markdown persistence

The blockedBy feature automatically enforces TDD order (can't start
Tests until Stub completes) and surfaces ready-to-dispatch work via
TaskList.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 90f20ddc2a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

→ On success: `TaskUpdate: "Phase N: Validate" status: completed`

**IMPORTANT**: Update tasks.md checkboxes immediately after each subagent returns successfully. This keeps progress visible and ensures state is preserved across context compactions.
**At phase completion**: Update tasks.md checkboxes to sync the persistent record. This ensures state is preserved across context compactions.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Syncing only at phase completion can lose progress

If a context compaction or session interruption happens mid‑phase, native Task* state is lost and the markdown file is the only persistent record. This instruction delays updating tasks.md until the end of the phase set, so any completed Stub/Tests/Implement steps since the last checkpoint are dropped, leading to re‑running work or misordered dependencies on resume. To preserve progress across compactions, the markdown sync needs to happen after each task completion (or at least after each step), not only at phase completion.

Useful? React with 👍 / 👎.

- Use consistent short format "PN: Step" (e.g., "P1: Stub") for task names
- Clarify markdown sync happens after each phase, not just at checkpoints
- Replace "..." with explicit comment "(repeat pattern for each phase)"

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cahaseler cahaseler merged commit d64eee1 into main Jan 23, 2026
4 checks passed
@cahaseler cahaseler deleted the feature/native-task-orchestration branch January 23, 2026 02:55
github-actions bot pushed a commit that referenced this pull request Jan 23, 2026
# [4.1.0](v4.0.1...v4.1.0) (2026-01-23)

### Features

* integrate native task system for real-time orchestration ([#186](#186)) ([d64eee1](d64eee1))
@github-actions
Copy link

🎉 This PR is included in version 4.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant