Install
$ agentstack add skill-rse-ase-ase-task-implement ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
@${CLAUDESKILLDIR}/../../meta/ase-control.md @${CLAUDESKILLDIR}/../../meta/ase-skill.md @${CLAUDESKILLDIR}/../../meta/ase-dialog.md @${CLAUDESKILLDIR}/../../meta/ase-getopt.md
Implement a Task Plan
$ARGUMENTS
Implement the task plan by modifying the artifacts with a corresponding, complete change set.
@${CLAUDESKILLDIR}/../../meta/ase-format-task.md
Procedure ---------
- Determine Task:
- Set initially.
Inherit the always existing from the current context. Inherit the always existing from the current context. Do not output anything.
- React on task id:
- matches the regexp
^[a-zA-Z][a-zA-Z0-9_-]*$
"> Set (set task id to instruction) and (set instruction empty), call the ase_task_id(id: "", session: "") tool from the ase MCP server to switch the task, and then only output the following :
⧉ ASE: ◉ task: **, ▶ status: task given**
- has the format
:where
matches the regexp ^[a-zA-Z][a-zA-Z0-9_-]*$ and is empty "> Set (set instruction to empty) and (set task id to id) and call the ase_task_id(id: "", session: "") tool from the ase MCP server to switch the task, and then only output the following :
⧉ ASE: ◉ task: **, ▶ status: task given**
- is NOT empty">
The argument is neither empty nor a valid task id. As this skill only accepts an optional [] argument and never a free-text instruction, only output the following and then immediately STOP processing the entire current skill:
⧉ ASE: ☻ skill: ase-task-implement, ▶ ERROR: expected single [] argument
- Determine Operation:
- Determine the current task plan content:
is equal true and a ase_task_save(id: '', ...) tool call exists earlier in the current session "> Set to the text argument of the most recent ase_task_save(id: '', ...) tool call, without calling ase_task_load again. Set plan reused. Do not output anything.
Call the ase_task_load(id: "") tool of the ase MCP server to load the current task plan content and set to the text output field of this ase_task_load tool call. Do not output anything related to this MCP tool call. Set plan loaded.
- If starts with
ERROR:orWARNING::
Set (set content to empty). Set to "0".
- If starts NOT with
ERROR:and NOT withWARNING::
Set (set content to text). Calculate the number of words of .
Only output the following :
⧉ ASE: ◉ task: **, ✪ plan: words, ▶ status: **
- If the is still empty, complain and tell the user to
use the ase-code-resolve, ase-code-refactor, ase-code-craft, or ase-task-edit skills first to create a task plan. Then immediately stop processing this skill.
- Create Implementation:
- Perform a final implementation of the task plan
by modifying the artifacts with a corresponding, complete change set.
For this, primarily follow and honor the task plan in .
Secondarily, derive hints from the optionally existing IMPLEMENTATION DRAFT section (from skill ase-task-preflight) in . But the specification text in always overrules the implementation draft in the IMPLEMENTATION DRAFT section of .
does NOT contain a ## VERIFICATION section heading"> The task plan deliberately omits the ## VERIFICATION section. You MUST therefore strictly skip the entire verification phase after modifying the source files: do NOT run any build, do NOT run any tests, do NOT run any linter, do NOT run any type-checker, do NOT execute the modified program, and do NOT otherwise verify the change set in any way.
- Only output the following :
⧉ ASE: ◉ task: **, ✪ plan: words, ▶ status: plan implemented**
- Decide Next Step:
- Determine next step:
- If is not equal to
none:
Treat as a comma-separated chronological list of pre-selected next-step tokens. Split it on ,, take the first token as , and store the remaining tokens (joined back with ,, or none if empty) into so downstream skills can consume the tail.
- If matches the regex
^(DONE|DELETE)$:
Honor the pre-selected token. Set .
- else:
Only output the following and then immediately STOP processing the entire current skill:
⧉ ASE: ☻ skill: ase-task-implement, ▶ ERROR: invalid --next token: ****
- If is equal to
none:
In the following, you MUST NOT use your built-in tool! Instead, you MUST just show a custom dialog according to the expanded custom-dialog definition. You MUST closely follow this definition:
Next Step: How would you like to proceed with the plan? DONE: Stop processing and PRESERVE task plan. DELETE: Stop processing and DELETE the task plan.
- Check the tool and dispatch accordingly:
- If is
DONEorCANCEL:
Only output the following and then STOP.
⧉ ASE: ◉ task: **, ✪ plan: words, ▶ status: plan implemented -- done**
- If is
DELETE:
Set (empty). Do not forward any remaining --next list tokens, because the ase:ase-task-delete skill accepts only an optional [] argument and no --next option; remaining tokens are intentionally discarded. Only output the following and then call the tool Skill(skill: "ase:ase-task-delete", args: "") to invoke the ase:ase-task-delete skill in order to delete the updated plan. Immediately stop processing the current skill once the Skill tool was used.
⧉ ASE: ◉ task: **, ✪ plan: words, ▶ status: plan implemented -- hand-off to delete task**
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.