generate-skilllisted

# Generate skill Turn a described need for a new procedure into a real `SKILL.md` — one that reads like it shipped with the framework: grounded in a named, current, cited standard for its domain, not generic advice dressed up as a procedure. ## When to use Whenever the user asks (from the Customize page, or directly in chat) to **add a skill** — "create a skill for security review grounded in OWASP", "I want a skill for accessibility audits", "add a skill for database migration reviews" — or when `propose-customizations` proposed a skill candidate the user picked. ## Method ### 1. Clarify before generating A one-line ask ("add a security skill") is under-specified. Use `.spectoflow/skills/clarify`'s reflex — one targeted question at a time, each with a recommended default — until you know: - **The exact procedure's scope.** "Security review" could mean a dozen different things (dependency vulnerabilities? authn/authz review? secrets scanning? infra hardening?) — narrow it before writing a method for the wrong one. - **Which capability it belongs to** — pick the closest match from `.spectoflow/capabilities.md`'s palette (security, quality, architecture, testing, operations, …); propose one, don't leave it open. - **Who runs it** — an existing agent whose capability matches, or does this need a new agent too (if so, this request also needs `generate-agent` — say so and sequence the two). ### 2. Identify the real domain standard — don't skip this, and don't fabric