Gsd Claw
Analysis
GSD Claw is a coherent instruction-only project workflow skill, with the main caution that it can guide the agent to edit project files, run verification commands, use sub-agents, and persist project planning notes.
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Task Types: - `type="auto"` — Agent executes autonomously ... After each task: ... Commit changes (if applicable)
The skill explicitly allows autonomous execution and commits during a development plan. This is expected for a spec-driven build workflow, but it gives the agent meaningful project-mutation authority.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
**Plans ARE prompts** — Executable instructions, not documents to interpret ... Document decisions in `{project}/.gsd/CONTEXT.md`The workflow stores project decisions and plans as persistent prompt-like files that the agent later treats as instructions. This is central to the skill, but users should keep those files accurate and free of secrets or untrusted edits.
For multi-task execution, spawn sub-agents: - Each sub-agent gets fresh 200k context
The skill may delegate work to sub-agents with project context. This is purpose-aligned, but it means task details may be shared across agent contexts.
