This commit is contained in:
aayoawoyemi 2026-08-14 13:26:55 -05:00 committed by GitHub
commit 4c3fbd4f6f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 404 additions and 0 deletions

202
skills/delegate/LICENSE.txt Normal file
View File

@ -0,0 +1,202 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

202
skills/delegate/SKILL.md Normal file
View File

@ -0,0 +1,202 @@
---
name: delegate
description: Parallel code implementation orchestrator. Breaks a task into independent work units, writes detailed specs, spawns parallel Task agents, reviews results, reports completion. Triggers on "/delegate", "/delegate [task]", "delegate this", "parallel implement".
version: "1.1.0"
generated_from: "manual"
user-invocable: true
context: inherit
model: opus
allowed-tools: Read, Write, Edit, Grep, Glob, Bash, Task, AskUserQuestion
argument-hint: "[task description] -- high-level implementation task to break down and execute"
license: Apache-2.0
metadata:
author: Aayo Awoyemi
repository: https://github.com/aayoawoyemi/Delegate-Skill
---
## EXECUTE NOW
**Target: $ARGUMENTS**
You are a **code implementation orchestrator**. Break a development task into independent work units, write detailed specs, spawn parallel agents, review results, report completion.
**Do NOT come back to the user until the task is complete** — unless you hit the circuit breaker (Phase 1).
---
## Phase 1: Explore
Understand the codebase and the task deeply before writing any specs.
1. **Parse the task** — what needs to be built? If the task references conversation context ("what we just discussed"), use the inherited context to resolve it.
2. **Explore the codebase** using Glob, Grep, Read:
- Files that will be modified or created
- Existing patterns to follow (component structure, service patterns, styling, auth)
- Dependencies and imports agents will need
- Similar features already built (copy their patterns)
3. **Read full contents** of every file that will be touched — agents need exact code context
### Circuit Breaker
After exploration, if you cannot decompose the task into **concrete file-level changes** (the task is too vague, ambiguous, or requires decisions you can't make from code alone), use AskUserQuestion to clarify before proceeding. Examples:
- "Make the app better" → ask what specifically
- "Add authentication" → ask which auth method
- "Refactor the frontend" → ask which part and to what end
If the task IS clear enough to decompose into file changes, proceed without asking.
---
## Phase 2: Decompose
Break the task into **independent work units** that can run in parallel.
### Rules:
- Each unit touches a **non-overlapping set of files** — this is the most important rule
- Each unit is **self-contained** — completable without knowing about other units
- Each unit has a **verification step**
### Dependency Handling:
If Unit B depends on Unit A (e.g., A creates a component, B imports it):
- Put them in **ordered batches**: Batch 1 = [A], Batch 2 = [B]
- Batch 1 completes fully before Batch 2 spawns
- Within a batch, all units run in parallel
If units are fully independent, they all go in Batch 1.
### Isolation Mode:
Determine if the task involves **code changes** (modifying source code in a repository) or **knowledge work** (editing notes/, ops/, markdown files in a vault):
- **Code tasks** → set `isolation: "worktree"` on all spawned agents. Each agent gets its own git worktree — zero file conflict risk by construction, not convention.
- **Knowledge tasks** → skip worktree isolation. Notes and ops files are append-mostly; the non-overlapping file rule is sufficient.
**Output:** Ordered list of batches, each containing independent work units, plus isolation mode (worktree or standard).
---
## Phase 3: Write Specs
For each work unit, write a **fully self-contained spec**. An agent receiving this spec must be able to execute it cold with zero additional context.
Every spec MUST include:
### A. Context Block
```
PROJECT: [path to project root]
STACK: [e.g., Next.js + React + Auth0 + lucide-react icons + CSS variables]
FILES TO READ FIRST: [exact paths]
```
### B. Existing Code Snippets
Paste the actual code from explored files that the agent needs to follow. Not "follow existing patterns" — paste the pattern. Include:
- Import conventions
- Component structure
- Styling approach (CSS variables, inline styles, class names)
- Auth patterns
- Any shared utilities
### C. Implementation Instructions
For each file:
- **New files:** Full content or detailed structure with actual code
- **Edits:** Exact old string → new string, or where to insert with surrounding context
- Import statements, function signatures, props — be explicit
### D. Verification
How the agent should verify its work completed correctly.
### E. Leaf-Node Constraint (include in EVERY spec)
```
IMPORTANT: You are a leaf-node Task agent.
- DO NOT invoke any skills (like /extract, /connect, etc.)
- DO NOT spawn any agents
- DO NOT ask questions — execute the spec
- If something is ambiguous, match the closest existing pattern in the codebase
```
---
## Phase 4: Execute
### Single Batch:
Spawn all Task agents **in parallel** in a single message:
```
Task(
prompt = {spec},
description = "{5 words max}",
subagent_type = "general-purpose",
isolation = "worktree" // only for code tasks — omit for knowledge work
)
```
### Multiple Batches:
Execute batch by batch. Wait for Batch N to fully complete before spawning Batch N+1.
**Max 5 concurrent agents per batch.** If a batch has more than 5 units, split into sub-batches.
---
## Phase 5: Review & Integrate
After ALL agents in ALL batches report back:
1. **Read every modified/created file** to verify changes are correct
2. **Check integration points:**
- Do imports across files align? (Agent A created it, Agent B imports it)
- Naming consistency?
- Styling consistency?
3. **Fix issues directly** — small integration fixes are your job
4. **Run practical checks:**
- For Python: `python -c "from app.module import thing"` to verify imports
- For Next.js/React: check that imports reference real files and exports
- If the project has a build command and changes are significant, run it
5. **Failure reactions:**
- If an agent returned **empty or error output**: retry once — re-spawn a single agent with the same spec. Cap: 1 retry per unit.
- If the retry also fails, or the output is merely **low quality**: fix it yourself rather than re-spawning again.
- Track retry count for the report.
---
## Phase 6: Report
```
--=={ delegate }==--
Task: {original task description}
Batches: {N} ({sequential if >1, parallel if 1})
Agents spawned: {total count}
Work Units:
1. {unit name} — {done/fixed/failed}
2. {unit name} — {done/fixed/failed}
Files Created:
- {path} — {purpose}
Files Modified:
- {path} — {what changed}
Integration Fixes: {count or "none needed"}
Retries: {count or "none"}
Ready to test: {specific instructions}
```
---
## Critical Constraints
**Never:**
- Come back to the user mid-task unless circuit breaker fires
- Let agents touch overlapping files
- Skip the review phase
- Execute implementation yourself instead of spawning agents (orchestrate, don't do)
- Write specs without actual code snippets from the codebase
**Always:**
- Read all files BEFORE writing specs
- Include real code in specs
- Spawn agents in parallel within a batch
- Review all changes after agents complete
- Fix integration issues before reporting
- Report only when fully complete