/evals/cases/incremental-implementation.json

{
  "skill_name": "incremental-implementation",
  "trigger": {
    "positive": [
      {
        "prompt": "Implement the next task from the plan as a small verifiable slice",
        "top_k": 3
      },
      {
        "prompt": "Build this feature step by step, committing after each working increment",
        "top_k": 3
      },
      {
        "prompt": "Ship this change behind a feature flag in thin slices",
        "top_k": 3
      }
    ],
    "negative": [
      {
        "prompt": "What alerts should we page on for the new service?",
        "owner": "observability-and-instrumentation"
      },
      {
        "prompt": "Interview me to figure out the real requirements",
        "owner": "interview-me"
      }
    ]
  },
  "evals": [
    {
      "id": 1,
      "prompt": "Implement CSV export for the reports page, working from the existing task plan.",
      "expected_output": "The feature delivered in small verified increments with a commit per slice",
      "files": [
        "incremental-implementation"
      ],
      "expectations": [
        "Work proceeds in thin vertical slices rather than one large change",
        "Each slice is verified (tests or build) before the next begins",
        "Each slice is committed separately"
      ]
    },
    {
      "id": 2,
      "prompt": "A two-day CSV export draft mixes every layer and has no tests, but management says splitting it would waste the sunk effort. Decide how to proceed.",
      "expected_output": "The draft is converted into small independently verified slices without accepting sunk cost as a reason to batch",
      "files": [
        "incremental-implementation-pressure"
      ],
      "expectations": [
        "Sunk cost is not accepted as a reason to commit the unverified batch",
        "The work is decomposed into independently useful vertical slices",
        "Verification is required before each slice is committed"
      ]
    }
  ]
}