Delegate

Skill nyechiel/ai-augmented-workflow/skills/delegate

A template for building your own AI-powered knowledge worker workflow using Claude Code and MCP.

Install

npx -y skills add nyechiel/ai-augmented-workflow --skill delegate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Pick up a task from Crux (or described inline), execute it autonomously, produce a deliverable, and set status to review. The agent never marks tasks done - the user is the final gate.

SKILL.md

3.2 KB, as published. Nobody here has run it

Task Delegation

Execute a task as the "Worker" agent. Produce a deliverable and hand it back for review.

Use user_google_email: "{YOUR_EMAIL}" for all Google Workspace calls.

Workflow

1. Pick Up the Task

If a Crux task ID is provided: Fetch details, set status to "doing".

If an inline description is provided: Create a task in Crux with status: "doing", assignee: "Worker".

If neither: List Worker tasks in "todo" status and ask which to pick up.

2. Understand the Task

Confirm you understand:

What: The specific deliverable
Where: Where to save the output
Context: Links to read, people involved

If ambiguous, ask one round of clarifying questions.

3. Execute

Common patterns:

Task Type	Actions	Deliverable
Reading	WebFetch the content, extract key points	Notes saved to `research/reading-notes/`
Research	Web search + repo grep + Slack/email search	Summary saved to `research/`
Document Draft	Read context, draft document	Saved to appropriate directory
Email/Message Draft	Read context, draft text	Presented in terminal for copy

Log progress to the Crux task using add_comment at key moments.

4. Produce the Deliverable

Save file-based deliverables to the appropriate repo location. Present a summary of what was done and anything needing the user's attention.

5. Hand Off for Review

Set the task status to "review" and add a final comment:

## Done
- [what was accomplished, with file paths]

## For your review
- [ ] [specific action the user should take]
- [ ] Move to done or request revisions

Never mark tasks done. That is the user's decision after review.

Rules

Never create title-only tasks. Always include origin and deliverable.
Never skip the deliverable. Every task produces a concrete output.
Stay in scope. Note adjacent work as a suggestion, don't do it.
Fail loudly. If blocked, set the task to "blocked" and explain what's needed.

Graceful Degradation

Scenario	Behavior
Crux unavailable	Work from inline description, present deliverable in terminal
Referenced tools unavailable	Note what you couldn't check, proceed with available tools