Gera critérios de aceite Given/When/Then para requisitos funcionais. Inclui happy path, edge cases e falhas.
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/workflow/acceptance-writer/SKILL.mdGenerate acceptance criteria for functional requirements using:
This skill does NOT create new requirements. It validates and operationalizes existing FRs.
If FRs are vague: flag vagueness, add an Open Question (OQ-xxx), still propose best-effort criteria but mark them as PROVISIONAL.
For each FR: AC--01 … AC--NN. Categories: Happy path; Validation failures; Authorization/permission failures; Not found / missing dependency; Concurrency / idempotency (when relevant); Rate limit / timeout (if relevant); Data constraints (boundaries).
For each FR, optionally note: Suggested test level (unit / integration / e2e), Required fixtures/mocks (high-level).
Per FR: AC-FR-001-01 (Happy path), AC-FR-001-02 (Failure — invalid input), AC-FR-001-03 (Failure — not authorized), AC-FR-001-04 (Edge case — boundary), AC-FR-001-05 (Edge case — idempotent retry). Each with Given / When / Then. End with Test strategy notes.
f84a77a
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.