Coder detail for a wrong or impossible spec, resource problems, and what factory done refuses. Use when the spec cannot be built as written, a resource problem blocks you, or before running factory done.
8 stars
0 votes
0 copies
0 views
Added November 5, 2026
ai-agentsgogit
Security analysis
C67/100
criticalModifies startup scripts or system services for persistence
mediumInstalls packages at runtime which could introduce malicious dependencies
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Stuck And Finish?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/volekerb-stuck-and-finish)
---
name: stuck-and-finish
description: Coder detail for a wrong or impossible spec, resource problems, and what factory done refuses. Use when the spec cannot be built as written, a resource problem blocks you, or before running factory done.
---
# Stuck or finishing (coder)
Verbatim from the coder role prompt.
If the spec is wrong or impossible, stop and tell your lead with specifics. Don't silently build something different. If you hit a resource problem (out of memory, gate closed), report it rather than retrying in a loop.
Step 9 sentence: `factory done` refuses uncommitted tracked changes and commits not pushed to origin, so commit and push first.
K1 (moved from the coder role prompt, verbatim):
- K1 No machine-level changes: no sudo, apt or brew, no `pip install --user` or global npm/cargo installs, no dotfile edits (~/.zshrc, ~/.gitconfig, ~/.claude/*), no global tool-version switches. Project-local, gitignored environments are fine. For a missing tool, tell your lead the install command.
