gsd-by-glittercowboy
v1.0.1Get Shit Done - Full project planning and execution workflow. Handles project initialization with deep context gathering, automated research, roadmap creation, phase planning, and execution with verification.
⭐ 0· 1.7k·8 current·8 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (project planning & execution) matches the delivered artifacts: many workflows for new-project, plan-phase, execute-phase, debug, design, discovery, etc. Required env vars/binaries/config paths are none, which is consistent with an instruction-only skill that operates over a project's .planning directory. Tools like WebSearch/WebFetch and git operations are reasonable for research and committing planning docs.
Instruction Scope
SKILL.md and workflow files instruct the agent to read/write project files under a .planning directory, run bash snippets, run git commits/tags, spawn subagents (sessions_spawn), and perform WebSearch/WebFetch for research. These actions are coherent with the stated purpose but are broad: they modify the repository (create/delete files, commit, tag), persist debug sessions, and perform network fetches. Users should understand it will perform repository-level changes and external searches if invoked.
Install Mechanism
Instruction-only skill with no install spec and no downloaded code. No archives, brew/npm installs, or external URL downloads are used. This is the lowest-risk install model.
Credentials
The skill declares no required environment variables, credentials, or privileged config paths. Workflows reference only local project files (e.g., .planning/*) and internal skill files. WebFetch/WebSearch usage implies network access but does not require user-provided secrets; this is proportionate to the research capabilities described.
Persistence & Privilege
always:false (normal). The skill instructs spawning persisted subagent sessions and writing persistent files under .planning (debug sessions, DESIGN-SYSTEM.md, DISCOVERY.md, etc.). Autonomous model invocation is allowed (platform default), so the skill could autonomously spawn subagents and perform repo edits when invoked. This is expected for an orchestrator skill but increases blast radius compared to read-only assistants.
Assessment
This skill appears internally consistent with a full project orchestration assistant, but it performs wide-ranging local file operations and git commits, spawns subagents, and can fetch external web content. Before installing or invoking: 1) back up your repository or run it in an isolated workspace; 2) review .planning/config.json (it controls whether docs are auto-committed) and set commit_docs=false if you want to avoid automatic git commits; 3) be prepared that the skill will create/move/delete files under .planning/, may remove REQUIREMENTS.md during milestone completion, and will spawn persistent debug sessions; 4) if you have sensitive data in the repo, avoid running WebFetch/WebSearch steps or provide only sanitized inputs. No credentials are requested by the skill itself.Like a lobster shell, security has layers — review code before you run it.
latestvk97cykvkdsfc52sqxd8e3b2m7s81313k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.