技能工具
- 作者仓库星标 435
- 作者仓库 nvim
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @benbrastmckie · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- Python
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Epi Implement Skill
Thin wrapper that delegates epidemiology implementation to `epi-implement-agent` subagent.
**IMPORTANT**: This skill implements the skill-internal postflight pattern. After the subagent returns,
this skill handles all postflight operations (status update, artifact linking, git commit) before returning.
## Context References
Reference (do not load eagerly):
- Path: `.claude/context/formats/return-metadata-file.md` - Metadata file schema
- Path: `.claude/context/patterns/postflight-control.md` - Marker file protocol
- Path: `.claude/context/patterns/file-metadata-exchange.md` - File I/O helpers
- Path: `.claude/context/patterns/jq-escaping-workarounds.md` - jq escaping patterns (Issue #1132)
Note: This skill is a thin wrapper with internal postflight. Context is loaded by the delegated agent.
## Trigger Conditions
This skill activates when:
- `/implement` on a task with `task_type: "epi"` or `task_type: "epi:study"`
- Epidemiology extension is available
---
## Input Parameters
### Required Parameters
- `task_number` - Task number (must exist in state.json with task_type="epi" or "epi:study")
- `session_id` - Session ID from orchestrator
---
## Execution Flow
### Stage 1: Input Validation
Validate required inputs:
- `task_number` - Must be provided and exist in state.json
- Verify task_type is "epi" or "epi:study"
```bash
task_data=$(jq -r --argjson num "$task_number" \
'.active_projects[] | select(.project_number == $num)' \
specs/state.json)
if [ -z "$task_data" ]; then
return error "Task $task_number not found"
fi
task_type=$(echo "$task_data" | jq -r '.task_type // ""')
status=$(echo "$task_data" | jq -r '.status')
project_name=$(echo "$task_data" | jq -r '.project_name')
description=$(echo "$task_data" | jq -r '.description // ""')
if [ "$task_type" = "epi" ] || [ "$task_type" = "epi:study" ]; then
: # valid
else
return error "Task $task_number is not an epi task (task_type=$task_type)"
fi
```
---
### Stage 2: Preflight Status Update
| state.json status | TODO.md marker |
|------------------|----------------|
| implementing | [IMPLEMENTING] |
```bash
jq --arg ts "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
--arg status "implementing" \
--arg sid "$session_id" \
'(.active_projects[] | select(.project_number == '$task_number')) |= . + {
status: $status,
last_updated: $ts,
session_id: $sid
}' specs/state.json > specs/tmp/state.json && mv specs/tmp/state.json specs/state.json
```
---
### Stage 3: Create Postflight Marker
```bash
padded_num=$(printf "%03d" "$task_number")
mkdir -p "specs/${padded_num}_${project_name}"
cat > "specs/${padded_num}_${project_name}/.postflight-pending" << EOF
{
"session_id": "${session_id}",
"skill": "skill-epi-implement",
"task_number": ${task_number},
"operation": "epi_implement",
"reason": "Postflight pending: status update, artifact linking, git commit",
"created": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
"stop_hook_active": false
}
EOF
```
---
### Stage 4: Prepare Delegation Context
Read the implementation plan to identify phases for per-phase delegation.
```json
{
"session_id": "sess_{timestamp}_{random}",
"delegation_depth": 1,
"delegation_path": ["orchestrator", "implement", "skill-epi-implement"],
"timeout": 3600,
"task_context": {
"task_number": N,
"task_name": "{project_name}",
"description": "{description}",
"task_type": "{task_type}"
},
"workflow_type": "epi_implement",
"forcing_data": "{from state.json task metadata: study_design, data_paths, etc.}",
"research_report_path": "specs/{NNN}_{SLUG}/reports/{MM}_epi-research.md",
"plan_path": "specs/{NNN}_{SLUG}/plans/{MM}_implementation-plan.md",
"metadata_file_path": "specs/{NNN}_{SLUG}/.return-meta.json"
}
```
Phased delegation: Read plan phases from the plan file. Delegate each phase to the subagent
sequentially, passing phase number and details. Resume from last incomplete phase on re-invocation.
---
### Stage 5: Invoke Subagent
**CRITICAL**: Use the **Agent** tool to spawn the subagent.
```
Tool: Agent (NOT Skill, NOT Plan)
Parameters:
- subagent_type: "epi-implement-agent"
- prompt: [Include task_context, delegation_context, workflow_type, forcing_data, research_report_path, plan_path, metadata_file_path]
- description: "Execute epi_implement for task {N}"
```
**DO NOT** use `Skill(epi-implement-agent)` - this will FAIL.
For phased plans, invoke subagent per-phase with phase context. Commit after each phase.
---
### Stage 5b: Self-Execution Fallback
**CRITICAL**: If you performed the work above WITHOUT using the Agent tool (i.e., you read files,
wrote artifacts, or updated metadata directly instead of spawning a subagent), you MUST write a
`.return-meta.json` file now before proceeding to postflight. Use the schema from
`return-metadata-file.md` with the appropriate status value for this operation.
If you DID use the Agent tool, skip this stage -- the subagent already wrote the metadata.
---
## Postflight (ALWAYS EXECUTE)
The following stages MUST execute after work is complete, whether the work was done by a
subagent or inline (Stage 5b). Do NOT skip these stages for any reason.
### Stage 6: Read Metadata File
```bash
metadata_file="specs/${padded_num}_${project_name}/.return-meta.json"
if [ -f "$metadata_file" ] && jq empty "$metadata_file" 2>/dev/null; then
meta_status=$(jq -r '.status' "$metadata_file")
artifact_path=$(jq -r '.artifacts[0].path // ""' "$metadata_file")
artifact_type=$(jq -r '.artifacts[0].type // ""' "$metadata_file")
artifact_summary=$(jq -r '.artifacts[0].summary // ""' "$metadata_file")
else
echo "Error: Invalid or missing metadata file"
meta_status="failed"
fi
```
---
### Stage 7: Update Task Status (Postflight)
**MUST NOT cross the postflight boundary**: The subagent MUST NOT update state.json or TODO.md status.
Only this skill performs postflight status transitions.
| Meta Status | Final state.json | Final TODO.md |
|-------------|-----------------|---------------|
| completed | completed | [COMPLETED] |
| partial | implementing | [IMPLEMENTING] |
| failed | (keep preflight) | (keep preflight marker) |
---
### Stage 8: Link Artifacts
Add artifact to state.json with summary. Use the two-step jq pattern to avoid Issue #1132.
Artifact type: "summary" (implementation summary with R script paths).
**Update TODO.md**: Link artifact using count-aware format. Apply the four-case Edit logic from `@.claude/context/patterns/artifact-linking-todo.md` with `field_name=**Summary**`, `next_field=**Description**`.
---
### Stage 9: Git Commit
```bash
git add -A
git commit -m "task ${task_number}: complete epi implementation
Session: ${session_id}"
```
---
### Stage 10: Cleanup
```bash
rm -f "specs/${padded_num}_${project_name}/.postflight-pending"
rm -f "specs/${padded_num}_${project_name}/.postflight-loop-guard"
rm -f "specs/${padded_num}_${project_name}/.return-meta.json"
```
---
### Stage 11: Return Brief Summary
**Implementation Success**:
```
Epi implementation completed for task {N}:
- R analysis scripts created and validated
- Created summary at specs/{NNN}_{SLUG}/summaries/{MM}_epi-implementation-summary.md
- Status updated to [COMPLETED]
- Changes committed with session {session_id}
```
---
## Error Handling
### Task not found
```
Epi implement skill error for task {N}:
- Task not found in state.json
- No status changes made
```
### Wrong task_type
```
Epi implement skill error for task {N}:
- Task is not an epi task (task_type={task_type})
- No status changes made
```
### Metadata file missing
Keep status at preflight level for resume.
### Git commit failure
Non-blocking. Log failure but continue.
---
## MUST NOT (Postflight Boundary)
After the agent returns -- whether with status implemented, partial, or failed -- this skill MUST proceed immediately to postflight (Stage 6). The skill MUST NOT:
1. **Edit R/Python files** - All analysis work is done by agent
2. **Run R scripts** - Execution is done by agent
3. **Use MCP tools** - Domain tools are for agent use only
4. **Analyze or grep source** - Analysis is agent work
5. **Write summary/reports** - Artifact creation is done by agent
> **PROHIBITION**: If the subagent returned partial or failed status, the lead skill MUST NOT attempt to continue, complete, or "fill in" the subagent's work. Report the partial/failed status and let the user re-run `/implement` to resume.
The postflight phase is LIMITED TO:
- Reading agent metadata file
- Updating state.json via jq
- Updating TODO.md status marker via Edit
- Linking artifacts in state.json
- Git commit
- Cleanup of temp/marker files
Reference: @.claude/context/standards/postflight-tool-restrictions.md
---
## Return Format
This skill returns a **brief text summary** (NOT JSON). The JSON metadata is written to the file and processed internally.
章节与文件索引
按说明文件中的顺序排列。
上下文参考
触发条件
所需参数
第一阶段:输入验证
第 2 阶段:预检状态更新
文件/命令 -> epi-implement-agent · .claude/context/formats/return-metadata-file.md · .claude/context/patterns/postflight-control.md · .claude/context/patterns/file-metadata-exchange.md · .claude/context/patterns/jq-escaping-workarounds.md · /implement · task_type: "epi" · task_type: "epi:study"
内容校验值 -> f4cf4fcd1642
当前原文的自动摘译,尚未人工审校。
上下文参考
参考(不要急于加载):路径:
.claude/context/formats/return-metadata-file.md- 元数据文件模式路径:.claude/context/patterns/postflight-control.md- 标记文件协议路径:.claude/context/patterns/file-metadata-exchange.md- 文件 I/O 帮助程序路径:.claude/context/patterns/jq-escaping-workarounds.md- jq 转义模式(问题#1132)触发条件
该技能在以下情况下激活:
/implement任务中具有task_type: "epi"或task_type: "epi:study"流行病学扩展可用所需参数
task_number- 任务编号(必须存在于 state.json 中,其中 task_type="epi" 或 "epi:study")session_id- 来自 Orchestrator 的会话 ID第一阶段:输入验证
验证所需的输入:
task_number- 必须提供并存在于 state.json 中验证 task_type 是“epi”还是“epi:study”第 2 阶段:预检状态更新
state.json 状态 · TODO.md 标记实现 · [实施]