nl-to-constraints

Transforms natural language requirements (user stories, verbal descriptions, business rules) into formal specifications and constraints. Use when converting informal requirements into structured, testable specifications with explicit constraints. Outputs in multiple formats including BDD-style Given-When-Then, JSON Schema, and structured plain text requirements documents.

Install with Tessl CLI

npx tessl i github:ArabelaTso/Skills-4-SE --skill nl-to-constraints

What are skills?

Review — 92%

Does it follow best practices?

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

70%

Payment API Formal Specification

JSON Schema specification with constraint extraction

Criteria

Without context

With context

REQ-NNN ID pattern

100%

CON-NNN ID pattern

100%

TEST-NNN ID pattern

100%

Requirement type enum

100%

Requirement priority enum

100%

Constraint category enum

100%

RFC 2119 severity

100%

Constraint entity field

100%

Formal expression

100%

Validation method

100%

Error message

100%

Acceptance criteria

100%

Traceability links

77%

100%

Without context: $0.4368 · 2m · 14 turns · 18 in / 9,242 out tokens

With context: $0.4685 · 1m 53s · 14 turns · 4,170 in / 8,165 out tokens

90%

Data Pipeline SLA Requirements Analysis

Ambiguity detection and flagging

Criteria

Without context

With context

Ambiguity flag marker

70%

80%

Requirement label per ambiguity

100%

Issue description

100%

Possible interpretations

40%

100%

Clarifying questions

100%

Default interpretation

60%

50%

Vague quantifier detection

100%

Missing edge case detection

100%

Undefined scope detection

100%

Unambiguous parts specified

88%

100%

Step 1 analysis artifacts

62%

Without context: $0.3253 · 2m 18s · 13 turns · 18 in / 6,685 out tokens

With context: $0.6885 · 3m 49s · 21 turns · 4,389 in / 10,971 out tokens

99%

33%

User Authentication System Test Coverage

BDD scenario generation and requirement classification

Criteria

Without context

With context

Gherkin Scenario keyword

100%

Given keyword

100%

When keyword

100%

Then keyword

100%

Requirement type classification

75%

87%

Requirement priority classification

100%

State constraint identified

100%

Authorization constraint identified

100%

Temporal constraint identified

100%

RFC 2119 severity used

100%

Implicit assumptions made explicit

100%

Negative scenario coverage

100%

Step 5 validation evidence

100%

Without context: $0.2820 · 1m 50s · 11 turns · 16 in / 5,157 out tokens

With context: $0.6895 · 3m 30s · 22 turns · 238 in / 10,692 out tokens

Evaluated: about 20 hours ago
Agent: Claude Code

Table of Contents

Payment API Formal Specification Data Pipeline SLA Requirements Analysis User Authentication System Test Coverage

Is this your skill?

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.