@givolt/i3-composer-agent 2.2.0 → 2.2.2

package/evals/cases/i3-code-simplification.json

@@ -0,0 +1,45 @@
+{
+  "skill_name": "i3-code-simplification",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "This function works but it is way too clever, simplify it without changing behavior",
+        "top_k": 3
+      },
+      {
+        "prompt": "Reduce the complexity of this module so juniors can maintain it",
+        "top_k": 3
+      },
+      {
+        "prompt": "Clean up this working code, it has grown hard to follow",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Add a feature flag system to the app",
+        "owner": "i3-incremental-implementation"
+      },
+      {
+        "prompt": "Diagnose why the build broke overnight",
+        "owner": "i3-debugging-and-error-recovery"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Simplify the provided 80-line function that parses config files, preserving exact behavior.",
+      "expected_output": "A simpler implementation with identical behavior and a summary of what was removed and why",
+      "files": [
+        "i3-code-simplification"
+      ],
+      "expectations": [
+        "Behavior is preserved (tests unchanged and passing, or equivalence argued concretely)",
+        "Complexity is reduced rather than relocated",
+        "The response explains what was removed and why it was safe",
+        "No new features are added during the simplification"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-constraint-driven-development.json

@@ -0,0 +1,79 @@
+{
+  "skill_name": "i3-constraint-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "Set up quality constraints for this project — I want to define our bar before the agent writes more code",
+        "top_k": 3
+      },
+      {
+        "prompt": "We have no written standards. Ask me what I care about and write it down with sane defaults",
+        "top_k": 3
+      },
+      {
+        "prompt": "The agent keeps adding @ts-ignore and skipping tests to get green. How do I stop that?",
+        "top_k": 3
+      },
+      {
+        "prompt": "What coverage threshold should we enforce, and where should it run so it doesn't slow us down?",
+        "top_k": 3
+      },
+      {
+        "prompt": "I care about accessibility and web performance — set those up as enforced constraints",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Review this pull request across correctness and security",
+        "owner": "i3-code-review-and-quality"
+      },
+      {
+        "prompt": "Add a deploy stage to our pipeline with a manual approval gate",
+        "owner": "i3-ci-cd-and-automation"
+      },
+      {
+        "prompt": "Write a failing test for this bug before we fix it",
+        "owner": "i3-test-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "kind": "dialogue",
+      "prompt": "Set up constraints for this repo. I don't really know what numbers to pick.",
+      "expected_output": "A short interview with defaults offered, followed by a CONSTRAINTS.md the user can explain",
+      "expectations": [
+        "The agent inspects the repo for stack, test runner, and existing linters before asking anything",
+        "No more than four questions are asked, and each one carries a usable default",
+        "When the user has no target number, the agent proposes recording today's value and holding it rather than inventing a threshold",
+        "The resulting constraints say where each check runs, keeping fast checks in the edit loop and slow checks later",
+        "Every number written down is accompanied by a reason"
+      ]
+    },
+    {
+      "id": 2,
+      "kind": "dialogue",
+      "prompt": "Our coverage is 62% and I want to enforce 85% starting today.",
+      "expected_output": "Pushback on setting an unmeetable budget, with the ratchet alternative offered",
+      "expectations": [
+        "The agent points out that a threshold the codebase fails today produces a permanently red build",
+        "It offers to record 62% and require that it not fall, as an adoptable alternative",
+        "It does not silently accept 85% without noting the consequence"
+      ]
+    },
+    {
+      "id": 3,
+      "kind": "dialogue",
+      "prompt": "Accessibility matters to us. Add it as a constraint.",
+      "expected_output": "A working accessibility check, not just a threshold written down",
+      "expectations": [
+        "The agent names axe-core and gives the install and run commands rather than only stating a violation threshold",
+        "It notes that axe needs a running URL and asks for one, or drops the dimension if the project has no URL to hit",
+        "The command that produces the verdict is recorded alongside the rule in CONSTRAINTS.md",
+        "The check is placed at the preview-deploy stage rather than in the per-edit loop"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-context-engineering.json

@@ -0,0 +1,44 @@
+{
+  "skill_name": "i3-context-engineering",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "What context should I load into the agent before starting this refactor?",
+        "top_k": 3
+      },
+      {
+        "prompt": "The model's output quality dropped mid-session, how do I fix its context?",
+        "top_k": 3
+      },
+      {
+        "prompt": "Set up rules files and context packing for my repository",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Write unit tests for the date parser",
+        "owner": "i3-test-driven-development"
+      },
+      {
+        "prompt": "Harden this endpoint against SQL injection",
+        "owner": "i3-security-and-hardening"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "An agent session has degraded: responses are generic and it keeps forgetting project conventions. Fix the context setup.",
+      "expected_output": "A diagnosis of the context problem and a concrete loading strategy (rules files, packing, task-scoped context)",
+      "files": [
+        "i3-context-engineering"
+      ],
+      "expectations": [
+        "The response diagnoses probable context causes rather than blaming the model generally",
+        "A specific context-loading plan is produced (what to load, when, and why)",
+        "Context is scoped to the task instead of loading everything"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-debugging-and-error-recovery.json

@@ -0,0 +1,58 @@
+{
+  "skill_name": "i3-debugging-and-error-recovery",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "The app crashes with a TypeError when I click save, help me find the root cause",
+        "top_k": 3
+      },
+      {
+        "prompt": "The API is throwing intermittent 500 errors in production, help me find the root cause",
+        "top_k": 3
+      },
+      {
+        "prompt": "This test passed yesterday and fails today, figure out what broke",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Write the API documentation for the orders service",
+        "owner": "i3-documentation-and-adrs"
+      },
+      {
+        "prompt": "Simplify this working function for readability",
+        "owner": "i3-code-simplification"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "A test that passed yesterday now fails with an off-by-one error in pagination. Find and fix the root cause.",
+      "expected_output": "A reproduced failure, an identified root cause, a minimal fix, and a guard against regression",
+      "files": [
+        "i3-debugging-and-error-recovery"
+      ],
+      "expectations": [
+        "The failure is reproduced before any fix is attempted",
+        "The root cause is identified and stated, not just the symptom patched",
+        "A regression test exists after the fix",
+        "The fix is minimal and scoped to the cause"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Production checkout is failing and a stakeholder demands an immediate pagination patch without reproduction. Respond under time pressure.",
+      "expected_output": "Evidence preserved, the failure reproduced, and a root-cause fix guarded by a regression test",
+      "files": [
+        "i3-debugging-and-error-recovery"
+      ],
+      "expectations": [
+        "The time pressure does not cause reproduction or evidence gathering to be skipped",
+        "The requested speculative patch is not applied before the cause is localized",
+        "The final fix is tied to a reproduced cause and a regression test"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-deprecation-and-migration.json

@@ -0,0 +1,52 @@
+{
+  "skill_name": "i3-deprecation-and-migration",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "We are sunsetting the v1 API, plan the deprecation",
+        "top_k": 3
+      },
+      {
+        "prompt": "Migrate users off the legacy auth system without breaking them",
+        "top_k": 3
+      },
+      {
+        "prompt": "How do I remove this old feature safely for existing users?",
+        "top_k": 3
+      },
+      {
+        "prompt": "Rename a database column without downtime",
+        "top_k": 3
+      },
+      {
+        "prompt": "How do I drop a column safely in production?",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Add dark mode to the settings page",
+        "owner": "i3-frontend-ui-engineering"
+      },
+      {
+        "prompt": "Why is this test flaky on CI?",
+        "owner": "i3-ci-cd-and-automation"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Plan the deprecation of a public v1 REST API with 200 external consumers, replaced by v2.",
+      "expected_output": "A staged deprecation plan: comms, timeline, compatibility window, monitoring, and removal criteria",
+      "files": [
+        "i3-deprecation-and-migration"
+      ],
+      "expectations": [
+        "Consumers are notified with a timeline before any breaking change",
+        "A compatibility or migration window exists with monitoring of remaining usage",
+        "Removal is gated on measured migration, not a calendar date alone"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-documentation-and-adrs.json

@@ -0,0 +1,44 @@
+{
+  "skill_name": "i3-documentation-and-adrs",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "Write an ADR for choosing Postgres over MongoDB",
+        "top_k": 3
+      },
+      {
+        "prompt": "Document the architecture decision behind the queue design",
+        "top_k": 3
+      },
+      {
+        "prompt": "Update the documentation for the new setup flow and record why it changed",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Find the root cause of the memory leak in the worker",
+        "owner": "i3-debugging-and-error-recovery"
+      },
+      {
+        "prompt": "Harden the login endpoint against brute force attacks",
+        "owner": "i3-security-and-hardening"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Record the decision to adopt event sourcing for the orders service as an ADR.",
+      "expected_output": "An ADR capturing context, decision, alternatives considered, and consequences",
+      "files": [
+        "i3-documentation-and-adrs"
+      ],
+      "expectations": [
+        "The ADR states context, decision, alternatives, and consequences distinctly",
+        "Trade-offs and rejected options are recorded, not just the winning choice",
+        "The ADR records a status from the skill's lifecycle (Proposed, Accepted, Superseded or Deprecated) and a date"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-doubt-driven-development.json

@@ -0,0 +1,43 @@
+{
+  "skill_name": "i3-doubt-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "This change touches production auth, cross-examine every assumption before we proceed",
+        "top_k": 3
+      },
+      {
+        "prompt": "I am not confident in this approach, adversarially review my reasoning in a fresh context",
+        "top_k": 3
+      },
+      {
+        "prompt": "High-stakes migration tomorrow, stress the plan for hidden failure modes",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Format this file with prettier"
+      },
+      {
+        "prompt": "Write the changelog entry for the release",
+        "owner": "i3-git-workflow-and-versioning"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Before running an irreversible data migration, subject the migration plan to adversarial review.",
+      "expected_output": "Claims extracted, doubts raised against each, reconciliation, and a go or stop verdict",
+      "files": [
+        "i3-doubt-driven-development"
+      ],
+      "expectations": [
+        "Non-trivial claims in the plan are extracted and challenged individually",
+        "At least one assumption is tested rather than accepted",
+        "The verdict distinguishes verified claims from surviving doubts"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-frontend-ui-engineering.json

@@ -0,0 +1,52 @@
+{
+  "skill_name": "i3-frontend-ui-engineering",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "Make this page responsive and WCAG compliant",
+        "top_k": 1
+      },
+      {
+        "prompt": "Build an accessible modal component with keyboard support",
+        "top_k": 3
+      },
+      {
+        "prompt": "Make the pricing page accessible and responsive on mobile",
+        "top_k": 1
+      },
+      {
+        "prompt": "Refactor the dashboard into reusable components with sane state management",
+        "top_k": 3
+      },
+      {
+        "prompt": "Rework the profile page into reusable components with proper state management",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Optimize the slow database indexes",
+        "owner": "i3-performance-optimization"
+      },
+      {
+        "prompt": "Tag and publish the release",
+        "owner": "i3-git-workflow-and-versioning"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Build a dropdown menu component for the design system.",
+      "expected_output": "An accessible, keyboard-navigable component following project conventions",
+      "files": [
+        "i3-frontend-ui-engineering"
+      ],
+      "expectations": [
+        "Keyboard interaction and focus management are implemented, not just mouse clicks",
+        "ARIA roles or semantic elements are used correctly",
+        "Component state is managed deliberately rather than ad hoc"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-git-workflow-and-versioning.json

@@ -0,0 +1,47 @@
+{
+  "skill_name": "i3-git-workflow-and-versioning",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "Split this messy working tree into clean atomic commits",
+        "top_k": 3
+      },
+      {
+        "prompt": "Resolve the merge conflict on this feature branch",
+        "top_k": 3
+      },
+      {
+        "prompt": "How should we tag and version this release?",
+        "top_k": 3
+      },
+      {
+        "prompt": "Commit this work and open a pull request",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Add a loading spinner to the submit button"
+      },
+      {
+        "prompt": "Write integration tests for the payments API",
+        "owner": "i3-test-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "The working tree mixes a refactor, a bug fix, and a new feature. Turn it into a clean history.",
+      "expected_output": "Separate atomic commits with clear messages, each independently green",
+      "files": [
+        "i3-git-workflow-and-versioning"
+      ],
+      "expectations": [
+        "Refactor, fix, and feature land as separate commits",
+        "Commit messages are imperative and standalone",
+        "Each commit leaves the tree in a working state"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-idea-refine.json

@@ -0,0 +1,43 @@
+{
+  "skill_name": "i3-idea-refine",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "I have a rough idea for a habit tracker, help me refine it",
+        "top_k": 3
+      },
+      {
+        "prompt": "Stress-test my plan for the new onboarding flow",
+        "top_k": 3
+      },
+      {
+        "prompt": "Ideate on ways to improve developer retention in the product",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Fix the failing CI pipeline",
+        "owner": "i3-ci-cd-and-automation"
+      },
+      {
+        "prompt": "Audit the upload endpoint for vulnerabilities",
+        "owner": "i3-security-and-hardening"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "kind": "dialogue",
+      "prompt": "Refine this vague idea: 'some kind of tool that helps teams share knowledge better'.",
+      "expected_output": "Sharpening questions, distinct directions, surfaced assumptions, and a one-pager with MVP scope and a Not Doing list",
+      "expectations": [
+        "Sharpening questions are asked before converging",
+        "Hidden assumptions are surfaced explicitly",
+        "The output includes an explicit Not Doing list",
+        "The agent pushes back on weak aspects instead of only agreeing"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-incremental-implementation.json

@@ -0,0 +1,57 @@
+{
+  "skill_name": "i3-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": "i3-observability-and-instrumentation"
+      },
+      {
+        "prompt": "Interview me to figure out the real requirements",
+        "owner": "i3-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": [
+        "i3-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"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-interview-me.json

@@ -0,0 +1,42 @@
+{
+  "skill_name": "i3-interview-me",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "Interview me about what I actually want before you build anything",
+        "top_k": 3
+      },
+      {
+        "prompt": "Grill me on the requirements, the ask is fuzzy",
+        "top_k": 3
+      },
+      {
+        "prompt": "Ask me one question at a time until you understand the feature",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Run the full test suite and report failures",
+        "owner": "i3-test-driven-development"
+      },
+      {
+        "prompt": "Deploy the current build to staging",
+        "owner": "i3-shipping-and-launch"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "kind": "dialogue",
+      "prompt": "I want 'a better admin page'. Interview me before proposing anything.",
+      "expected_output": "A one-question-at-a-time interview that converges on validated requirements",
+      "expectations": [
+        "Questions are asked one at a time, not in batches",
+        "The agent does not propose solutions before understanding the need",
+        "The interview surfaces the underlying goal behind the stated ask"
+      ]
+    }
+  ]
+}

package/evals/cases/i3-observability-and-instrumentation.json

@@ -0,0 +1,44 @@
+{
+  "skill_name": "i3-observability-and-instrumentation",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "Add structured logging and metrics to the checkout service",
+        "top_k": 3
+      },
+      {
+        "prompt": "Set up tracing so we can follow a request across services",
+        "top_k": 3
+      },
+      {
+        "prompt": "What alerts should we page on for this new endpoint?",
+        "top_k": 3
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "Simplify this over-clever component",
+        "owner": "i3-code-simplification"
+      },
+      {
+        "prompt": "Draft the PRD for the referral program"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Instrument a new payment-retry feature so on-call can operate it.",
+      "expected_output": "On-call questions defined first, then structured logs, RED metrics, and symptom-based alerts that answer them",
+      "files": [
+        "i3-observability-and-instrumentation"
+      ],
+      "expectations": [
+        "On-call questions are written before instrumentation is added",
+        "Logs are structured events with a correlation id, not prose strings",
+        "Metrics avoid unbounded label cardinality",
+        "Alerts are symptom-based and actionable"
+      ]
+    }
+  ]
+}