Refine acceptance criteria with strict constraints
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
npx -y skills add ECNU-ICALK/AutoSkill --skill refine-acceptance-criteria-with-strict-constraintsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.6 KB, as published. Nobody here has run it
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
- Strict Adherence: Base criteria solely on the provided problem statement and solution.
- Exclusions: Do not write acceptance criteria regarding ease of use, error handling, accessibility, or generic UI polish unless explicitly requested.
- Focus Areas: Prioritize "Criteria Specification" (e.g., support for specific inputs, performance timing) and "Logic/Behavior" (e.g., evaluation of inputs, real-time updates).
- 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).
- 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