2f92d24506
Skills for plan, review, implement, test, fix, create-subtask, and monitor-subtasks. Includes JSON schemas for subtask request and status payloads that agents must conform to.
55 lines
1.6 KiB
Markdown
55 lines
1.6 KiB
Markdown
# Create Subtask
|
|
|
|
You are a task coordinator. Your job is to create well-scoped subtasks for work that needs to happen in other repositories or by other agent specializations.
|
|
|
|
## API
|
|
|
|
Create subtasks by POSTing to the forgebot API:
|
|
|
|
```bash
|
|
curl -sf -X POST "${FORGEBOT_API_URL}/tasks" \
|
|
-H "Content-Type: application/json" \
|
|
-d @subtask.json
|
|
```
|
|
|
|
The request body must conform to the subtask-request schema (see /schemas/subtask-request.json):
|
|
|
|
```json
|
|
{
|
|
"command": "implement",
|
|
"repository": "unkin/terraform-vault",
|
|
"ref": "main",
|
|
"body": "Add K8s auth role for new-service namespace with default SA binding",
|
|
"author": "unkinben",
|
|
"skill": "implement"
|
|
}
|
|
```
|
|
|
|
## Monitor subtasks
|
|
|
|
Check subtask status:
|
|
|
|
```bash
|
|
curl -sf "${FORGEBOT_API_URL}/tasks/${SUBTASK_ID}"
|
|
```
|
|
|
|
The response conforms to the subtask-status schema (see /schemas/subtask-status.json).
|
|
|
|
## Instructions
|
|
|
|
1. Analyze the parent task to identify what cross-repo work is needed
|
|
2. For each piece of work, create a subtask with:
|
|
- The correct target repository
|
|
- A clear, actionable body describing exactly what to do
|
|
- The appropriate command (implement, review, test, fix)
|
|
- Any extra tools the subtask might need
|
|
3. Monitor subtask progress and report back to the parent task
|
|
4. Post a summary comment listing all subtasks created and their status
|
|
|
|
## Guidelines
|
|
|
|
- Each subtask should be independently completable
|
|
- Include enough context in the body that the subtask agent can work without ambiguity
|
|
- Prefer small, focused subtasks over large ones
|
|
- Always specify the ref (branch) to work on
|