feat(assistant): add dev-orchestrator skill for parallel task management#31
Open
Menendez2004 wants to merge 7 commits into
Open
feat(assistant): add dev-orchestrator skill for parallel task management#31Menendez2004 wants to merge 7 commits into
Menendez2004 wants to merge 7 commits into
Conversation
Introduces the dev-orchestrator skill, designed to detect and manage multiple independent development tasks concurrently. This skill allows for efficient orchestration of tasks, enhancing workflow by dispatching sub-agents for parallel execution.
…esolution Expanded the dev-orchestrator skill to include an opt-in '--worktree' execution mode, allowing for isolated git worktree management and sequential task execution. The skill now also resolves issue-tracker tickets (Linear, Jira, GitHub Issues, Notion) referenced in prompts, enhancing its ability to manage multi-task development workflows. Updated the skill's description and version to reflect these changes.
Deleted obsolete files related to the dev-orchestrator skill, including SKILL.md, ticket-resolution.md, workflow.md, worktree-mode.md, and associated scripts. This cleanup streamlines the codebase and removes outdated documentation and functionality that are no longer in use.
…lated agent functionality Enhanced the dev-orchestrator skill by updating its description to clarify the isolated agent functionality, which allows for parallel execution of independent tasks with scoped tool lists. The version has been incremented to 4 to reflect these changes. Additionally, new references and scripts related to worktree management and ticket resolution have been introduced to improve the orchestration workflow.
…aintain consistency
… clause Updated the SKILL.md to include a new test-plan obligation clause, ensuring that every dispatch prompt for code-touching tasks includes specific instructions for updating the QA test plan. Introduced a new reference file for the test-plan obligation clause and improved the clarity of task orchestration instructions. Additionally, refined the worktree management process to ensure integration worktrees are utilized effectively during merges.
…cripts Updated the `setup-integration-branch.sh` and `setup-worktree.sh` scripts to enhance the readability of local reference checks for the 'main' and 'master' branches. The previous inline conditional assignments have been replaced with explicit if statements for better clarity and maintainability.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adds the
dev-orchestratorskill: detects when a single prompt bundles multiple independent dev tasks and dispatches each as an isolated agent, classifying dependencies so independent tasks fan out in parallel and dependent ones run in order. Includes an opt-in worktree mode that provisions an integration branch off the protected base, runs each task in its own git worktree, validates the combined result, and hands off toagent-pr-creatorfor the protected-base PR. Also resolves issue-tracker tickets (Linear, Jira, GitHub Issues, Notion) via MCP.Type of Change
Workflow schemas
End-to-end orchestration flow
flowchart TD A(["Start<br/>user prompt"]) --> B{"Phase 0?<br/>ticket ref or --ticket"} B -->|yes| B1["MCP resolve<br/>prepend envelope"] B -->|no| C B1 --> C["Phase 1<br/>detect · classify · route"] C --> D{"One task<br/>after merge?"} D -->|yes| E["Main session<br/>skip 2–4"] D -->|2+ tasks| F["Phase 2<br/>Layout A/B/C confirm"] F --> G{"User<br/>confirmed?"} G -->|edit plan| F G -->|go-ahead| H["Phase 3<br/>dispatch agents (M1·M2·M3)"] H --> I["Phase 4<br/>Orchestrator Results"] I --> J{"Mode 3 +<br/>merge PR path?"} J -->|yes| K["Phase 4.5<br/>validate · push · PR"] J -->|no| L{"QA gate"} K --> L L -->|all failed| M["Retry — no QA"] L -->|doc-only| N["Skip QA<br/>no testable artifacts"] L -->|code-touching ok| Q["Phase 5<br/>qa-orchestrator"] Q --> R["Verdict + issue URLs"]Phase 1 — pairwise dependency classification
flowchart TD P(["Tasks A and B"]) --> Q{"B breaks<br/>without A?"} Q -->|yes| R["Hard-chained<br/>→ merge into one task"] Q -->|no| S{"Better if<br/>A runs before B?"} S -->|yes| T["Soft-sequenced<br/>→ waves"] S -->|no| U["Independent<br/>→ single parallel wave"]Worktree mode — merge & PR handoff (Mode 3)
flowchart TD A["setup-integration-branch.sh<br/>integration branch off protected base"] --> B["setup-worktree.sh<br/>one worktree per task"] B --> C["dispatch isolated agent per worktree"] C --> D["verify commit<br/>SHA + diff"] D --> E["merge-worktree.sh --no-push<br/>merge in DEDICATED integration worktree"] E --> F{"merge clean?"} F -->|conflict| G["contained in integration worktree<br/>primary checkout untouched"] F -->|clean| H{"more waves?"} H -->|yes| B H -->|no| I["Phase 4.5<br/>validate $INTEGRATION_WORKTREE"] I --> J["push integration branch"] J --> K["agent-pr-creator<br/>PR: integration → base"]What's included
dispatch-contract.md,worktree-mode.md,ticket-resolution.md,workflow.md,test-plan-obligation.md,dispatch-patterns.md.setup-integration-branch.sh,setup-worktree.sh,merge-worktree.sh,validate-worktree.sh.marketplace.json+ generated.claude-plugin/artifacts.Fixes in this revision (merge/worktree safety)
The previous CI failure (shellcheck SC2015) is resolved, along with several correctness issues found while reviewing the merge and worktree-creation paths:
A && B || trueidiom insetup-integration-branch.shandsetup-worktree.shwith explicitif ensure_local_ref …; then …; fiblocks.merge-worktree.shnow merges inside a dedicated integration worktree instead of checking the base branch out in the primary worktree. A clean merge leaves the user's HEAD untouched; a conflict is contained in that worktree (not stranded in the user's checkout). The script emitsINTEGRATION_WORKTREE=<path>for downstream validate/push.--no-editso--no-ffcannot hang on the commit-message editor.merge-base --is-ancestorcheck against the base — no blindbranch -Dthat could drop unmerged work.setup-worktree.shaddspid+RANDOMentropy to branch names and worktree paths so same-second, same-slug dispatches in a wave no longer collide.validate-worktree.shsetsCI=truefornpm testso watch-mode runners (vitest/CRA) run once and exit.worktree-mode.mdPhase 4.5 now validates/pushes/PR-creates against$INTEGRATION_WORKTREE.Verification
bash -nclean on all four scripts.ruby scripts/skills_audit.rb→ PASS (43/43 skills)..claude-plugin/artifacts regenerated and identical to source.Breaking Changes
Screenshots / Videos
N/A — no UI changes.