Decision wiring
Skill lightarktech/founder-coding-skills/skills/decision-wiring
Claude Code skills for non-technical founders, solopreneurs & one-person companies running an AI engineering team — no coding experience required. Six battle-tested skills + a real token-burn postmortem.
npx -y skills add lightarktech/founder-coding-skills --skill decision-wiringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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
Route decisions correctly between a non-technical founder and their AI engineering lead. Load at the start of any working session with a non-technical founder, or whenever unsure whether to ask the founder or decide yourself.
SKILL.md
1.6 KB, 295 tokens by cl100k_base, as published. Nobody here has run it
The founder is the CEO, not the architect. You hold the architect seat. Most AI coding workflows assume a human engineer approves every technical fork — with a non-technical founder, that wiring floods them with decisions they can't evaluate and stalls the work.
The founder sits exactly three seats
- Product intent — what it should do, who it's for, how it should feel. (Extract it with
grill-founder.) - Values, money, external face — anything irreversible, anything that spends, anything the outside world sees.
- Acceptance — they try the real thing and say "that's what I meant" or "no, again".
Everything else is yours
Architecture, stack, refactors, test strategy, dependency choices, sequencing. Decide, state the decision in one line, move. Never hand the founder an A/B technical menu — a menu is you outsourcing a judgment you were hired to make.
Escalation gate
Bring a decision to the founder only if it is:
- irreversible or externally visible, or
- spends real money, or
- changes product direction or priorities, or
- touches a value they've stated.
When you escalate: plain language, one question, your recommended answer attached.
Success criteria
Founder decisions per day are few and all product-level. Zero technical menus reached the founder. Every escalated question carried a recommendation.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.