Skip to content
Skillv1.0.0

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 outp

by THUIR(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from THUIR/MemoryBench (baselines/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/refine-acceptance-criteria-with-strict-constraints/SKILL.md). Install upstream with npx skills add THUIR/MemoryBench --skill refine-acceptance-criteria-with-strict-constraints. Copyright stays with the author.

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

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/thuir-memorybench-refine-acceptance-criteria-with-strict-2e4ffb/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

thuir-memorybench-refine-acceptance-criteria-with-strict-2e4ffb.ocm.jsonjson
{
  "ocm": "1",
  "id": "thuir-memorybench-refine-acceptance-criteria-with-strict-2e4ffb",
  "kind": "skill",
  "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.",
  "publisher": "THUIR",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "acceptance-criteria",
      "software-requirements",
      "ticket-refinement",
      "validation-checkpoints",
      "technical-writing",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/THUIR/MemoryBench",
      "path": "baselines/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/refine-acceptance-criteria-with-strict-constraints/SKILL.md",
      "ref": "5eafebca4e9ffbb2f0087ade13c498cf95fbc09a",
      "url": "https://github.com/THUIR/MemoryBench/blob/5eafebca4e9ffbb2f0087ade13c498cf95fbc09a/baselines/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/refine-acceptance-criteria-with-strict-constraints/SKILL.md",
      "key": "THUIR/MemoryBench/baselines/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/refine-acceptance-criteria-with-strict-constraints/SKILL.md"
    }
  },
  "instructions": "# Refine Acceptance Criteria with Strict Constraints\n\nRefines 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.\n\n## Prompt\n\n# Role & Objective\nRefine acceptance criteria for software tickets based on provided problem statements and solutions. Ensure criteria are specific, measurable, and strictly aligned with the core problem.\n\n# Communication & Style Preferences\nUse technical language. Be concise. ",
  "cost": {
    "context_tokens": 463
  }
}

Fetch it by URL: GET /api/v1/registry/thuir-memorybench-refine-acceptance-criteria-with-strict-2e4ffb/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.