invoke-impl

Agent Skills › AjayIrkal23/agentic-mercy-10x › invoke-impl

invoke-impl

GitHub

执行 impl 行动，调度实现工程师生成 IMPL-REPORT.md。处理运行文件夹管理、子代理分发及失败重试，支持 opus-guard 路由，适用于代码实现任务。

skills/invoke-impl/SKILL.md AjayIrkal23/agentic-mercy-10x

Trigger Scenarios

需要自动化执行代码实现任务生成实现报告并归档到运行文件夹

Install

npx skills add AjayIrkal23/agentic-mercy-10x --skill invoke-impl -g -y

More Options

Use without installing

npx skills use AjayIrkal23/agentic-mercy-10x@invoke-impl

指定 Agent (Claude Code)

npx skills add AjayIrkal23/agentic-mercy-10x --skill invoke-impl -a claude-code -g -y

安装 repo 全部 skill

npx skills add AjayIrkal23/agentic-mercy-10x --all -g -y

预览 repo 内 skill

npx skills add AjayIrkal23/agentic-mercy-10x --list

SKILL.md

Frontmatter

{
    "name": "invoke-impl",
    "description": "Run the IMPL act — dispatches implementation-engineer (default sonnet; opus-guard routes) and writes `IMPL-REPORT.md` into a run folder. Single-act form of `\/invoke impl -- <task>`.",
    "argument-hint": "[--run <dir>] [task]"
}

Run the impl act for: $ARGUMENTS

This is /invoke impl without the closers; ~/.claude/skills/invoke/SKILL.md governs anything not said here.

Run folder: --run <dir> in the arguments → reuse that folder (absolute path) and update its run.json with Edit; otherwise create a new one exactly as /invoke §2 (RUN="$(git rev-parse --show-toplevel)/.claude/runs/$(date -u +%Y%m%dT%H%M)-$SLUG", BRIEF.md, run.json with "acts": ["impl"]). Never write into any other existing run folder.
Set run.json.expected_artifacts["implementation-engineer"] = "IMPL-REPORT.md".
Agent(subagent_type="implementation-engineer", description="impl: <task>", prompt=...). The prompt names $RUN/BRIEF.md, every artifact already in $RUN/, and the exact output path $RUN/IMPL-REPORT.md. No model=: opus-guard routes it (pins, escalation, per-project mode). Artifact missing or the act failed → re-dispatch once with the prompt prefixed Previous attempt failed: <one-line reason>.
Append impl to run.json.done, then report the artifact path and a one-paragraph verdict.

This form always dispatches implementation-engineer (general/infra). For frontend- or backend-specific work prefer /invoke impl -- <task>, which surface-routes to the FE/BE specialists. A plan artifact in the run folder is the input; without one the implementor writes a mini-plan first.