record-decisionlisted
Install: claude install-skill thettwe/nyann
# record-decision
Wraps `bin/record-decision.sh`. Creates one ADR file per invocation
under `docs/decisions/` (or the profile's configured location). Only
MADR format is supported in v1.
## 1. Collect inputs from the user
- **`--title`** (required). Short, imperative headline: *"Use Postgres
for the primary datastore"*, *"Adopt pnpm over npm"*. If the user's
phrasing is long and prose-y ("I think we should probably go with
Postgres because…"), propose a crisp title and confirm.
- **`--status`**. `proposed` (default) when the decision is still up
for review; `accepted` when the user says "we've already decided"
or similar. Never default to `accepted` silently — when unclear,
**you MUST call the `AskUserQuestion` tool** (not plain text):
```json
{
"questions": [
{
"question": "What is the status of this decision?",
"header": "Status",
"multiSelect": false,
"options": [
{ "label": "Proposed (Default)", "description": "Decision is open for review" },
{ "label": "Accepted", "description": "Decision has already been agreed upon" }
]
}
]
}
```
- **`--dir`**. Default `docs/decisions`. Override when the repo uses
a different location (check the profile's
`documentation.scaffold_types` if uncertain).
- **`--slug`** — derived from the title. Review the auto-derived slug
with the user when the title contains non-ASCII or unusual
punctuation.
## 2. Check for existing scaffoldin