do-work
/do-work
Execute the approved plan in work/<slug>/README.md (status ready), write outputs into work/<slug>/data/, record what happened in the Results section, then hand off to review-work. Use when there is a ready work item.
- Author
- allenai ↗
- Repository
- asta-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Execute the approved plan in work/<slug>/README.md (status ready), write outputs into work/<slug>/data/, record what happened in the Results section, then hand off to review-work. Use when there is a ready work item.
Original author description
Execute the approved plan in work/<slug>/README.md (status ready), write outputs into work/<slug>/data/, record what happened in the Results section, then hand off to review-work. Use when there is a ready work item.
How it works
- Input
- Output
- Procedure
- Out of scope
SKILL.md preview
--- name: do-work description: Execute the approved plan in work/<slug>/README.md (status ready), write outputs into work/<slug>/data/, record what happened in the Results section, then hand off to review-work. Use when there is a ready work item. allowed-tools: Read(work/**) Read(project.md) Edit(work/**) Write(work/**) Bash(*) Skill(asta-assistant:review-work) Skill(asta-assistant:save-work) Skill(asta-tools:*) --- # Do Work Executes a single ready work item end-to-end. The plan in `# Instructions` is the contract; this skill follows it rather than redesigning it. ## Input `work/<slug>/README.md` with `status: ready` and a populated `# Instructions` section. ## Output - `work/<slug>/data/` — any data artifacts the plan produced. Each artifact should have a stable name referenced from the README. - `work/<slug>/README.md` updated: - `# Results` populated with a natural-language narrative of what was actually done, what artifacts were produced, and anything that diverged from the plan. - Frontmatter `status: pending-assessment`. - A handoff to **review-work** with the slug. ## Procedure 1. **Lock the item.** Set frontmatter `status: in-progress` to prevent re-entry. 2. **Read the plan.** Open `# Instructions`. If it is empty or vague, set `status: needs-input` and stop — the plan should have been concrete coming out of **plan-work**/**review-plan**. Do not improvise design decisions here. 3. **Execute step-by-step.** For each step: - Run the named tool/command/skill with the specified inputs. - Save artifacts under `work/<slug>/data/` using the names from the plan. - If a step fails, capture the error verbatim (do not silently retry with a different approach). 4. **Handle deviations.** When reality forces a deviation (a tool produced unexpected output, an external dependency is unavailable, a step turned out to be unnecessary), document it in `# Results` with: what was planned, what actually happened, why the deviation was justified. Do **not** silently substitute one step for another. 5. **Write `# Results`.** Structure: ```markdown # Results ## Summary <one paragraph> ## Artifacts - `data/<file>` — <one-line description> ## Step-by-step <what was done for each plan step, including deviations and failures> ``` 6. **Set status and hand off.** Set frontmatter `status: pending-assessment`, then invoke **review-work** with the slug. ## Out of scope - Designing or revising the plan (that is **plan-work**). - Assessing success (that is **review-work**). - Indexing or committing artifacts (that is **save-work**).
Versions
The database has no other skills named do-work.
Database snapshot: 13.11.2026 · package version fd6c076b1dd9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90lantern-plan-handoff
Hand an approved Lantern plan to `lantern-delegate` and keep it ticked - `plan.mjs handoff` names the items of the next unblocked stage (a stage with unanswered questions gives the questions to ask first), each delegate's brief is written from its item, delegates record… - 100aiwork-protocol
Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (intent, triage, research, spec, prd, areas, plan, review, notes, docs/). Use when the user asks to plan, capture an intent, make a spec, triage, research a task, write a report,… - 100execute-via-cursor
Hand a fleet plan under docs/plans/** to Cursor's agent CLI for implementation, then Claude reviews the result against the plan (diff + Verification) with a short FIX resume loop. Alternative to in-process /execute-plan. Claude does not implement; Cursor does. Args: [plan-file]… - 90write-handoff
Build features/<slug>/handoff.md for a coding agent from approved steps and approved brain entries only. Use when someone says "write the handoff" or "hand this to the coding agent". - 86plan-capture
Capture an approved plan as tracked work items. Use when exiting plan mode, when the user approves a plan, or says "capture this plan". Writes docs/plans/<date>-<slug>.md and appends the plan''s tasks to .work/todo.jsonl via bin/worklog. - 100perform-task
Implement, self-review, test, and commit exactly one existing ai/tasks task, by slug or full date/slug id. Use when the user invokes /perform-task <name>, or the continue scheduler delegates one selected task.