rePACT

Run a recursive PACT cycle for this sub-task: $ARGUMENTS

This command initiates a nested P→A→C→T cycle for a sub-task that is too complex for simple delegation but should remain part of the current feature work.

Team behavior: rePACT spawns sub-scope teammates into the session team ({team_name}). The platform provisions the team; rePACT does not create a new one. Use scope-prefixed names (e.g., backend-coder-auth-scope) to distinguish sub-scope teammates from parent-scope teammates.

---

Task Hierarchy

Create a nested Task hierarchy as a child of the current context:

1. `TaskCreate`: Sub-feature task "{verb} {sub-feature}" (child of parent context) — stamp metadata.variety.total (4-16)
2. `TaskCreate`: Nested phase tasks:
   - "PREPARE: {sub-feature-slug}"
   - "ARCHITECT: {sub-feature-slug}"
   - "CODE: {sub-feature-slug}"
   - "TEST: {sub-feature-slug}"
3. `TaskUpdate`: Set dependencies:
   - Phase-to-phase blockedBy chain (same as orchestrate)
   - Parent task addBlockedBy = [sub-feature task]
4. `TaskUpdate`: Sub-feature task status = "in_progress"
5. Execute nested P→A→C→T cycle (same per-phase lifecycle as orchestrate: create phase task → `in_progress` → dispatch agents → agent tasks `in_progress` → `completed` → phase `completed`)
6. On completion: Parent task unblocked

Example structure (standard):

[Feature] "Implement user auth" (parent, blockedBy: sub-feature)
└── [Sub-Feature] "Implement OAuth2 token refresh"
    ├── [Phase] "PREPARE: oauth2-token-refresh"
    ├── [Phase] "ARCHITECT: oauth2-token-refresh"
    ├── [Phase] "CODE: oauth2-token-refresh"
    └── [Phase] "TEST: oauth2-token-refresh"

Scope-aware naming (when scope contract is provided):

When a scope contract provides a scope_id, prefix all tasks with [scope:{scope_id}]:

[Feature] "Implement user auth" (parent, blockedBy: sub-feature)
└── [Sub-Feature] "[scope:backend-api] Implement backend API"
    ├── [Phase] "[scope:backend-api] PREPARE: backend-api"
    ├── [Phase] "[scope:backend-api] ARCHITECT: backend-api"
    ├── [Phase] "[scope:backend-api] CODE: backend-api"
    └── [Phase] "[scope:backend-api] TEST: backend-api"

Include scope_id in task metadata: { "scope_id": "backend-api" }. This enables the parent orchestrator to filter tasks by scope when aggregating results.

---