spec-task

v1.2.1

结构化任务管理与生命周期强制执行。以下场景必须使用:(1) 任何被 coordinator 通过 sessions_spawn 派发的任务 (2) 可拆解步骤≥3 的复杂任务 (3) 工作区已存在 spec-task/ 目录时的后续任务 (4) 用户显式要求使用 spec-task (5) prependCont...

0· 88·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (structured task management, lifecycle enforcement) match the provided artifacts: SKILL.md, schemas, templates, and config all define a spec-driven task workflow. There are no unrelated required env vars, binaries, or install steps.
Instruction Scope
The runtime instructions require reading and writing workspace files (spec-task/<task>/status.yaml, brief/spec/plan/checklist, outputs/, memory/task-history, etc.) and mandate a strict workflow for child agents. That file I/O and workspace mutation are expected for a task-management skill, but you should be aware it will create and update files in the agent workspace and agent memory. There are no instructions to call external network endpoints or access unrelated system config.
Install Mechanism
Instruction-only skill with no install spec and no code files to fetch or execute. This is the lowest-risk install profile.
Credentials
The skill declares no required environment variables, credentials, or config paths. The config.yaml controls local behavior (timeouts, archive rules). Requested accesses (workspace, writing memory archives) are proportional to a task-management capability.
Persistence & Privilege
always:false (normal). The skill expects to write archival history and lessons into agent memory and workspace (memory/task-history, memory/task-lessons, outputs/). This is typical for a task-tracking skill but means artifacts and potentially sensitive content could be stored in the agent workspace/memory—review storage policies if that is a concern. The skill also enforces use by spawned child agents per its instructions; that is a behavioral constraint rather than an elevated system privilege.
Assessment
This skill is coherent for enforcing a spec-driven task workflow and is instruction-only (no external downloads or credential requests). Before installing: (1) confirm you are comfortable with the skill creating and modifying files under your agent workspace (spec-task/<task>/, outputs/, memory/*), (2) ensure no sensitive secrets or PII will be written to those locations, (3) be aware child agents dispatched by a coordinator will be required to follow this workflow (may interfere with other agent behaviors), and (4) review and, if needed, adjust config.yaml (timeouts, auto_archive, per_agent_archive) to match your environment. A minor oddity: docs mention legacy .py script names even though no Python scripts are included—this appears to be a documentation remnant only.

Like a lobster shell, security has layers — review code before you run it.

Deprecatedvk970rn2b75hyqcfnc8gpc3j9en83t0qjlatestvk970rn2b75hyqcfnc8gpc3j9en83t0qj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments