@givolt/i3-composer-agent 1.0.1 → 2.0.0

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",

package/evals/cases/{using-agent-skills.json → i3-using-agent-skills.json}

@@ -1,5 +1,5 @@
 {
-  "skill_name": "using-agent-skills",
+  "skill_name": "i3-using-agent-skills",
   "trigger": {
     "positive": [
       {
@@ -18,11 +18,11 @@
     "negative": [
       {
         "prompt": "Debug the null pointer crash in checkout",
-        "owner": "debugging-and-error-recovery"
+        "owner": "i3-debugging-and-error-recovery"
       },
       {
         "prompt": "Make the modal accessible for keyboard users",
-        "owner": "frontend-ui-engineering"
+        "owner": "i3-frontend-ui-engineering"
       }
     ]
   },
@@ -32,7 +32,7 @@
       "prompt": "A user asks: 'the login page is broken after yesterday's deploy'. Decide which skill applies and why.",
       "expected_output": "Correct routing through the decision tree with the chosen skill and rationale",
       "files": [
-        "using-agent-skills"
+        "i3-using-agent-skills"
       ],
       "expectations": [
         "The chosen skill matches the decision tree in the meta-skill",

package/evals/fixtures/{git-workflow-and-versioning → i3-git-workflow-and-versioning}/.eval/working-tree.patch

@@ -1,6 +1,6 @@
-diff --git a/git-workflow-and-versioning/app.js b/git-workflow-and-versioning/app.js
---- a/git-workflow-and-versioning/app.js
-+++ b/git-workflow-and-versioning/app.js
+diff --git a/i3-git-workflow-and-versioning/app.js b/i3-git-workflow-and-versioning/app.js
+--- a/i3-git-workflow-and-versioning/app.js
++++ b/i3-git-workflow-and-versioning/app.js
 @@ -1,7 +1,15 @@
  'use strict';
 

package/evals/plugin/code-review-fires/graders/skill-fired.md

@@ -1,5 +1,5 @@
 ---
 type: tool_used
 tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(code-review-and-quality|review)"'
+input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-code-review-and-quality|review)"'
 ---

package/evals/plugin/code-review-stays-quiet/graders/not-fired.md

@@ -1,7 +1,7 @@
 ---
 type: tool_used
 tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(code-review-and-quality|review)"'
+input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-code-review-and-quality|review)"'
 min: 0
 max: 0
 arm: both

package/evals/plugin/code-review-stays-quiet/graders/tdd-fired.md

@@ -1,6 +1,6 @@
 ---
 type: tool_used
 tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(test-driven-development|test)"'
+input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-test-driven-development|test)"'
 arm: with-only
 ---

package/evals/plugin/code-review-stays-quiet/prompt.md

@@ -1,6 +1,6 @@
 ---
-description: A test-first request that belongs to test-driven-development. The review skill must not fire.
-expected_outcome: The reply proposes a failing test first; code-review-and-quality is never invoked.
+description: A test-first request that belongs to i3-test-driven-development. The review skill must not fire.
+expected_outcome: The reply proposes a failing test first; i3-code-review-and-quality is never invoked.
 max_turns: 12
 allowed_tools: [Read, Glob, Grep, Skill]
 ---

package/evals/plugin/code-review-stays-quiet-on-commit-message/graders/not-fired.md

@@ -1,7 +1,7 @@
 ---
 type: tool_used
 tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(code-review-and-quality|review)"'
+input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-code-review-and-quality|review)"'
 min: 0
 max: 0
 arm: both

package/evals/plugin/code-review-stays-quiet-on-commit-message/prompt.md

@@ -1,6 +1,6 @@
 ---
-description: A pasted diff with a request that belongs to git-workflow-and-versioning. Guards the "even when the diff is pasted inline" clause of the review skill's description, since a pasted diff alone must not make the review skill fire.
-expected_outcome: A commit message; code-review-and-quality is never invoked.
+description: A pasted diff with a request that belongs to i3-git-workflow-and-versioning. Guards the "even when the diff is pasted inline" clause of the review skill's description, since a pasted diff alone must not make the review skill fire.
+expected_outcome: A commit message; i3-code-review-and-quality is never invoked.
 max_turns: 12
 allowed_tools: [Read, Glob, Grep, Skill]
 ---

