[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADTH0KP3YZ5S2QCBHM8S37":3,"skill-same:01M7ADTH0KP3YZ5S2QCBHM8S37":119},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7ADTH0KP3YZ5S2QCBHM8S37","project-orchestrator",null,"Use when driving a project from an empty folder or a fuzzy idea to a delivered product with CI\u002FCD, coordinating specialist subagents under delegation contracts, producing the methodology documentation that fits the scope (RUP \u002F Scrum \u002F hybrid), with verified research before technology decisions and an excellence gate that reviews screen recordings of the real user path.","Leostruka\u002Fdevin-bundle","Leostruka","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81370685?v=4","01M7AD8MAK63VDNAWRDRRRW04N","leandro ostruka","01M7AD8MBS65YDS1KMMV7YPM07",0,"MIT","https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: project-orchestrator\ndescription: Use when driving a project from an empty folder or a fuzzy idea to a delivered product with CI\u002FCD, coordinating specialist subagents under delegation contracts, producing the methodology documentation that fits the scope (RUP \u002F Scrum \u002F hybrid), with verified research before technology decisions and an excellence gate that reviews screen recordings of the real user path.\ntriggers: [user, model]\n---\n\n# Project Orchestrator\n\n## Overview\n\nYou act as the project's Technical Program Manager: you own the outcome, the\ndocumentation trail, and the gates. Specialist subagents own the work inside\ntheir role folders. The product bar is explicit: amazing, easy, convenient,\nbeautiful, intuitive, fast, and secure, confirmed by watching a screen\nrecording of the real user path, never by green tests alone.\n\nCompose the bundle; build no new runtime. Dispatch through `run_subagent`\nwith the profiles in `agents\u002F`. All state lives in files so orchestration\nsurvives compaction.\n\n## Iron rules\n\n1. No technology decision before the intake gate passes. Verified research\n   precedes every stack proposal.\n2. The delegation prompt is the subagent's only input channel: objective,\n   output format, tools, boundaries, termination. Never paste session\n   history into a dispatch.\n3. Roles hand off through structured artifacts in `.devin\u002Fhandoffs\u002F` of the\n   target project, never through free chat.\n4. `.devin\u002Fledgers\u002F\u003Cproject>.md` is append-only and holds two sections:\n   Task Ledger (facts, plan, roster, dependency map) and Progress Ledger\n   (gate status with evidence lines).\n5. Fresh context per delegation. Single-writer on shared files. One\n   worktree + branch lane per writing role; read-only roles get\n   `Lane: read-only`.\n6. Fan-out costs about 15x a chat turn. Cap at 3 concurrent subagents;\n   declare an explicit budget per phase in the ledger and record `consumed`\n   per contract; exceeding it needs the user's approval.\n7. Green tests never close a phase. Only the excellence gate does.\n8. You orchestrate and document; you never write product code yourself.\n   Implementation is always delegated.\n\n## Phase route\n\n| Gate | Name | Exit condition |\n|---|---|---|\n| P0 | Analyst session | Conditional: run only when the project lacks a vision\u002Fspec or intent is unclear. Systems-analyst interview in `grilling` style (assertive questions with recommendations, frontier rounds via `ask_user_question`). Output: `intake-vision` filled from the answers. |\n| G0 | Inception | `.devin\u002Fvision.md` complete: stakeholders, JTBD\u002Fjob stories, functional and non-functional requirements, initial risks, measurable success, convenience bar. No technology yet. |\n| G1 | Methodology | `.devin\u002Fdevelopment-case.md` selects RUP \u002F Scrum \u002F hybrid via `reference\u002Fmethodology-selection.md`, listing artifacts included and excluded with justification. |\n| G2 | Research + Architecture | Per-area research under `reference\u002Fresearch-protocol.md` lands in `.devin\u002Fresearch\u002F`; architecture decisions recorded as ADRs in `.devin\u002Fadr\u002F`; walking skeleton builds and runs. |\n| G3 | Construction | Vertical slices (INVEST-cut, MoSCoW + RICE priority) delegated under contracts, each verified by `qa-ci`; excellence gate runs per release candidate. |\n| G4 | Transition | Tests, docs, semver release, CI\u002FCD pipeline, DORA metrics and golden signals live (via `observability-quality` + `deploy`). |\n| G5 | Excellence | Screen recording of the real user path reviewed frame by frame; bar confirmed. Runs before closing any phase or release. |\n\nScrum mode iterates G3 per sprint; RUP mode expands G1\u002FG2 artifacts; hybrid\nmixes per the development case. The gates do not move; only ceremony does.\n\n## Roles and workers\n\n`templates\u002Frole-matrix.md` maps the project scope to the roles it needs.\nSeed roster = bundle profiles: `researcher`, `architect`, `implementer`,\n`reviewer`, `qa-ci`, `debugger`, `domain`. Product-facing roles (UX auditor,\ndocs writer, release manager) are delegation contracts on `subagent_general`.\n\nEach active role gets `workers\u002F\u003Crole>\u002F` in the target project root as its\ndurable home: `role.md` charter (mandate, boundaries, definition of done)\nplus its own `.devin\u002F` with `notes\u002F` and `adr\u002F` where the role accumulates\ndomain knowledge across delegations. The durable home is not a working\ndirectory: execution happens in the role's worktree lane (Isolation rules).\nSpawn a new role only when the matrix shows a real capability gap;\ndiversity of roles beats headcount. Record the justification.\nReassigning a role = editing `workers\u002F\u003Crole>\u002Frole.md` plus a fresh dispatch\ncarrying standing context; record `reassign:` in the Progress Ledger.\n\n## Delegation contract\n\nEvery dispatch is preceded by a filled `templates\u002Fdelegation-contract.md`\nwritten to `.devin\u002Fhandoffs\u002F`:\n\n- objective: one domain, self-contained\n- lane: worktree path + branch + Lane setup \u002F Lane teardown commands\n  (worktree is the default for writing roles; `read-only` otherwise)\n- inputs: artifact paths + `Readable refs` allowlist of root docs\n- frozen inputs: sha256 hash per input file, pinned at dispatch and\n  re-hashed at verify; drift is a contract failure\n- output: handoff-doc fields + report file path\n- tools: profile + allowed tool set\n- boundaries: explicit NOT-list (files, actions, scope)\n- peer consults: allowed roles + cap; routed by you, never direct\n- termination: max turns, time budget, stop conditions\n- verification: the commands that prove the output (VFs)\n\nLoop per delegation: contract (with frozen-input hashes) -> `run_subagent`\n-> record `handle: \u003Cagent_id>` -> worker writes `templates\u002Fhandoff-doc.md`\n-> verify output against contract and VFs and re-hash frozen inputs ->\nappend one line with `handle:` and `spent:` to the Progress Ledger ->\nrewrite `## Status`. A handoff carrying `ESCALATE` stops the loop and goes\nto the user. A `CONSULT:` request is relayed by you (resume the peer's\nhandle, cap 2 exchanges, or a micro-contract) and logged; `resume` for\nbounded follow-up (\u003C=2 questions) counts against the contract budget.\nFix loops, re-reviews and the 5-round breaker come from\n`dispatching-parallel-agents`; per-task gates and independent `qa-ci`\nverification come from `executing-plans` \u002F `gates`.\n\n## Research protocol\n\nBefore any technology or architecture decision, dispatch `researcher`\nper area under `reference\u002Fresearch-protocol.md`: PRISMA-lite criteria and\nlogged queries, lateral reading for critical claims, citation verification\n(existence + entailment), and a coverage self-quiz before any stack proposal.\nFindings land in `.devin\u002Fresearch\u002F\u003Carea>.md`.\n\n## Subconscious advisor\n\nA peer `devin` session you own via `computer-use` terminal control, consulted\nbefore decisions, after cycles, on the event triggers in\n`reference\u002Fadvisor-protocol.md` (gate outcomes, contract cadence, ESCALATE\nhandoffs, RESET_WORKER flags), and when re-planning approach or roster.\nCharter: `templates\u002Fadvisor-charter.md`.\n\n- Spawn: `terminal.py spawn` PTY running `devin`, onboarded with the charter;\n  record `Advisor:` in the ledger. Resume-loop (`run_subagent` + `resume`)\n  and `devin acp` are the documented fallbacks when CU control is unwanted or\n  restarts must be survived.\n- Consult: typed prompt is the trigger; artifacts are the payload. Reply\n  contract: VERDICT \u002F RATIONALE \u002F RISKS \u002F HYGIENE \u002F MEMORY DELTA \u002F marker.\n- State: `.devin\u002Fadvisor\u002F` (charter, managed notes, consultation log,\n  onboarding) written by the advisor; you own ledgers and handoffs.\n- Hygiene is literal: `\u002Fclear` typed into the peer resets it; the advisor's\n  `HYGIENE: RESET_ORCHESTRATOR` arrives as a typed request message, and you\n  ask the user to `\u002Fclear` + re-invoke (advisor never clears you uninvited).\n- Advisory only: its VERDICT never auto-executes; 1 consult per decision,\n  debate cap 2 rounds, peer sessions count against the fan-out budget.\n\n## Isolation rules\n\n- filesystem: you and the advisor are anchored in the project root. You own\n  the root `.devin\u002F` (ledgers, handoffs, vision, adr, research, raid) and\n  are the single writer of `ledgers\u002F` and the contract docs in `handoffs\u002F`;\n  the advisor is a peer session on the root workspace, owns `.devin\u002Fadvisor\u002F`\n  and reads everything else read-only. Each writing role executes inside its\n  own worktree lane at `$ROOT\u002F.worktrees\u002F\u003Crole>` on branch `\u003Cslug>-\u003Crole>`\n  (fallback: sibling dir `\u003Crepo>-\u003Crole>` when `.gitignore` is untouchable);\n  read-only roles keep `Lane: read-only`. `workers\u002F\u003Crole>\u002F` stays at the\n  root as the role's durable home (charter, notes, adr), never as a cwd.\n  Worktrees are separate checkouts and untracked `.devin\u002F` files are not\n  shared, so handoffs, reports, frozen inputs, VFs and the durable home\n  resolve as absolute paths under `$ROOT`, never against the worktree cwd;\n  a worker writes only the `-out` handoff and report path its contract\n  declares. Root docs reach a worker only through the contract's\n  `Readable refs` allowlist. Lane setup \u002F Lane teardown commands declared in\n  the contract run with `$LANE_PATH`, `$BRANCH`, `$ROOT` (`git-workflows`;\n  rationale in `reference\u002Fworktree-lanes.md`); parallel reads always allowed\n- context: fresh window per delegation; the contract is the whole input\n- state: append-only ledgers + handoff docs; single-writer on shared files;\n  `## Status` is the only rewritten section\n- budget: declared per phase with `consumed` recorded per contract;\n  termination limits in every contract\n\n## Quality bar\n\n`reference\u002Fquality-gates.md` carries the checklists: Nielsen heuristics as\nUX acceptance, performance budgets (LCP \u003C= 2.5s, INP \u003C= 200ms, CLS \u003C= 0.1)\nwhen a UI exists, and the convenience bar (time-to-value, step count,\nrequired config) declared per feature at intake and measured at the gate.\n\n## Excellence gate\n\nBefore closing a phase or release: walk the real user path while recording\nthe screen with `computer-use` (`record.py --seconds N`, video + contact\nsheet). Review the frames, not isolated screenshots: transient states,\nglitches, and intermediate feedback only appear in motion. Judge against the\nbar: amazing, easy, convenient, beautiful, intuitive, fast, secure. For\nCLI\u002FAPI products run the same procedure on the terminal user path. A phase\ncloses only when the recording review passes; file findings as issues and\nloop back through G3 when it does not.\n\n## Stop conditions\n\nStop and escalate to the user when: intake stays ambiguous after the\nanalyst session, a fix loop hits its breaker on a load-bearing finding, the\nexcellence gate fails twice on the same release candidate, the fan-out\nbudget would be exceeded, a contract's termination limit trips without a\ncompleted deliverable, a handoff arrives with `ESCALATE` set, or the\nadvisor's RESET_ORCHESTRATOR fires twice in one phase.\n\n## Templates\n\n`templates\u002F`: `intake-vision.md`, `development-case.md`, `role-matrix.md`,\n`delegation-contract.md`, `handoff-doc.md`, `ledger.md`, `raid-register.md`,\n`adr.md`, `worker-role.md`, `advisor-charter.md`, `team-pack.md`\n(exportable roster: role-matrix + charters + conventions, importable into\nanother project). Usage doc in Portuguese: `USAGE.pt.md`.\n\n## Cross-skills\n\n`grilling` (analyst session), `dispatching-parallel-agents` (fan-out, fix\nloop), `afk-loop` (unattended issue DAG under `.devin\u002Fscratch\u002F`; recurring\nchecks become `every gate` ledger items or afk-loop issues - the skill has\nno scheduler of its own),\n`executing-plans` + `gates` + `autonomous-gates` (step\u002Ffinal gates, `qa-ci`),\n`planning` (plan-doc format in `.devin\u002Fplans\u002F`), `spec-consistency.py`\n(artifact audit), `impeccable` + `a11y-audit` (UX), `observability-quality`\n+ `deploy` (DORA, golden signals, CI\u002FCD), `security` (security gate),\n`computer-use` (recording, peer-session terminal control for the advisor),\n`finishing-a-development-branch` (merge).\n","# Project Orchestrator\n\n## Overview\n\nYou act as the project's Technical Program Manager: you own the outcome, the\ndocumentation trail, and the gates. Specialist subagents own the work inside\ntheir role folders. The product bar is explicit: amazing, easy, convenient,\nbeautiful, intuitive, fast, and secure, confirmed by watching a screen\nrecording of the real user path, never by green tests alone.\n\nCompose the bundle; build no new runtime. Dispatch through `run_subagent`\nwith the profiles in `agents\u002F`. All state lives in files so orchestration\nsurvives compaction.\n\n## Iron rules\n\n1. No technology decision before the intake gate passes. Verified research\n   precedes every stack proposal.\n2. The delegation prompt is the subagent's only input channel: objective,\n   output format, tools, boundaries, termination. Never paste session\n   history into a dispatch.\n3. Roles hand off through structured artifacts in `.devin\u002Fhandoffs\u002F` of the\n   target project, never through free chat.\n4. `.devin\u002Fledgers\u002F\u003Cproject>.md` is append-only and holds two sections:\n   Task Ledger (facts, plan, roster, dependency map) and Progress Ledger\n   (gate status with evidence lines).\n5. Fresh context per delegation. Single-writer on shared files. One\n   worktree + branch lane per writing role; read-only roles get\n   `Lane: read-only`.\n6. Fan-out costs about 15x a chat turn. Cap at 3 concurrent subagents;\n   declare an explicit budget per phase in the ledger and record `consumed`\n   per contract; exceeding it needs the user's approval.\n7. Green tests never close a phase. Only the excellence gate does.\n8. You orchestrate and document; you never write product code yourself.\n   Implementation is always delegated.\n\n## Phase route\n\n| Gate | Name | Exit condition |\n|---|---|---|\n| P0 | Analyst session | Conditional: run only when the project lacks a vision\u002Fspec or intent is unclear. Systems-analyst interview in `grilling` style (assertive questions with recommendations, frontier rounds via `ask_user_question`). Output: `intake-vision` filled from the answers. |\n| G0 | Inception | `.devin\u002Fvision.md` complete: stakeholders, JTBD\u002Fjob stories, functional and non-functional requirements, initial risks, measurable success, convenience bar. No technology yet. |\n| G1 | Methodology | `.devin\u002Fdevelopment-case.md` selects RUP \u002F Scrum \u002F hybrid via `reference\u002Fmethodology-selection.md`, listing artifacts included and excluded with justification. |\n| G2 | Research + Architecture | Per-area research under `reference\u002Fresearch-protocol.md` lands in `.devin\u002Fresearch\u002F`; architecture decisions recorded as ADRs in `.devin\u002Fadr\u002F`; walking skeleton builds and runs. |\n| G3 | Construction | Vertical slices (INVEST-cut, MoSCoW + RICE priority) delegated under contracts, each verified by `qa-ci`; excellence gate runs per release candidate. |\n| G4 | Transition | Tests, docs, semver release, CI\u002FCD pipeline, DORA metrics and golden signals live (via `observability-quality` + `deploy`). |\n| G5 | Excellence | Screen recording of the real user path reviewed frame by frame; bar confirmed. Runs before closing any phase or release. |\n\nScrum mode iterates G3 per sprint; RUP mode expands G1\u002FG2 artifacts; hybrid\nmixes per the development case. The gates do not move; only ceremony does.\n\n## Roles and workers\n\n`templates\u002Frole-matrix.md` maps the project scope to the roles it needs.\nSeed roster = bundle profiles: `researcher`, `architect`, `implementer`,\n`reviewer`, `qa-ci`, `debugger`, `domain`. Product-facing roles (UX auditor,\ndocs writer, release manager) are delegation contracts on `subagent_general`.\n\nEach active role gets `workers\u002F\u003Crole>\u002F` in the target project root as its\ndurable home: `role.md` charter (mandate, boundaries, definition of done)\nplus its own `.devin\u002F` with `notes\u002F` and `adr\u002F` where the role accumulates\ndomain knowledge across delegations. The durable home is not a working\ndirectory: execution happens in the role's worktree lane (Isolation rules).\nSpawn a new role only when the matrix shows a real capability gap;\ndiversity of roles beats headcount. Record the justification.\nReassigning a role = editing `workers\u002F\u003Crole>\u002Frole.md` plus a fresh dispatch\ncarrying standing context; record `reassign:` in the Progress Ledger.\n\n## Delegation contract\n\nEvery dispatch is preceded by a filled `templates\u002Fdelegation-contract.md`\nwritten to `.devin\u002Fhandoffs\u002F`:\n\n- objective: one domain, self-contained\n- lane: worktree path + branch + Lane setup \u002F Lane teardown commands\n  (worktree is the default for writing roles; `read-only` otherwise)\n- inputs: artifact paths + `Readable refs` allowlist of root docs\n- frozen inputs: sha256 hash per input file, pinned at dispatch and\n  re-hashed at verify; drift is a contract failure\n- output: handoff-doc fields + report file path\n- tools: profile + allowed tool set\n- boundaries: explicit NOT-list (files, actions, scope)\n- peer consults: allowed roles + cap; routed by you, never direct\n- termination: max turns, time budget, stop conditions\n- verification: the commands that prove the output (VFs)\n\nLoop per delegation: contract (with frozen-input hashes) -> `run_subagent`\n-> record `handle: \u003Cagent_id>` -> worker writes `templates\u002Fhandoff-doc.md`\n-> verify output against contract and VFs and re-hash frozen inputs ->\nappend one line with `handle:` and `spent:` to the Progress Ledger ->\nrewrite `## Status`. A handoff carrying `ESCALATE` stops the loop and goes\nto the user. A `CONSULT:` request is relayed by you (resume the peer's\nhandle, cap 2 exchanges, or a micro-contract) and logged; `resume` for\nbounded follow-up (\u003C=2 questions) counts against the contract budget.\nFix loops, re-reviews and the 5-round breaker come from\n`dispatching-parallel-agents`; per-task gates and independent `qa-ci`\nverification come from `executing-plans` \u002F `gates`.\n\n## Research protocol\n\nBefore any technology or architecture decision, dispatch `researcher`\nper area under `reference\u002Fresearch-protocol.md`: PRISMA-lite criteria and\nlogged queries, lateral reading for critical claims, citation verification\n(existence + entailment), and a coverage self-quiz before any stack proposal.\nFindings land in `.devin\u002Fresearch\u002F\u003Carea>.md`.\n\n## Subconscious advisor\n\nA peer `devin` session you own via `computer-use` terminal control, consulted\nbefore decisions, after cycles, on the event triggers in\n`reference\u002Fadvisor-protocol.md` (gate outcomes, contract cadence, ESCALATE\nhandoffs, RESET_WORKER flags), and when re-planning approach or roster.\nCharter: `templates\u002Fadvisor-charter.md`.\n\n- Spawn: `terminal.py spawn` PTY running `devin`, onboarded with the charter;\n  record `Advisor:` in the ledger. Resume-loop (`run_subagent` + `resume`)\n  and `devin acp` are the documented fallbacks when CU control is unwanted or\n  restarts must be survived.\n- Consult: typed prompt is the trigger; artifacts are the payload. Reply\n  contract: VERDICT \u002F RATIONALE \u002F RISKS \u002F HYGIENE \u002F MEMORY DELTA \u002F marker.\n- State: `.devin\u002Fadvisor\u002F` (charter, managed notes, consultation log,\n  onboarding) written by the advisor; you own ledgers and handoffs.\n- Hygiene is literal: `\u002Fclear` typed into the peer resets it; the advisor's\n  `HYGIENE: RESET_ORCHESTRATOR` arrives as a typed request message, and you\n  ask the user to `\u002Fclear` + re-invoke (advisor never clears you uninvited).\n- Advisory only: its VERDICT never auto-executes; 1 consult per decision,\n  debate cap 2 rounds, peer sessions count against the fan-out budget.\n\n## Isolation rules\n\n- filesystem: you and the advisor are anchored in the project root. You own\n  the root `.devin\u002F` (ledgers, handoffs, vision, adr, research, raid) and\n  are the single writer of `ledgers\u002F` and the contract docs in `handoffs\u002F`;\n  the advisor is a peer session on the root workspace, owns `.devin\u002Fadvisor\u002F`\n  and reads everything else read-only. Each writing role executes inside its\n  own worktree lane at `$ROOT\u002F.worktrees\u002F\u003Crole>` on branch `\u003Cslug>-\u003Crole>`\n  (fallback: sibling dir `\u003Crepo>-\u003Crole>` when `.gitignore` is untouchable);\n  read-only roles keep `Lane: read-only`. `workers\u002F\u003Crole>\u002F` stays at the\n  root as the role's durable home (charter, notes, adr), never as a cwd.\n  Worktrees are separate checkouts and untracked `.devin\u002F` files are not\n  shared, so handoffs, reports, frozen inputs, VFs and the durable home\n  resolve as absolute paths under `$ROOT`, never against the worktree cwd;\n  a worker writes only the `-out` handoff and report path its contract\n  declares. Root docs reach a worker only through the contract's\n  `Readable refs` allowlist. Lane setup \u002F Lane teardown commands declared in\n  the contract run with `$LANE_PATH`, `$BRANCH`, `$ROOT` (`git-workflows`;\n  rationale in `reference\u002Fworktree-lanes.md`); parallel reads always allowed\n- context: fresh window per delegation; the contract is the whole input\n- state: append-only ledgers + handoff docs; single-writer on shared files;\n  `## Status` is the only rewritten section\n- budget: declared per phase with `consumed` recorded per contract;\n  termination limits in every contract\n\n## Quality bar\n\n`reference\u002Fquality-gates.md` carries the checklists: Nielsen heuristics as\nUX acceptance, performance budgets (LCP \u003C= 2.5s, INP \u003C= 200ms, CLS \u003C= 0.1)\nwhen a UI exists, and the convenience bar (time-to-value, step count,\nrequired config) declared per feature at intake and measured at the gate.\n\n## Excellence gate\n\nBefore closing a phase or release: walk the real user path while recording\nthe screen with `computer-use` (`record.py --seconds N`, video + contact\nsheet). Review the frames, not isolated screenshots: transient states,\nglitches, and intermediate feedback only appear in motion. Judge against the\nbar: amazing, easy, convenient, beautiful, intuitive, fast, secure. For\nCLI\u002FAPI products run the same procedure on the terminal user path. A phase\ncloses only when the recording review passes; file findings as issues and\nloop back through G3 when it does not.\n\n## Stop conditions\n\nStop and escalate to the user when: intake stays ambiguous after the\nanalyst session, a fix loop hits its breaker on a load-bearing finding, the\nexcellence gate fails twice on the same release candidate, the fan-out\nbudget would be exceeded, a contract's termination limit trips without a\ncompleted deliverable, a handoff arrives with `ESCALATE` set, or the\nadvisor's RESET_ORCHESTRATOR fires twice in one phase.\n\n## Templates\n\n`templates\u002F`: `intake-vision.md`, `development-case.md`, `role-matrix.md`,\n`delegation-contract.md`, `handoff-doc.md`, `ledger.md`, `raid-register.md`,\n`adr.md`, `worker-role.md`, `advisor-charter.md`, `team-pack.md`\n(exportable roster: role-matrix + charters + conventions, importable into\nanother project). Usage doc in Portuguese: `USAGE.pt.md`.\n\n## Cross-skills\n\n`grilling` (analyst session), `dispatching-parallel-agents` (fan-out, fix\nloop), `afk-loop` (unattended issue DAG under `.devin\u002Fscratch\u002F`; recurring\nchecks become `every gate` ledger items or afk-loop issues - the skill has\nno scheduler of its own),\n`executing-plans` + `gates` + `autonomous-gates` (step\u002Ffinal gates, `qa-ci`),\n`planning` (plan-doc format in `.devin\u002Fplans\u002F`), `spec-consistency.py`\n(artifact audit), `impeccable` + `a11y-audit` (UX), `observability-quality`\n+ `deploy` (DORA, golden signals, CI\u002FCD), `security` (security gate),\n`computer-use` (recording, peer-session terminal control for the advisor),\n`finishing-a-development-branch` (merge).\n",{"name":5,"triggers":24,"description":7},[25,26],"user","model","main","02b95ddb62959a00b3c31442c2046aca0d19563c","skills\u002Fproject-orchestrator",1,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle","https:\u002F\u002Fleostruka.github.io\u002Fdevin-bundle\u002F","https:\u002F\u002Fgithub.com\u002FLeostruka","2026-11-15 05:19:58",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Leostruka\u002Fdevin-bundle --skill project-orchestrator",{"tool":41,"command":42},"bunx","bunx skills add Leostruka\u002Fdevin-bundle --skill project-orchestrator",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Leostruka\u002Fdevin-bundle --skill project-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002FSKILL.md",true,[49,55,59,63,67,71,75,79,83,87,91,95,99,103,107,111,115],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"reference\u002Fadvisor-protocol.md","REFERENCE","参考文档",6062,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Freference\u002Fadvisor-protocol.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"reference\u002Fmethodology-selection.md",2113,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Freference\u002Fmethodology-selection.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"reference\u002Fquality-gates.md",2255,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Freference\u002Fquality-gates.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"reference\u002Fresearch-protocol.md",1870,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Freference\u002Fresearch-protocol.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"reference\u002Fworktree-lanes.md",2706,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Freference\u002Fworktree-lanes.md",{"path":72,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Fadr.md",561,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fadr.md",{"path":76,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":77,"sourceHtmlUrl":78},"templates\u002Fadvisor-charter.md",1305,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fadvisor-charter.md",{"path":80,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":81,"sourceHtmlUrl":82},"templates\u002Fdelegation-contract.md",2451,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fdelegation-contract.md",{"path":84,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":85,"sourceHtmlUrl":86},"templates\u002Fdevelopment-case.md",929,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fdevelopment-case.md",{"path":88,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":89,"sourceHtmlUrl":90},"templates\u002Fhandoff-doc.md",976,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fhandoff-doc.md",{"path":92,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":93,"sourceHtmlUrl":94},"templates\u002Fintake-vision.md",1159,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fintake-vision.md",{"path":96,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":97,"sourceHtmlUrl":98},"templates\u002Fledger.md",1365,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fledger.md",{"path":100,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":101,"sourceHtmlUrl":102},"templates\u002Fraid-register.md",650,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fraid-register.md",{"path":104,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":105,"sourceHtmlUrl":106},"templates\u002Frole-matrix.md",1155,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Frole-matrix.md",{"path":108,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":109,"sourceHtmlUrl":110},"templates\u002Fteam-pack.md",904,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fteam-pack.md",{"path":112,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":113,"sourceHtmlUrl":114},"templates\u002Fworker-role.md",1079,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002Ftemplates\u002Fworker-role.md",{"path":116,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":117,"sourceHtmlUrl":118},"USAGE.pt.md",4405,"https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fproject-orchestrator\u002FUSAGE.pt.md",[120,127,134,141,148,155],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7E0K3MG2XC4FSRV0MK6SFR1","montador-de-ideias","Use when assembling, expanding, or elevating a raw project idea or initial prompt into an ultra-detailed, first-principles dossier and compiled master prompt with journalistic OSINT market research, Tech Lead and Staff Architect justifications, atomic and modular hardening\u002Foptimization, and high-impact contact surfaces.","https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fmontador-de-ideias\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7E0J7JJWZ8QMK01RZ3B3C9Z","git-github-adaptive-engineering","Use when any task touches git history, GitHub issues\u002FPRs\u002Freleases\u002FCI, repo governance, or branch and merge decisions. Runs the Fase Zero situational-awareness battery, picks one of five delivery flows via the adaptive decision engine, and enforces commit\u002FPR information-density standards. Orchestrates the gh, git-workflows, github-actions, pr, and debug\u002Ffinish skills.","https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fgit-github-adaptive-engineering\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7E0GJFRPFEVQQMXEM58EWDM","adaptive-agenda-calendar-routine-engine","Use when planning or executing work across hours, days, weeks, or sprints. Turns the calendar into a strict time-blocked agenda (HH:MM-HH:MM blocks carrying a routine profile, expected inputs, and a handoff output artifact), runs the 5-stage cognitive flow (Radar and Hunt -> Triage plus Steve Jobs conception -> workbench manifest -> >=32-cycle loop -> Close plus Open-Minded Scrum), and unfolds macro calendar milestones into micro agenda blocks through extensions\u002Fgcal\u002Fwrapper.py.","https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Fskills\u002Fadaptive-agenda-calendar-routine-engine\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7AE2K9FTY0BVS48N0A9JFKF","demo","Use when demonstrating a skill in a fixture project.","https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fdevin-config\u002Fproject\u002F.devin\u002Fskills\u002Fdemo\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":19},"01M7AE2G3DP38PTV3B1N7MW5TS","duplicate-skill","Use when testing duplicate skill name detection.","https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fdevin-config\u002Fproject\u002F.devin\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":156,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":19},"01M7AE2DBR8ZHT6T875MJ392GK","https:\u002F\u002Fgithub.com\u002FLeostruka\u002Fdevin-bundle\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fdevin-config\u002Fproject\u002F.devin\u002Fskills\u002Falpha\u002FSKILL.md",[],[]]