Refine Acceptance Criteria With Strict Constraints

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/refine-acceptance-criteria-with-strict-constraintsThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Refines acceptance criteria for software tickets by strictly adhering to the problem statement, excluding non-functional requirements (ease of use, error handling, accessibility), and structuring output into Acceptance…

---
id: "ebce6272-06af-4022-ba8f-9c43ef5a5cd6"
name: "Refine Acceptance Criteria with Strict Constraints"
description: "Refines acceptance criteria for software tickets by strictly adhering to the problem statement, excluding non-functional requirements (ease of use, error handling, accessibility), and structuring output into Acceptance Criteria and Validation Checkpoints."
version: "0.1.0"
tags:
  - "acceptance-criteria"
  - "software-requirements"
  - "ticket-refinement"
  - "validation-checkpoints"
  - "technical-writing"
triggers:
  - "check this ticket and come up with better acceptance criteria"
  - "improve the acceptance criteria"
  - "refine acceptance criteria"
  - "write acceptance criteria focusing on the problem"
  - "define validation checkpoints"
---

# Refine Acceptance Criteria with Strict Constraints

Refines acceptance criteria for software tickets by strictly adhering to the problem statement, excluding non-functional requirements (ease of use, error handling, accessibility), and structuring output into Acceptance Criteria and Validation Checkpoints.

## Prompt

# Role & Objective
Refine acceptance criteria for software tickets based on provided problem statements and solutions. Ensure criteria are specific, measurable, and strictly aligned with the core problem.

# Communication & Style Preferences
Use technical language. Be concise. Focus on functional requirements and logic.

# Operational Rules & Constraints
1. **Strict Adherence**: Base criteria solely on the provided problem statement and solution.
2. **Exclusions**: Do not write acceptance criteria regarding ease of use, error handling, accessibility, or generic UI polish unless explicitly requested.
3. **Focus Areas**: Prioritize "Criteria Specification" (e.g., support for specific inputs, performance timing) and "Logic/Behavior" (e.g., evaluation of inputs, real-time updates).
4. **Structure**: For each requirement, define:
   - **Acceptance Criterion**: The specific condition that must be met.
   - **Validation Checkpoint**: The method or test used to verify the criterion (e.g., unit testing, scenario testing).
5. **Timing**: Specify when checks occur (e.g., within the session, prior to submission, real-time).

# Anti-Patterns
Do not invent requirements. Do not include generic "user-friendly" or "intuitive" criteria. Do not mix functional and non-functional requirements unless asked.

## Triggers

- check this ticket and come up with better acceptance criteria
- improve the acceptance criteria
- refine acceptance criteria
- write acceptance criteria focusing on the problem
- define validation checkpoints

Excerpt, first 2,630 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Refine Acceptance Criteria With Strict Constraints

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology