sakura-delegate

Delegates bounded development tasks to subagents and preserves their results in the parent context.

3|1|Updated Sep 9, 2026
One-click install
npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-delegate-v20227
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sakura-delegate
Source: https://github.com/v20227/using-sakura-dev/tree/main/skills/sakura-delegate
Command: npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-delegate-v20227

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating work to subagents often leads to lost results, duplicated assignments, orphaned contexts, and uncontrolled parallel writes. This Skill defines a disciplined protocol for dispatching, receiving, and cleaning up supporting contexts so the main task keeps a recoverable record of every delegated outcome. ## Core Features & Use Cases - Bounded Dispatch: Assigns each supporting conversation exactly one focused task with explicit scope, authority limits, and stop conditions, using native subagent or task tools. - Result Recovery: Preserves returned conclusions, artifacts, evidence, and next actions in the parent context so nothing depends on the child conversation surviving. - Prompt Cleanup: Closes or archives completed contexts immediately after handoff and tracks status in a context ledger, with defined handling for failed cleanup. - Use Case: While building a feature, you dispatch one subagent to research an API and another to run tests in parallel; each returns once, results are recorded in the project state, and both contexts are closed before integration continues. ## Quick Start Delegate the independent research and test-execution parts of this task to subagents, then collect and preserve their results in the main task.

Frequently Asked Questions about sakura-delegate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate coding tasks to subagents without losing their results?▼

Assign each subagent one bounded task with explicit scope and stop conditions, then preserve its returned conclusion, artifacts, and evidence in the parent context before closing it. The parent must make every accepted result recoverable without relying on the child conversation.

When should I use subagents instead of doing work in the main conversation?▼

Use subagents for independent exploration, research, implementation, test execution, log analysis, diagnosis, or review that would add noise to the main task. Keep tightly coupled work together and only parallelize writes with mutually exclusive file ownership.

Can a subagent delegate its own work to another subagent?▼

A project task may assign a complete workstream and a workstream may assign bounded support work, but a support context must not delegate its entire objective again. This prevents unbounded delegation chains.

What happens if subagent cleanup fails or is unavailable?▼

The acknowledged result is retained, the cleanup status is recorded as FAILED or UNAVAILABLE in the context ledger, and that context is never reused. The parent work continues and cleanup is retried at the next recovery point.

What permissions should a delegated subagent have?▼

Supporting contexts receive only the read scope and exclusive write scope their task requires. They are never granted authority to commit, push, merge, deploy, publish, purchase, use credentials, delete data, or mutate external systems.