KunanonJ/superstacks / plugins/superstacks/skills/owner-decisions
owner-decisions
VerifiedUse when about to merge, mark ready, close a ticket, force push, deploy, change a rule, or ask the owner a question. Reads authority from the owner's decision record, or starts one.
Owner decisions
Authority is what the owner's recorded decisions say. safety-overrides still win, and no record can lift a one-way door past a human plus interrogate.
1. Find the record
Take the first that exists. Never invent one silently.
- A project decision skill: a skill in the project's skills folder whose name or description is about the owner's or founder's decisions.
- A ledger file:
DECISIONS.mdat the repo root, or the path the project's agent instructions name. - Decisions on the tracker: the ticket itself and any issue the project names as its decision log.
Done when you can name the record you are using, or state that none exists.
2. Read before asking
Search the record for the question first. A question the record answers is not asked. When acting on a recorded decision, quote it: the owner's words, the date, where it is recorded.
3. Record before acting
Write a new decision to the record first, then act. An entry holds:
- the question as put, with its options
- the owner's exact words, quoted
- the option those words select
- the date (ISO)
- what the decision does not cover
Reading short answers:
- A bare "yes" or "follow your recommendation" selects every item that had exactly one recommendation, and nothing else.
- A yes to a question with several options and no recommendation selects nothing. Ask again.
- An approval given on a statement that turns out to be false is void. Say so, do not act, and ask again with the corrected facts.
4. Authority comes from the record
Authorities: merge, ready, close, force-push, deploy (and stack rebases, rule changes). Each is what the latest recorded decision says, within its scope and exceptions.
- With no recorded decision the default applies: drafts only, a human merges, no force push, no deploy.
- A decision never widens by analogy. "May merge its own PR after a passing review" does not cover a locked path, a one-way door, or a deploy.
- A ledger can be queried:
python <this-skill>/scripts/authority.py DECISIONS.md mergeprints the standing rule orDEFAULT: human.
5. No record yet
Create DECISIONS.md from templates/DECISIONS.md only when the owner asks for a record or answers the first decision question. Say that you created it and where. Validate it with python <this-skill>/scripts/check_decisions.py DECISIONS.md until it prints nothing.
6. Learn
When the ledger holds five or more decisions of the same kind, propose a standing rule that would have answered them. Do not apply it. Show a short table:
| Proposed rule | Scope | Exceptions | Decisions it rests on |
|---|
The owner's yes becomes a recorded standing rule with its source entry. One decision never becomes a rule.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |