spec-stateflow
PassAudited by ClawScan on May 8, 2026.
Overview
This instruction-only skill appears to be a coherent software-planning workflow, but users should be aware it can guide the agent to edit project files, commit changes, and rely on persistent task state.
Before installing, confirm you want this skill to manage a structured development workflow in your repository. It appears benign, but because it can guide file edits, commits, state recovery, and continuous execution, review the generated requirements, design, tasks.md, and code diffs before accepting changes.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may change project files and commit those changes as part of the workflow.
The test expectations show the workflow can direct the agent to modify files and create commits. This is purpose-aligned for a coding workflow, but it is still meaningful local mutation authority.
Agent应读取tasks.md，将第一个任务标记为[~]，执行该任务（涉及文件、具体方法），完成后更新tasks.md为[✓]，提交commit
Review requirements, design, and tasks.md before allowing execution; inspect diffs before accepting or pushing commits.
If tasks.md is inaccurate or modified unexpectedly, the agent could continue from the wrong task or perform unintended project work.
The skill treats a persistent local task file as authoritative state for future execution and recovery. That is useful for the workflow, but stale or incorrect contents could steer later agent behavior.
`{SPEC_PATH}/tasks.md` | Task breakdown & progress tracker (Phase 3 output, **single source of truth**)Keep the spec files in a trusted project location and review tasks.md after interruptions, context switches, or manual edits.
If continuous mode is enabled, the agent may proceed through multiple implementation tasks before stopping.
The skill references an authorized continuous operation mode. The provided artifact excerpt does not show hidden persistence, but continuous automation can broaden the amount of work performed without per-step review.
User authorized continuous batch / driver-monitor automation | **Phase 4 → [Continuous Operation Mode](#continuous-operation-mode)**
Use continuous operation only after explicitly setting task boundaries, review checkpoints, and stop conditions.