메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Show the user the agent's work on a research project and save iterations on the user's behalf. Scaffold rendering and deploy infrastructure (Quarto today, GitHub Pages, dev container), show the rendered output, save iterations. Doesn't handle research execution (use `asta-flows`).
Install or update the `asta` CLI to the version pinned by this plugin. Invoke whenever `asta` is not on PATH (e.g. `command not found` for `asta`) or when a subcommand/flag appears missing — that signals a stale install needing an update.
Converse with the user to identify the next most productive units of work for the current project, and record them in project.md under Pending Work. Use when the user wants to plan what to work on next, or when there is no project.md yet.
Write a detailed, executable plan for a single unit of work, then get it approved by review-plan. Updates work/<slug>/README.md with concrete instructions and sets status to ready (or needs-input if review repeatedly rejects).
Critic skill. Given a plan in work/<slug>/README.md (status pending-review), check that the steps are concrete, the tools are appropriate, and the plan is realistic. Write a verdict and feedback back into the README.
Critic skill. Given an executed work item (status pending-assessment), assess whether the Goal was actually accomplished. Identify the root cause when it was not (incorrect assumption, technical blocker, missing data). Updates work/<slug>/README.md Assessment section.
| 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:*) Skill(asta-preview:*) |
Executes a single ready work item end-to-end. The plan in # Instructions is the contract; this skill follows it rather than redesigning it.
work/<slug>/README.md with status: ready and a populated # Instructions section.
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.status: pending-assessment.Lock the item. Set frontmatter status: in-progress to prevent re-entry.
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.
Execute step-by-step. For each step:
work/<slug>/data/ using the names from the plan.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.
Write # Results. Structure:
# Results
## Summary
<one paragraph>
## Artifacts
- `data/<file>` — <one-line description>
## Step-by-step
<what was done for each plan step, including deviations and failures>
Set status and hand off. Set frontmatter status: pending-assessment, then invoke review-work with the slug.