cige-test-authoringlisted

# CIGE: Agentic Test Case Authoring Use this skill when writing, reviewing, or refactoring AI agent test cases. It enforces the CIGE standard — a structured format that separates stable test intent from adaptive execution, enabling self-healing agentic tests. ## When to invoke - Authoring a new agentic test case from scratch - Reviewing an existing test for brittleness or missing structure - Designing test guardrails for a new agent workflow For a completed run — pass or fail — do not decide repairs here. Invoke `cige-failure-classification` first; it classifies the outcome and names which skill (if any) should act. --- ## The CIGE Format Every agentic test case must be expressed in this structure: ```json { "Context": { "system": "<app or service under test, version if relevant>", "environment": "<staging | dev | ephemeral | ...>", "tools": ["<tool 1>", "<tool 2>"], "preconditions": ["<seed data>", "<auth state>", "<feature flags>"], "specRef": "<path or URL to the BRD / product spec that defines expected behavior>", "buildRef": "<pointer to the build/version under test and its release documentation — changelog, release notes, or build manifest>" }, "Intent": "<single outcome-based objective — what success looks like>", "Guardrails": [ "<constraint the agent must never violate>", "<scope boundary or irreversibility limit>" ], "Execution": [ "<adaptive step 1 — guidance, not script>", "<adaptive step 2>", "<verif