package/hooks/SDD-CACHE.md

@@ -1,10 +1,10 @@
 # sdd-cache hook
 
-Cross-session citation cache for [`source-driven-development`](../skills/source-driven-development/SKILL.md). Skips redundant `WebFetch` calls without weakening the skill's "verify against current docs" guarantee.
+Cross-session citation cache for [`i3-source-driven-development`](../skills/i3-source-driven-development/SKILL.md). Skips redundant `WebFetch` calls without weakening the skill's "verify against current docs" guarantee.
 
 ## Why
 
-`source-driven-development` fetches official docs for every framework-specific decision. Working on the same project across sessions means fetching the same pages over and over. Caching the content as local memory would contradict the skill — docs change, and a stale cache hides that.
+`i3-source-driven-development` fetches official docs for every framework-specific decision. Working on the same project across sessions means fetching the same pages over and over. Caching the content as local memory would contradict the skill — docs change, and a stale cache hides that.
 
 This hook caches fetched content on disk, but **revalidates with the origin server on every reuse** via HTTP `If-None-Match` / `If-Modified-Since`. Content is only served from cache when the server responds `304 Not Modified`, which is a fresh verification — not a memory read.
 
@@ -48,7 +48,7 @@ This hook caches fetched content on disk, but **revalidates with the origin serv
 
 2. Make sure `.claude/sdd-cache/` is in your `.gitignore` (already included in this repo).
 
-3. Use `/source-driven-development` (or the skill) as usual. No changes to the skill or the agent's workflow — the cache is transparent.
+3. Use `/i3-source-driven-development` (or the skill) as usual. No changes to the skill or the agent's workflow — the cache is transparent.
 
 ## Mental model
 

package/hooks/SIMPLIFY-IGNORE.md

@@ -1,6 +1,6 @@
 # simplify-ignore hook
 
-Block-level protection for `/code-simplify`. Mark code that should never be simplified — the model won't see it.
+Block-level protection for `/i3-code-simplify`. Mark code that should never be simplified — the model won't see it.
 
 ## Setup
 
