propose-options

Validates proposed options against a seven-question governance checklist before presenting them to users.

5|9|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ajenchen/design-system --skill propose-options-ajenchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose-options
Source: https://github.com/ajenchen/design-system/tree/main/.agents/skills/propose-options
Command: npx skills add https://github.com/ajenchen/design-system --skill propose-options-ajenchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI assistant proposes options or recommendations without verifying the problem actually exists, users waste time reviewing invalid suggestions and lose trust. This Skill forces a mandatory self-check on every candidate option before it appears in a reply, filtering out unverified or redundant proposals. ## Core Features & Use Cases - Seven-Question Gate: Each option must pass checks for pre-verification via grep and spec reading, world-class benchmarks, internal design-system canonical alignment, single-source-of-truth enforcement, rule-of-three placement, downstream absorption, and full issue mapping. - Inline Evidence Tables: Outputs a structured markdown table showing pass/fail status per option with explicit reject reasons, so users can see the verification process. - Issue Mapping: For plan iterations, every user-raised issue is mapped to a step, marked informational, or explicitly dropped with a reason. - Use Case: Before replying with "Option A / B / C" for a design-system migration, run this gate to grep existing component usage, cite spec sections, and reject any option lacking file:line evidence. ## Quick Start Ask the assistant to propose options for a design-system change and require each option to pass the seven-question verification table with cited file and spec evidence before listing it.

Frequently Asked Questions about propose-options

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify options before proposing them to a user?

Run each candidate option through the seven-question gate: grep the codebase to confirm the problem exists, read the relevant spec, check internal canonical patterns, and cite file:line evidence. Options failing any check are rejected or labeled with the failure reason.

What is a propose-time gate in AI-assisted workflows?

A propose-time gate is a self-check the assistant runs before writing recommendations into a reply. It complements pre-write and post-edit hooks by catching invalid proposals at the moment options are generated, since chat replies have no hook coverage.

When should this option-validation skill not be invoked?

Skip it when the user has already explicitly chosen an action, when answering purely informational questions, or when applying a surgical bug fix with no option list. Emergency fixes bypass the full checklist but should still note the root cause.

How are rejected options handled in the output?

Rejected options are explicitly marked with their failure reasons in the inline results table rather than silently omitted. This transparency lets users see that each proposal passed principle checks before being listed.

What happens to user-raised issues during plan iterations?

Every issue the user raised must be mapped in a table to a step, marked as informational, folded into another step, or explicitly dropped with a reason. Silent drops are treated as failures.