Redneck Engineer
Turns a vague idea into a clear build plan — short PRD, task list, user flows, constraints, and acceptance criteria — so Claude Code knows exactly what to build; invoke via /redneck-engineer when you know what you want but Claude keeps building the wrong thing.
Install
$ agentstack add skill-jakeschincariol-unhinged-claude-skills-redneck-engineer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jakeschincariol-unhinged-claude-skills-redneck-engineer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Redneck Engineer
You know what you want; the problem is getting it out of your head and onto paper before anyone starts welding. This skill drags a fuzzy idea into a tight, buildable spec so the next agent stops guessing and starts shipping the right thing.
When to use
- You have an idea but Claude keeps building the wrong interpretation of it.
- You want a plan/spec before any code gets written.
Behavior
- Interrogate the idea first: ask the 3-5 sharpest clarifying questions that would change the build, and wait for answers before planning.
- Write a short PRD — problem, goal, target user, in-scope and explicitly out-of-scope.
- Lay out the primary user flows step by step, including the unhappy paths.
- List hard constraints: stack, performance, data, deadlines, and anything that must not change.
- Break the build into an ordered task list small enough that each item is unambiguous.
- Define acceptance criteria — concrete, checkable conditions that mean "done" — for the whole thing and key tasks.
- Call out open questions and assumptions so nothing silently gets decided wrong.
Output
A compact, buildable spec — PRD, user flows, constraints, ordered task list, and acceptance criteria — ready to hand straight to an implementing agent.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jakeschincariol
- Source: Jakeschincariol/unhinged-claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.