diff --git a/autoplan/SKILL.md b/autoplan/SKILL.md index 5346f1d43..f8ca34a42 100644 --- a/autoplan/SKILL.md +++ b/autoplan/SKILL.md @@ -399,6 +399,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -450,6 +452,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/canary/SKILL.md b/canary/SKILL.md index 08d4d7369..1922a0723 100644 --- a/canary/SKILL.md +++ b/canary/SKILL.md @@ -391,6 +391,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -442,6 +444,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/codex/SKILL.md b/codex/SKILL.md index 33228ff9b..02c9daefd 100644 --- a/codex/SKILL.md +++ b/codex/SKILL.md @@ -394,6 +394,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -445,6 +447,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/context-restore/SKILL.md b/context-restore/SKILL.md index 59b40e82c..ea8acef61 100644 --- a/context-restore/SKILL.md +++ b/context-restore/SKILL.md @@ -395,6 +395,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -446,6 +448,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/context-save/SKILL.md b/context-save/SKILL.md index a1eb24595..dc95fcb80 100644 --- a/context-save/SKILL.md +++ b/context-save/SKILL.md @@ -394,6 +394,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -445,6 +447,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/cso/SKILL.md b/cso/SKILL.md index d4f84ab34..ad045defa 100644 --- a/cso/SKILL.md +++ b/cso/SKILL.md @@ -397,6 +397,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -448,6 +450,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/design-consultation/SKILL.md b/design-consultation/SKILL.md index e6d761dd9..dffab6c8b 100644 --- a/design-consultation/SKILL.md +++ b/design-consultation/SKILL.md @@ -417,6 +417,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -468,6 +470,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/design-html/SKILL.md b/design-html/SKILL.md index a480bd62c..bd6a07cc1 100644 --- a/design-html/SKILL.md +++ b/design-html/SKILL.md @@ -398,6 +398,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -449,6 +451,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/design-review/SKILL.md b/design-review/SKILL.md index b71a441cb..285f32f2b 100644 --- a/design-review/SKILL.md +++ b/design-review/SKILL.md @@ -395,6 +395,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -446,6 +448,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/design-shotgun/SKILL.md b/design-shotgun/SKILL.md index 3386d18fa..cdb598de8 100644 --- a/design-shotgun/SKILL.md +++ b/design-shotgun/SKILL.md @@ -412,6 +412,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -463,6 +465,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/devex-review/SKILL.md b/devex-review/SKILL.md index 7ef324b3e..70b6c16a4 100644 --- a/devex-review/SKILL.md +++ b/devex-review/SKILL.md @@ -397,6 +397,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -448,6 +450,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/diagram/SKILL.md b/diagram/SKILL.md index 9e5a41066..bf57f3937 100644 --- a/diagram/SKILL.md +++ b/diagram/SKILL.md @@ -392,6 +392,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -443,6 +445,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/document-generate/SKILL.md b/document-generate/SKILL.md index 30846fc4d..09f3646cc 100644 --- a/document-generate/SKILL.md +++ b/document-generate/SKILL.md @@ -397,6 +397,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -448,6 +450,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/document-release/SKILL.md b/document-release/SKILL.md index b95873625..2debd544f 100644 --- a/document-release/SKILL.md +++ b/document-release/SKILL.md @@ -395,6 +395,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -446,6 +448,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/health/SKILL.md b/health/SKILL.md index e68199dec..50f03ce57 100644 --- a/health/SKILL.md +++ b/health/SKILL.md @@ -393,6 +393,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -444,6 +446,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/investigate/SKILL.md b/investigate/SKILL.md index 559211127..ecad1582d 100644 --- a/investigate/SKILL.md +++ b/investigate/SKILL.md @@ -432,6 +432,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -483,6 +485,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/ios-clean/SKILL.md b/ios-clean/SKILL.md index 127649646..085239309 100644 --- a/ios-clean/SKILL.md +++ b/ios-clean/SKILL.md @@ -395,6 +395,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -446,6 +448,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/ios-design-review/SKILL.md b/ios-design-review/SKILL.md index 904da7589..3b9f24833 100644 --- a/ios-design-review/SKILL.md +++ b/ios-design-review/SKILL.md @@ -397,6 +397,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -448,6 +450,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/ios-fix/SKILL.md b/ios-fix/SKILL.md index 3ddae1ac0..92db5f4d6 100644 --- a/ios-fix/SKILL.md +++ b/ios-fix/SKILL.md @@ -398,6 +398,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -449,6 +451,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/ios-qa/SKILL.md b/ios-qa/SKILL.md index a5d4575d4..518cec0bc 100644 --- a/ios-qa/SKILL.md +++ b/ios-qa/SKILL.md @@ -401,6 +401,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -452,6 +454,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/ios-sync/SKILL.md b/ios-sync/SKILL.md index 2f689c4d6..3ee94b72e 100644 --- a/ios-sync/SKILL.md +++ b/ios-sync/SKILL.md @@ -395,6 +395,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -446,6 +448,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/land-and-deploy/SKILL.md b/land-and-deploy/SKILL.md index 54ebf52c0..09f9584d5 100644 --- a/land-and-deploy/SKILL.md +++ b/land-and-deploy/SKILL.md @@ -390,6 +390,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -441,6 +443,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/landing-report/SKILL.md b/landing-report/SKILL.md index 8f7e6e210..3289f8a41 100644 --- a/landing-report/SKILL.md +++ b/landing-report/SKILL.md @@ -391,6 +391,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -442,6 +444,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/learn/SKILL.md b/learn/SKILL.md index a0c6ae053..cc5f030cf 100644 --- a/learn/SKILL.md +++ b/learn/SKILL.md @@ -393,6 +393,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -444,6 +446,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/office-hours/SKILL.md b/office-hours/SKILL.md index 0f78588d6..3d3c7281d 100644 --- a/office-hours/SKILL.md +++ b/office-hours/SKILL.md @@ -428,6 +428,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -479,6 +481,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/open-gstack-browser/SKILL.md b/open-gstack-browser/SKILL.md index 28fb1ddb2..7fa816132 100644 --- a/open-gstack-browser/SKILL.md +++ b/open-gstack-browser/SKILL.md @@ -390,6 +390,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -441,6 +443,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/pair-agent/SKILL.md b/pair-agent/SKILL.md index eed9d171a..e024744f6 100644 --- a/pair-agent/SKILL.md +++ b/pair-agent/SKILL.md @@ -392,6 +392,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -443,6 +445,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/plan-ceo-review/SKILL.md b/plan-ceo-review/SKILL.md index f325e2f1c..241a9de06 100644 --- a/plan-ceo-review/SKILL.md +++ b/plan-ceo-review/SKILL.md @@ -422,6 +422,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -473,6 +475,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/plan-design-review/SKILL.md b/plan-design-review/SKILL.md index e81f7f12a..c2a8ad692 100644 --- a/plan-design-review/SKILL.md +++ b/plan-design-review/SKILL.md @@ -394,6 +394,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -445,6 +447,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/plan-devex-review/SKILL.md b/plan-devex-review/SKILL.md index 20a32da8b..951969691 100644 --- a/plan-devex-review/SKILL.md +++ b/plan-devex-review/SKILL.md @@ -400,6 +400,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -451,6 +453,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/plan-eng-review/SKILL.md b/plan-eng-review/SKILL.md index fc1719fac..4754ee908 100644 --- a/plan-eng-review/SKILL.md +++ b/plan-eng-review/SKILL.md @@ -398,6 +398,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -449,6 +451,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/plan-tune/SKILL.md b/plan-tune/SKILL.md index f49b66fac..ccdc0fca6 100644 --- a/plan-tune/SKILL.md +++ b/plan-tune/SKILL.md @@ -403,6 +403,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -454,6 +456,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/pr-prep/SKILL.md b/pr-prep/SKILL.md index 4151ba72f..a10ae9476 100644 --- a/pr-prep/SKILL.md +++ b/pr-prep/SKILL.md @@ -400,6 +400,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -451,6 +453,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/qa-only/SKILL.md b/qa-only/SKILL.md index 801a935c0..aac180ace 100644 --- a/qa-only/SKILL.md +++ b/qa-only/SKILL.md @@ -393,6 +393,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -444,6 +446,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/qa/SKILL.md b/qa/SKILL.md index 8aa7d9cc3..21a50f9f3 100644 --- a/qa/SKILL.md +++ b/qa/SKILL.md @@ -399,6 +399,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -450,6 +452,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/retro/SKILL.md b/retro/SKILL.md index 0a35a36cb..ae5096b11 100644 --- a/retro/SKILL.md +++ b/retro/SKILL.md @@ -410,6 +410,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -461,6 +463,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/review/SKILL.md b/review/SKILL.md index 5f26e2e42..d95502756 100644 --- a/review/SKILL.md +++ b/review/SKILL.md @@ -395,6 +395,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -446,6 +448,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/scrape/SKILL.md b/scrape/SKILL.md index dc965ec5f..ef0e2a0eb 100644 --- a/scrape/SKILL.md +++ b/scrape/SKILL.md @@ -391,6 +391,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -442,6 +444,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/scripts/resolvers/preamble/generate-ask-user-format.ts b/scripts/resolvers/preamble/generate-ask-user-format.ts index 533c002c0..982e3d4ea 100644 --- a/scripts/resolvers/preamble/generate-ask-user-format.ts +++ b/scripts/resolvers/preamble/generate-ask-user-format.ts @@ -64,6 +64,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use \`Completeness: N/10\` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: \`Note: options differ in kind, not coverage — no completeness score.\` +Single-select is the DEFAULT — options are mutually exclusive. Set \`multiSelect: true\` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score \`Completeness: =X/10\` per atom. Bundles or combinations of the same underlying items (\`E1+E3\`, \`All three\`, \`E1 only\`, \`Defer all\`) are mutually exclusive by construction — \`multiSelect: false\`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: \`✅ No cons — this is a hard-stop choice\`. Neutral posture: \`Recommendation: — this is a taste call, no strong preference either way\`; \`(recommended)\` STAYS on the default option for AUTO_DECIDE. @@ -115,6 +117,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] \`multiSelect: false\` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/setup-deploy/SKILL.md b/setup-deploy/SKILL.md index 3465dc564..1f43cc400 100644 --- a/setup-deploy/SKILL.md +++ b/setup-deploy/SKILL.md @@ -394,6 +394,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -445,6 +447,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/setup-gbrain/SKILL.md b/setup-gbrain/SKILL.md index 89c2ffbc3..b88d9ba27 100644 --- a/setup-gbrain/SKILL.md +++ b/setup-gbrain/SKILL.md @@ -393,6 +393,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -444,6 +446,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/ship/SKILL.md b/ship/SKILL.md index 53ad7060b..bdaf55383 100644 --- a/ship/SKILL.md +++ b/ship/SKILL.md @@ -395,6 +395,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -446,6 +448,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/skillify/SKILL.md b/skillify/SKILL.md index 7cb434d0c..748b12def 100644 --- a/skillify/SKILL.md +++ b/skillify/SKILL.md @@ -391,6 +391,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -442,6 +444,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/spec/SKILL.md b/spec/SKILL.md index 0894e98d1..ec9f91980 100644 --- a/spec/SKILL.md +++ b/spec/SKILL.md @@ -392,6 +392,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -443,6 +445,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) @@ -1462,6 +1465,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -1513,6 +1518,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC) diff --git a/sync-gbrain/SKILL.md b/sync-gbrain/SKILL.md index bfaf291d2..9b8717113 100644 --- a/sync-gbrain/SKILL.md +++ b/sync-gbrain/SKILL.md @@ -393,6 +393,8 @@ ELI10 is always present, in plain English, not function names. Recommendation is Completeness: use `Completeness: N/10` only when options differ in coverage. 10 = complete, 7 = happy path, 3 = shortcut. If options differ in kind, write: `Note: options differ in kind, not coverage — no completeness score.` +Single-select is the DEFAULT — options are mutually exclusive. Set `multiSelect: true` only when every option is an independently-selectable atom whose pro/con/effort stands alone; then score `Completeness: =X/10` per atom. Bundles or combinations of the same underlying items (`E1+E3`, `All three`, `E1 only`, `Defer all`) are mutually exclusive by construction — `multiSelect: false`, score per option LETTER, and never write "Multi-select" into the question text. Tell: a defer/none option or a do-everything option in the list proves the question is single-select. With 5+ independent atoms use the split chain below, not multiSelect. + Pros / cons: use ✅ and ❌. Minimum 2 pros and 1 con per option when the choice is real; Minimum 40 characters per bullet. Hard-stop escape for one-way/destructive confirmations: `✅ No cons — this is a hard-stop choice`. Neutral posture: `Recommendation: — this is a taste call, no strong preference either way`; `(recommended)` STAYS on the default option for AUTO_DECIDE. @@ -444,6 +446,7 @@ Before calling AskUserQuestion, verify: - [ ] ELI10 paragraph present (stakes line too) - [ ] Recommendation line present with concrete reason - [ ] Completeness scored (coverage) OR kind-note present (kind) +- [ ] `multiSelect: false` unless every option is an independently-selectable atom (bundles/combinations ⇒ single-select) - [ ] Every option has ≥2 ✅ and ≥1 ❌, each ≥40 chars (or hard-stop escape) - [ ] (recommended) label on one option (even for neutral-posture) - [ ] Dual-scale effort labels on effort-bearing options (human / CC)