{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "uzairansaruzi-p3-stack--fan-out-work-to-worktree-workers",
 "repo": "uzairansaruzi/p3-stack",
 "repo_url": "https://github.com/uzairansaruzi/p3-stack",
 "repo_slug": "uzairansaruzi-p3-stack",
 "title": "Split a feature across child agents in separate worktrees",
 "page_title": "How to split a feature across child agents in separate worktrees with P3 Stack",
 "summary": "Delegate parallel pieces to child agents, each bound to its own worktree and branch.",
 "who": "A developer with a feature large enough to split into independent parts that can be built at the same time.",
 "problem": "Parallel agents editing one checkout collide, and advice alone does not stop two writers from touching the same files.",
 "outcome": "Each piece lands on its own branch in its own worktree, with one writer per worktree enforced by the app.",
 "steps": [
  "Install the skills with `./install.sh` from the P3 Stack clone, as described in the README.",
  "Run `/p3-mode` and choose the orchestrate or multi-phase plan playbook for the feature.",
  "Let the orchestrator call `t3_thread_launch` to start one worker per part, each in its own worktree and branch.",
  "Let the orchestrator call `delegate_task` for review panels and sub-work, using the per-role models from p3-models.md.",
  "Review each branch and merge the parts you accept."
 ],
 "agent_prompt": "In the repo at <repo-path>, use p3-stack's orchestrate playbook to split <feature description> into independent parts, one worktree per part via t3_thread_launch. Expected output: one branch per part and a short summary per branch. Verify that no two workers share a worktree.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README does not describe how work is merged back, so merging and conflict handling are left to you.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "shell",
 "requirements": [
  "T3 Code installed, since install.sh links skills for it to read",
  "git and a shell to run install.sh",
  "At least one model provider available through T3 Code's orchestrator_capabilities",
  "A git repository to work on"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/uzairansaruzi-p3-stack/fan-out-work-to-worktree-workers/",
 "md": "https://dedupedai.com/use-cases/uzairansaruzi-p3-stack/fan-out-work-to-worktree-workers/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/uzairansaruzi-p3-stack--fan-out-work-to-worktree-workers.json",
 "api_version": "v1"
}