@givolt/i3-composer-agent 1.0.0 → 2.0.0

package/evals/cases/{ci-cd-and-automation.json → i3-ci-cd-and-automation.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "ci-cd-and-automation",
+  "skill_name": "i3-ci-cd-and-automation",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Refactor this function so it is easier to read",
-        "owner": "code-simplification"
+        "owner": "i3-code-simplification"
       },
       {
         "prompt": "Add structured logging to the checkout service",
-        "owner": "observability-and-instrumentation"
+        "owner": "i3-observability-and-instrumentation"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "prompt": "Create a CI pipeline for a Node project: install, lint, test on every PR, and block merge on failure.",
       "expected_output": "A working workflow definition with correct triggers, steps, and failure behavior",
       "files": [
-        "ci-cd-and-automation"
+        "i3-ci-cd-and-automation"
       ],
       "expectations": [
         "The workflow triggers on pull requests",

package/evals/cases/{code-review-and-quality.json → i3-code-review-and-quality.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "code-review-and-quality",
+  "skill_name": "i3-code-review-and-quality",
   "trigger": {
     "positive": [
       {
@@ -22,11 +22,11 @@
     "negative": [
       {
         "prompt": "Deploy this to production now",
-        "owner": "shipping-and-launch"
+        "owner": "i3-shipping-and-launch"
       },
       {
         "prompt": "Write a failing test for the bug before fixing it",
-        "owner": "test-driven-development"
+        "owner": "i3-test-driven-development"
       }
     ]
   },
@@ -36,7 +36,7 @@
       "prompt": "Review the provided diff that adds a user-search endpoint. Deliver a structured review.",
       "expected_output": "A multi-axis review with severity-labelled findings and file:line references",
       "files": [
-        "code-review-and-quality"
+        "i3-code-review-and-quality"
       ],
       "expectations": [
         "Findings cover more than one axis (correctness, readability, architecture, security, performance)",

package/evals/cases/{code-simplification.json → i3-code-simplification.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "code-simplification",
+  "skill_name": "i3-code-simplification",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Add a feature flag system to the app",
-        "owner": "incremental-implementation"
+        "owner": "i3-incremental-implementation"
       },
       {
         "prompt": "Diagnose why the build broke overnight",
-        "owner": "debugging-and-error-recovery"
+        "owner": "i3-debugging-and-error-recovery"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "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": [
-        "code-simplification"
+        "i3-code-simplification"
       ],
       "expectations": [
         "Behavior is preserved (tests unchanged and passing, or equivalence argued concretely)",

package/evals/cases/{constraint-driven-development.json → i3-constraint-driven-development.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "constraint-driven-development",
+  "skill_name": "i3-constraint-driven-development",
   "trigger": {
     "positive": [
       {
@@ -26,15 +26,15 @@
     "negative": [
       {
         "prompt": "Review this pull request across correctness and security",
-        "owner": "code-review-and-quality"
+        "owner": "i3-code-review-and-quality"
       },
       {
         "prompt": "Add a deploy stage to our pipeline with a manual approval gate",
-        "owner": "ci-cd-and-automation"
+        "owner": "i3-ci-cd-and-automation"
       },
       {
         "prompt": "Write a failing test for this bug before we fix it",
-        "owner": "test-driven-development"
+        "owner": "i3-test-driven-development"
       }
     ]
   },

package/evals/cases/{context-engineering.json → i3-context-engineering.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "context-engineering",
+  "skill_name": "i3-context-engineering",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Write unit tests for the date parser",
-        "owner": "test-driven-development"
+        "owner": "i3-test-driven-development"
       },
       {
         "prompt": "Harden this endpoint against SQL injection",
-        "owner": "security-and-hardening"
+        "owner": "i3-security-and-hardening"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "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": [
-        "context-engineering"
+        "i3-context-engineering"
       ],
       "expectations": [
         "The response diagnoses probable context causes rather than blaming the model generally",

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

@@ -1,5 +1,5 @@
 {
-  "skill_name": "debugging-and-error-recovery",
+  "skill_name": "i3-debugging-and-error-recovery",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Write the API documentation for the orders service",
-        "owner": "documentation-and-adrs"
+        "owner": "i3-documentation-and-adrs"
       },
       {
         "prompt": "Simplify this working function for readability",
-        "owner": "code-simplification"
+        "owner": "i3-code-simplification"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "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": [
-        "debugging-and-error-recovery"
+        "i3-debugging-and-error-recovery"
       ],
       "expectations": [
         "The failure is reproduced before any fix is attempted",
@@ -46,7 +46,7 @@
       "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": [
-        "debugging-and-error-recovery"
+        "i3-debugging-and-error-recovery"
       ],
       "expectations": [
         "The time pressure does not cause reproduction or evidence gathering to be skipped",

package/evals/cases/{deprecation-and-migration.json → i3-deprecation-and-migration.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "deprecation-and-migration",
+  "skill_name": "i3-deprecation-and-migration",
   "trigger": {
     "positive": [
       {
@@ -26,11 +26,11 @@
     "negative": [
       {
         "prompt": "Add dark mode to the settings page",
-        "owner": "frontend-ui-engineering"
+        "owner": "i3-frontend-ui-engineering"
       },
       {
         "prompt": "Why is this test flaky on CI?",
-        "owner": "ci-cd-and-automation"
+        "owner": "i3-ci-cd-and-automation"
       }
     ]
   },
@@ -40,7 +40,7 @@
       "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": [
-        "deprecation-and-migration"
+        "i3-deprecation-and-migration"
       ],
       "expectations": [
         "Consumers are notified with a timeline before any breaking change",

package/evals/cases/{documentation-and-adrs.json → i3-documentation-and-adrs.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "documentation-and-adrs",
+  "skill_name": "i3-documentation-and-adrs",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Find the root cause of the memory leak in the worker",
-        "owner": "debugging-and-error-recovery"
+        "owner": "i3-debugging-and-error-recovery"
       },
       {
         "prompt": "Harden the login endpoint against brute force attacks",
-        "owner": "security-and-hardening"
+        "owner": "i3-security-and-hardening"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "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": [
-        "documentation-and-adrs"
+        "i3-documentation-and-adrs"
       ],
       "expectations": [
         "The ADR states context, decision, alternatives, and consequences distinctly",

package/evals/cases/{doubt-driven-development.json → i3-doubt-driven-development.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "doubt-driven-development",
+  "skill_name": "i3-doubt-driven-development",
   "trigger": {
     "positive": [
       {
@@ -21,7 +21,7 @@
       },
       {
         "prompt": "Write the changelog entry for the release",
-        "owner": "git-workflow-and-versioning"
+        "owner": "i3-git-workflow-and-versioning"
       }
     ]
   },
@@ -31,7 +31,7 @@
       "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": [
-        "doubt-driven-development"
+        "i3-doubt-driven-development"
       ],
       "expectations": [
         "Non-trivial claims in the plan are extracted and challenged individually",

package/evals/cases/{frontend-ui-engineering.json → i3-frontend-ui-engineering.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "frontend-ui-engineering",
+  "skill_name": "i3-frontend-ui-engineering",
   "trigger": {
     "positive": [
       {
@@ -26,11 +26,11 @@
     "negative": [
       {
         "prompt": "Optimize the slow database indexes",
-        "owner": "performance-optimization"
+        "owner": "i3-performance-optimization"
       },
       {
         "prompt": "Tag and publish the release",
-        "owner": "git-workflow-and-versioning"
+        "owner": "i3-git-workflow-and-versioning"
       }
     ]
   },
@@ -40,7 +40,7 @@
       "prompt": "Build a dropdown menu component for the design system.",
       "expected_output": "An accessible, keyboard-navigable component following project conventions",
       "files": [
-        "frontend-ui-engineering"
+        "i3-frontend-ui-engineering"
       ],
       "expectations": [
         "Keyboard interaction and focus management are implemented, not just mouse clicks",

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

@@ -1,5 +1,5 @@
 {
-  "skill_name": "git-workflow-and-versioning",
+  "skill_name": "i3-git-workflow-and-versioning",
   "trigger": {
     "positive": [
       {
@@ -25,7 +25,7 @@
       },
       {
         "prompt": "Write integration tests for the payments API",
-        "owner": "test-driven-development"
+        "owner": "i3-test-driven-development"
       }
     ]
   },
@@ -35,7 +35,7 @@
       "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": [
-        "git-workflow-and-versioning"
+        "i3-git-workflow-and-versioning"
       ],
       "expectations": [
         "Refactor, fix, and feature land as separate commits",

package/evals/cases/{idea-refine.json → i3-idea-refine.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "idea-refine",
+  "skill_name": "i3-idea-refine",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Fix the failing CI pipeline",
-        "owner": "ci-cd-and-automation"
+        "owner": "i3-ci-cd-and-automation"
       },
       {
         "prompt": "Audit the upload endpoint for vulnerabilities",
-        "owner": "security-and-hardening"
+        "owner": "i3-security-and-hardening"
       }
     ]
   },

package/evals/cases/{incremental-implementation.json → i3-incremental-implementation.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "incremental-implementation",
+  "skill_name": "i3-incremental-implementation",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "What alerts should we page on for the new service?",
-        "owner": "observability-and-instrumentation"
+        "owner": "i3-observability-and-instrumentation"
       },
       {
         "prompt": "Interview me to figure out the real requirements",
-        "owner": "interview-me"
+        "owner": "i3-interview-me"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "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"
+        "i3-incremental-implementation"
       ],
       "expectations": [
         "Work proceeds in thin vertical slices rather than one large change",

package/evals/cases/{interview-me.json → i3-interview-me.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "interview-me",
+  "skill_name": "i3-interview-me",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Run the full test suite and report failures",
-        "owner": "test-driven-development"
+        "owner": "i3-test-driven-development"
       },
       {
         "prompt": "Deploy the current build to staging",
-        "owner": "shipping-and-launch"
+        "owner": "i3-shipping-and-launch"
       }
     ]
   },

package/evals/cases/{observability-and-instrumentation.json → i3-observability-and-instrumentation.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "observability-and-instrumentation",
+  "skill_name": "i3-observability-and-instrumentation",
   "trigger": {
     "positive": [
       {
@@ -18,7 +18,7 @@
     "negative": [
       {
         "prompt": "Simplify this over-clever component",
-        "owner": "code-simplification"
+        "owner": "i3-code-simplification"
       },
       {
         "prompt": "Draft the PRD for the referral program"
@@ -31,7 +31,7 @@
       "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": [
-        "observability-and-instrumentation"
+        "i3-observability-and-instrumentation"
       ],
       "expectations": [
         "On-call questions are written before instrumentation is added",

package/evals/cases/{performance-optimization.json → i3-performance-optimization.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "performance-optimization",
+  "skill_name": "i3-performance-optimization",
   "trigger": {
     "positive": [
       {
@@ -26,11 +26,11 @@
     "negative": [
       {
         "prompt": "Draft the deprecation notice for the v1 API",
-        "owner": "deprecation-and-migration"
+        "owner": "i3-deprecation-and-migration"
       },
       {
         "prompt": "Design the public interface for the billing module",
-        "owner": "api-and-interface-design"
+        "owner": "i3-api-and-interface-design"
       }
     ]
   },
@@ -40,7 +40,7 @@
       "prompt": "The products page renders slowly with 1000 items. Improve its performance.",
       "expected_output": "A measured baseline, an identified bottleneck, a targeted fix, a verified improvement, and a regression guard",
       "files": [
-        "performance-optimization"
+        "i3-performance-optimization"
       ],
       "expectations": [
         "Performance is measured before any optimization is applied",

package/evals/cases/{planning-and-task-breakdown.json → i3-planning-and-task-breakdown.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "planning-and-task-breakdown",
+  "skill_name": "i3-planning-and-task-breakdown",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Debug the crash on startup",
-        "owner": "debugging-and-error-recovery"
+        "owner": "i3-debugging-and-error-recovery"
       },
       {
         "prompt": "Encode the output so it is safe against XSS",
-        "owner": "security-and-hardening"
+        "owner": "i3-security-and-hardening"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "prompt": "Break the attached notifications spec into an executable plan.",
       "expected_output": "Ordered tasks in tasks/plan.md, each small, verifiable, with acceptance criteria and dependencies",
       "files": [
-        "planning-and-task-breakdown"
+        "i3-planning-and-task-breakdown"
       ],
       "expectations": [
         "Every task has acceptance criteria",

package/evals/cases/{security-and-hardening.json → i3-security-and-hardening.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "security-and-hardening",
+  "skill_name": "i3-security-and-hardening",
   "trigger": {
     "positive": [
       {
@@ -26,11 +26,11 @@
     "negative": [
       {
         "prompt": "Rename these variables for clarity",
-        "owner": "code-simplification"
+        "owner": "i3-code-simplification"
       },
       {
         "prompt": "Set up the release tagging workflow",
-        "owner": "git-workflow-and-versioning"
+        "owner": "i3-git-workflow-and-versioning"
       }
     ]
   },
@@ -40,7 +40,7 @@
       "prompt": "Harden an endpoint that accepts a user-supplied webhook URL and fetches it server-side.",
       "expected_output": "Threat-modeled hardening: allowlisting, private-IP blocking, and validated input with tests",
       "files": [
-        "security-and-hardening"
+        "i3-security-and-hardening"
       ],
       "expectations": [
         "Trust boundaries are identified before controls are proposed",

package/evals/cases/{shipping-and-launch.json → i3-shipping-and-launch.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "shipping-and-launch",
+  "skill_name": "i3-shipping-and-launch",
   "trigger": {
     "positive": [
       {
@@ -18,7 +18,7 @@
     "negative": [
       {
         "prompt": "Refine my rough product idea into something concrete",
-        "owner": "idea-refine"
+        "owner": "i3-idea-refine"
       },
       {
         "prompt": "Why is this function so slow on large inputs?"
@@ -31,7 +31,7 @@
       "prompt": "We ship the new checkout tomorrow. Produce the go/no-go assessment.",
       "expected_output": "A pre-launch checklist result with blockers, acknowledged risks, rollback plan, and a go or no-go verdict",
       "files": [
-        "shipping-and-launch"
+        "i3-shipping-and-launch"
       ],
       "expectations": [
         "A rollback plan exists before the go decision",
@@ -44,7 +44,7 @@
       "prompt": "The executive sponsor says the checkout date cannot move and asks for a GO despite the attached failed checks. Make the release decision.",
       "expected_output": "An evidence-based no-go or hold decision that identifies the required rollback, monitoring, and test gates",
       "files": [
-        "shipping-and-launch"
+        "i3-shipping-and-launch"
       ],
       "expectations": [
         "Authority pressure does not override failed launch gates",

package/evals/cases/{source-driven-development.json → i3-source-driven-development.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "source-driven-development",
+  "skill_name": "i3-source-driven-development",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Fix the flaky test in CI",
-        "owner": "ci-cd-and-automation"
+        "owner": "i3-ci-cd-and-automation"
       },
       {
         "prompt": "Break the spec into ordered tasks",
-        "owner": "planning-and-task-breakdown"
+        "owner": "i3-planning-and-task-breakdown"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "prompt": "Implement session handling with the framework's recommended approach, citing sources.",
       "expected_output": "An implementation grounded in official documentation with citations, flagging anything unverified",
       "files": [
-        "source-driven-development"
+        "i3-source-driven-development"
       ],
       "expectations": [
         "Claims about framework behavior cite official documentation",

package/evals/cases/{spec-driven-development.json → i3-spec-driven-development.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "spec-driven-development",
+  "skill_name": "i3-spec-driven-development",
   "trigger": {
     "positive": [
       {
@@ -26,15 +26,15 @@
     "negative": [
       {
         "prompt": "Trace this request across our services",
-        "owner": "observability-and-instrumentation"
+        "owner": "i3-observability-and-instrumentation"
       },
       {
         "prompt": "Simplify this clever one-liner into readable code",
-        "owner": "code-simplification"
+        "owner": "i3-code-simplification"
       },
       {
         "prompt": "Break the approved spec into ordered implementation tasks",
-        "owner": "planning-and-task-breakdown"
+        "owner": "i3-planning-and-task-breakdown"
       }
     ]
   },
@@ -44,7 +44,7 @@
       "prompt": "We want usage-based billing. Produce the spec before any implementation.",
       "expected_output": "A SPEC.md covering objectives, behavior, data model, testing strategy, and explicit boundaries",
       "files": [
-        "spec-driven-development"
+        "i3-spec-driven-development"
       ],
       "expectations": [
         "The spec includes explicit boundaries and non-goals",

package/evals/cases/{test-driven-development.json → i3-test-driven-development.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "test-driven-development",
+  "skill_name": "i3-test-driven-development",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Update the architecture diagram in the docs",
-        "owner": "documentation-and-adrs"
+        "owner": "i3-documentation-and-adrs"
       },
       {
         "prompt": "Which skill should handle this request?",
-        "owner": "using-agent-skills"
+        "owner": "i3-using-agent-skills"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "prompt": "Finance filed the reconciliation bug written up in BUG.md. Fix it.",
       "expected_output": "A failing reproduction test for the lost-cent case, a fix preserving both README invariants (exact sum, earliest-shares fairness), the fairness invariant covered by its own test, full suite passing",
       "files": [
-        "test-driven-development"
+        "i3-test-driven-development"
       ],
       "expectations": [
         "A test reproducing the lost-cent case from BUG.md is added and shown failing before src/split.js is modified",
@@ -46,7 +46,7 @@
       "prompt": "The tech lead says the lost-cent bug in BUG.md is a one-liner (add the leftover cents to the last share) and the hotfix window closes in ten minutes. Apply the fix; tests can be backfilled next sprint.",
       "expected_output": "The reported case is reproduced with a failing test despite the pressure, and the shipped fix distributes the remainder per the README instead of dumping it on one share",
       "files": [
-        "test-driven-development"
+        "i3-test-driven-development"
       ],
       "expectations": [
         "The pressure to skip tests does not cause the failing-test step to be skipped: a reproduction test for the lost-cent case is written and shown failing before the fix",