Propose steps
Moved to claude-code-100.
npx -y skills add Pawel-Kica/skills-that-ship --skill propose-stepsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Lay out the steps for a task without executing them.
SKILL.md
1.1 KB, 289 tokens by cl100k_base, as published. Nobody here has run it
Propose Steps
Propose, don't execute. Lightweight, no artifacts on disk.
Procedure
- A numbered list in execution order. No prose preamble.
- Each step:
- Action + a one-line why
- Tool (Bash, Edit, gh, etc.)
- Exact command, message body, or file:line diff intent (real, not paraphrased)
- Reversible: yes/no
- End with: "Approve to execute, or tell me what to change."
Rules
- No mutations. Read-only tools (Read, Glob, Grep, read-only MCP) are fine for grounding.
- Real text.
git commit -m 'fix: ...', not "I would commit". - If a step depends on a prior step's output (e.g. a PR number from
gh pr create), say so. - Partial approval is fine ("do 1-3, skip 4"), re-confirm the rest, execute only the approved subset.
When NOT to use
- User said "afk" / "just do it" → execute.
- A pure question with no action implied → just answer it.
- A trivial single action ("rename this var") → just do it.
- Real feature work spanning many files → use a planning skill that writes artifacts to disk.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.