vitya
82f82a2036
- mapping.yaml: 7 pending → auto (setup-tasks, using-tasks, setup-wiki, using-wiki, using-projects-meta, using-context7, project-bootstrap, recommend-dont-menu). pending count now 0. - dist-hermes/ populated: software-development: project-bootstrap (+ assets) productivity: recommend-dont-menu, setup-tasks, using-tasks research: setup-wiki, using-wiki mcp: using-context7, using-projects-meta - active-platform replace-rule verified: Windows+PowerShell → Linux+bash in body SKILL.md (frontmatter description unchanged by design). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
33 lines
858 B
Markdown
33 lines
858 B
Markdown
# recommend-dont-menu
|
|
|
|
One recommendation, not a menu. When the user asks "what should we do?", give your best choice with reasoning and trade-offs — don't enumerate A/B/C/D options.
|
|
|
|
## What it does
|
|
|
|
Overrides the `superpowers:brainstorming` default of presenting multiple options. Instead, respond with:
|
|
|
|
```
|
|
Я рекомендую X, потому что Y₁, Y₂. Trade-off: Z. Возражения?
|
|
```
|
|
|
|
Only mention alternatives when they're genuinely competitive or carry an important trade-off.
|
|
|
|
## When to use
|
|
|
|
During design discussions, architecture reviews, brainstorming, or any "what should we do" question.
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
bash scripts/install.sh recommend-dont-menu
|
|
```
|
|
|
|
## Trigger line
|
|
|
|
Add to `CLAUDE.md`:
|
|
```
|
|
prefer single recommendations
|
|
```
|
|
|
|
Or use `project-bootstrap` (v1.9.0+) which includes this trigger in its template.
|