@@ -42,7 +42,7 @@ result[3] = buf[3] ^ key[3];
 }
 ```
 
-3. Run `/code-simplify` — protected blocks become `/* BLOCK_de115a1d: perf-critical */` placeholders. The model reasons about surrounding code without seeing the protected implementation.
+3. Run `/i3-code-simplify` — protected blocks become `/* BLOCK_de115a1d: perf-critical */` placeholders. The model reasons about surrounding code without seeing the protected implementation.
 
 > **Note:** The hook stores temporary backups in `.claude/.simplify-ignore-cache/`. Make sure this path is in your `.gitignore`.
 

package/hooks/session-start-test.sh

@@ -37,7 +37,7 @@ if (hasJq) {
     throw new Error('additionalContext is missing startup preface');
   }
   if (!ctx.includes('# Using i3 Composer Agent')) {
-    throw new Error('additionalContext is missing using-agent-skills content');
+    throw new Error('additionalContext is missing i3-using-agent-skills content');
   }
 } else if (!ctx.includes('jq is required')) {
   throw new Error('additionalContext is missing jq fallback guidance');

package/hooks/session-start.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 # i3-composer-agent session start hook
-# Injects the using-agent-skills meta-skill into a new session.
+# Injects the i3-using-agent-skills meta-skill into a new session.
 #
 # Not wired by the plugin: hosts that already route skills from their
 # descriptions (Claude Code, Codex CLI) would run a second router on top of
@@ -13,7 +13,7 @@
 
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
 SKILLS_DIR="$(dirname "$SCRIPT_DIR")/skills"
-META_SKILL="$SKILLS_DIR/using-agent-skills/SKILL.md"
+META_SKILL="$SKILLS_DIR/i3-using-agent-skills/SKILL.md"
 
 if ! command -v jq >/dev/null 2>&1; then
   echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "i3-composer-agent: jq is required for the session-start hook but was not found on PATH. Install jq (e.g. `brew install jq` or `apt-get install jq`) to enable meta-skill injection. Skills remain available individually."}}'
@@ -29,5 +29,5 @@ if [ -f "$META_SKILL" ]; then
 $CONTENT" \
     '{hookSpecificOutput: {hookEventName: "SessionStart", additionalContext: $context}}'
 else
-  echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "i3-composer-agent: using-agent-skills meta-skill not found. Skills may still be available individually."}}'
+  echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "i3-composer-agent: i3-using-agent-skills meta-skill not found. Skills may still be available individually."}}'
 fi

package/package.json

@@ -82,7 +82,7 @@
     "upstreamCommit": "1401c8b8030e023baeebb31781a6653fe8e93026",
     "upstreamRepository": "https://github.com/addyosmani/agent-skills"
   },
-  "version": "1.0.1",
+  "version": "2.0.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/49780522/i3-composer-agent.git"

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "i3-composer-agent",
-  "version": "1.0.1",
+  "version": "2.0.0",
   "description": "Production-grade engineering skills for AI coding agents covering the development lifecycle from spec to ship.",
   "homepage": "https://github.com/49780522/i3-composer-agent",
   "repository": "https://github.com/49780522/i3-composer-agent"

package/rebrand/INSTALLATION-SPEC.md

@@ -14,7 +14,8 @@ CodeBuddy desktop IDE target.
   registry; CodeBuddy, Codex, Claude Code, Cursor and other tools remain choices.
 - Native installation copies all skills and their shared references. CodeBuddy
   and Claude Code also receive the nine existing command workflows and personas.
-  Portable command references use the installed stable skill IDs.
+  Portable command references use the installed i3- Skill IDs. Prefix migration
+  follows PREFIX-SPEC.md, with backups and rollback for owned legacy paths.
 - Shared destinations are installed once when several tools use the same path.
 - Existing assets require confirmed replacement and are retained in backups.
   Unrelated settings and project files are untouched. Failed installation rolls

package/rebrand/MAINTENANCE.md

@@ -91,7 +91,8 @@ npm pack --pack-destination ../releases/next
 - `overlay/`：本项目的 npm CLI、发行测试、品牌校验和发行 CI；上游相关文件改变时需合并审查。
 - `templates/`：品牌 README 和安装指南；上游对应说明改变时同步模板。
 - 目录数量、Skill 表、命令表和插件描述由已记录的目录生成，不固定为 25/9。
-- Skill frontmatter 保留原文；校验比较换行规范化后的哈希，兼容 LF/CRLF 检出。
+- 源码保留上游 Skill 名称；品牌版 Skill 和命令使用 i3- 前缀，按 PREFIX-SPEC.md 重放。
+- Skill frontmatter 只映射 name；还原 name 后比较换行规范化的上游哈希，兼容 LF/CRLF。
 - LICENSE、NOTICE、真实上游链接、历史评估说明和标准名称保留。
 - 如果上游新增根 package.json，重放会失败，先适配分发配置和依赖再继续。
 
@@ -100,7 +101,7 @@ npm pack --pack-destination ../releases/next
 维护流程与安装能力分开验收。默认 npm CLI 使用多工具安装向导；`--prepare`
 保留完整插件准备和宿主注册提示。两种模式分别验收，不把准备文件等同于安装。
 实际宿主安装范围、启用、命令执行以及交互向导仍需各自验证。
-Codex 的生命周期斜杠命令适配是独立工作，已有 Skill ID 不因维护流程改名。
+Codex 的生命周期斜杠命令适配是独立工作；原生 Skill 通过 $i3-<名称> 调用。
 
 发布审核通过后，发布已经测过的 tarball，先使用试用标签，完成 registry 安装验证后再更新 latest：
 

package/rebrand/NOTICE.md

@@ -6,7 +6,8 @@ The initial distribution is based on upstream commit `1401c8b` (version 0.6.12).
 
 The original MIT license and copyright notice are preserved in LICENSE.
 Givolt maintains the branding, npm distribution, and installation CLI.
-The original skill IDs, command workflows, and persona definitions are retained.
+Skill IDs and command filenames use an i3- prefix in this distribution.
+The original command workflows and persona definitions are retained.
 
 The tool installation directory presets in `bin/agent-targets.json` are adapted
 from Vercel's [Skills CLI registry](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/src/agents.ts)