Use when writing a new requirement, defining a new feature, or when asked to implement behavior that has no requirement in specs/. Produces an EARS requirement with an FDD-style feature name, anchor Gherkin scenarios, and a stable REQ ID. Also use when an existing requirement must change.
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
This skill hasn't been evaluated yet
tessl scenario generatetessl eval runigouss/gitweb-rs
9ef2429
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.