feat: reimplement PACT-Task system integration (orchestrator-only) #121
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tration (#118)" This reverts commit 21bca1c (PR #118), giving us a clean baseline for reimplementation with the orchestrator-only architecture. The original integration assumed sub-agents could call Task tools (TaskCreate, TaskUpdate, etc.), but empirical testing revealed this is a Claude Code platform limitation — only the parent orchestrator process has access to these tools. Reimplementation follows the revised plan at docs/plans/2026-01-28-task-system-revised-design.md
Create pact-task-tracking SKILL.md as the agent reporting protocol (HANDOFF format, BLOCKER/ALGEDONIC text-based reporting) and add Task Lifecycle Management section to CLAUDE.md defining the orchestrator-only dispatch lifecycle. Critical constraint: sub-agents do NOT have Task tools — only the orchestrator owns TaskCreate/TaskUpdate/TaskGet/TaskList. Agents communicate status via structured text.
Update orchestrate.md, comPACT.md, and imPACT.md with Task hierarchy creation, signal monitoring, and agent blocker/algedonic prompt language. Orchestrator creates all Tasks, agents report via text.
Update plan-mode.md, rePACT.md, peer-review.md, and wrap-up.md with Task hierarchy, signal monitoring, agent prompt language, and TaskList audit logic.
Create pact-task-hierarchy.md with orchestrator-only Task ownership model. Update pact-protocols.md with Task Hierarchy section and Task-Based Coordination in S2. Update algedonic.md flow to show text-based agent reporting. All 11 protocol extracts verified.
Collaborator
Author
|
Superseded by PR #122 (v3 fix-in-place approach). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
Phase 0: Revert — Clean slate by reverting PR #118 merge commit
Phase 1: Foundation —
pact-task-trackingSKILL.md (agent reporting protocol) + Task Lifecycle Management in CLAUDE.mdPhase 2: Core Workflows — Task hierarchy, signal monitoring, and agent prompt language in orchestrate.md, comPACT.md, imPACT.md
Phase 3: Supporting Workflows — Same additions in plan-mode.md, rePACT.md, peer-review.md, wrap-up.md
Phase 4: Protocols — pact-task-hierarchy.md (new), pact-protocols.md, pact-s2-coordination.md, algedonic.md updated; 11/11 protocol extracts verified
Key Architectural Decision
Sub-agents spawned via Claude Code's
Tasktool do NOT have access to Task tools. This was discovered empirically during PR #120. The revised architecture makes the orchestrator the single authority for all Task state management.Test plan
/PACT:orchestrateon a test task and verify Task hierarchy creation