Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Options?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/greenfield-inc-options)
---
name: options
description: Use when the person asks what to do or for trade-offs, or more than one design is live. Waits for a pick. Never plans.
---
# Options
This is the only place alternatives are argued. If an implementer could still choose the architecture, this step was skipped.
## Rules
- One section per decision. Small decisions can be asked inline and recorded later in the plan cover sheet instead of getting a document.
- Two or three real options per decision, plus two that are always present: the **smallest version** (what ships if everything deferrable is deferred, and what the user loses) and **do nothing** (what stays wrong, observably).
- State each option's complexity-ladder rung from the standing rules, and give a reason for every rung above the lowest workable one.
- Give every option, including the smallest version and doing nothing, a short complexity statement as described in the template. Cover both the requirements and the implementation: the complexity added compared with today, the likely ways it breaks, and the ongoing maintenance or operating cost. Say which requirements drive that cost, what could be simplified or deferred, and what the user would lose. Back claims with repository evidence where you have it, label assumptions, and describe effort and risk in words rather than scores or probabilities.
- For a decision about an interface, first show how 4 to 6 comparable products handle it, with sources. Then make each option a mockup (`ui-mockup`) with its user journey: the happy path plus 2 to 4 edge cases. When the runtime shape differs between options, add an `architecture-diagram`.
- Recommend one option and say what the person must accept if they take it.
- A decision blocked on a missing fact becomes a spike or a question for `researcher`.
- Revise the document in place as the person learns. Record why options changed under "What we learned".
## Socrates
When the person says they are ready to pick, send the brief and this document to `socrates` once, with repository access. Relay its material questions. Record its verdict (pass, clarify, or rethink) against the revision it reviewed. Continue the same Socrates agent through follow-ups, two rounds at most. Socrates investigates facts and asks questions. The person settles product choices. Skip Socrates for small decisions.
## Output
An HTML page for the person, laid out as in [references/options-template.md](references/options-template.md) and rendered with the `page` house standard. Save it as `options.html` in the work's bundle. End with the status line and wait.
## Banned
- Implementation steps, file-level changes, work packages
- Picking on the person's behalf
- Starting the plan before there is an explicit pick