@givolt/i3-composer-agent 0.6.12 → 1.0.1

package/.agents/plugins/marketplace.json

@@ -6,7 +6,7 @@
   "plugins": [
     {
       "name": "i3-composer-agent",
-      "version": "0.6.12",
+      "version": "1.0.1",
       "description": "Production-grade engineering skills for AI coding agents covering the development lifecycle from spec to ship.",
       "source": {
         "source": "local",
@@ -16,7 +16,8 @@
         "installation": "AVAILABLE",
         "authentication": "ON_INSTALL"
       },
-      "category": "Productivity"
+      "category": "Productivity",
+      "homepage": "https://github.com/49780522/i3-composer-agent"
     }
   ]
 }

package/.claude-plugin/marketplace.json

@@ -8,9 +8,10 @@
   "plugins": [
     {
       "name": "i3-composer-agent",
-      "version": "0.6.12",
+      "version": "1.0.1",
       "source": "./",
       "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",
       "license": "MIT",
       "keywords": [
         "skills",

package/.claude-plugin/plugin.json

@@ -1,10 +1,12 @@
 {
   "name": "i3-composer-agent",
-  "version": "0.6.12",
+  "version": "1.0.1",
   "description": "Production-grade engineering skills for AI coding agents covering the development lifecycle from spec to ship.",
   "author": {
     "name": "Givolt"
   },
+  "homepage": "https://github.com/49780522/i3-composer-agent",
+  "repository": "https://github.com/49780522/i3-composer-agent",
   "license": "MIT",
   "commands": [
     "./.claude/commands",

package/.codex-plugin/plugin.json

@@ -1,10 +1,12 @@
 {
   "name": "i3-composer-agent",
-  "version": "0.6.12",
+  "version": "1.0.1",
   "description": "Production-grade engineering skills for AI coding agents covering the development lifecycle from spec to ship.",
   "author": {
     "name": "Givolt"
   },
+  "homepage": "https://github.com/49780522/i3-composer-agent",
+  "repository": "https://github.com/49780522/i3-composer-agent",
   "license": "MIT",
   "skills": "./skills/",
   "interface": {

package/CHANGELOG.md

@@ -0,0 +1,34 @@
+# i3 Composer Agent changes
+
+## 1.0.1 — 2026-10-07
+
+Upstream baseline: agent-skills 0.6.12 at commit 1401c8b8030e023baeebb31781a6653fe8e93026.
+
+### Fixed
+
+- Restore the promised terminal installation wizard with multiple tool selection, project/global scope, a destination summary and confirmation.
+- Install complete native skill files and shared references; include short lifecycle commands and personas for CodeBuddy and Claude Code.
+- Protect existing assets with confirmed replacement, backups and rollback on installation failure.
+- Retain complete plugin preparation with --prepare and existing explicit --dir calls.
+
+## 1.0.0 — 2026-10-07
+
+Upstream baseline: agent-skills 0.6.12 at commit 1401c8b8030e023baeebb31781a6653fe8e93026.
+
+### Changed
+
+- Start independent i3 release numbering. The upstream baseline remains 0.6.12; this replaces the unpublished 0.6.13 candidate.
+- Display the i3 release and upstream baseline together in the README, CLI help, and bundle preparation output. Keep --version machine-readable.
+- Include the upstream version, commit, and repository in package metadata.
+- Maintain source changes on agent/source, generate and validate a branded candidate, then update main in this independent repository.
+
+### Fixed
+
+- Preserve complete reviewed runtime assets when replaying branding, including newly approved upstream skills and commands.
+- Keep replay checks repeatable in npm bundles without repository CI files.
+- Preserve branded ignore rules and exclude Finder metadata from runtime preservation checks.
+
+## 0.6.12
+
+- Publish the first i3 Composer Agent npm distribution based on agent-skills 0.6.12.
+- Retain upstream skill IDs, command workflows, specialist personas, shared references, and MIT attribution.

package/NOTICE.md

@@ -5,5 +5,10 @@ i3 Composer Agent is a branded distribution of
 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 bundle preparation CLI.
+Givolt maintains the branding, npm distribution, and installation CLI.
 The original skill IDs, 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)
+at commit `48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e`. Copyright (c) 2026
+Vercel, Inc. Its MIT license is retained in `bin/skills-registry.LICENSE`.

package/README.md

@@ -1,178 +1,156 @@
-# i3 Composer Agent
+# i3 Composer Agent v1.0.1
 
-**Intelligence. Integration. Innovation.**
+**Based on agent-skills v0.6.12**
 
-Production-grade engineering skills, lifecycle commands, and specialist personas
-for AI coding agents. This is the engineering-skill product in the i3 Composer
-family; the GSD-derived workflow product is maintained separately.
+**Intelligence. Integration. Innovation.**
 
+Engineering skills, lifecycle commands, and specialist personas for AI coding agents.
 Based on [Agent Skills](https://github.com/addyosmani/agent-skills) by Addy Osmani
-(MIT). See [NOTICE.md](NOTICE.md) for attribution and the upstream baseline.
+(MIT). See [NOTICE.md](NOTICE.md) for attribution.
 
-## Prepare the complete plugin with npx
+The npm package is `@givolt/i3-composer-agent`; the plugin and marketplace ID is
+`i3-composer-agent`. Skill IDs retain their upstream names.
 
-The npm package is `@givolt/i3-composer-agent`. The plugin and marketplace ID is
-`i3-composer-agent`. Skill IDs and workflow behavior retain their upstream names.
+## Install with the wizard
 
-Once the package is published, run this in the project where you want to use it:
+Run in the project where you want to use the skills:
 
 ```bash
+npx @givolt/i3-composer-agent
+# Preselect a tool; the wizard still allows multiple selections:
 npx @givolt/i3-composer-agent --codebuddy
-# Or prepare a bundle for another host:
-npx @givolt/i3-composer-agent --codex
-npx @givolt/i3-composer-agent --claude
 ```
 
-The CLI prepares a persistent `./i3-composer-agent/` directory with all 25 skills,
-9 commands, 4 personas, and shared references. It prints the native registration
-commands; run those in the selected host to enable the plugin.
+The interactive terminal wizard offers multiple tools, project or global scope,
+an installation summary, and confirmation. Its 79 tool directory presets come
+from the pinned [Vercel Skills CLI registry](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/src/agents.ts).
+Choose by tool ID or comma-separated menu numbers. Use `--list-agents` to list
+the choices. Directory presets are not an execution test of every host.
 
-### CodeBuddy / Claude Code
+Every selected tool receives all 25 skills and shared references.
+CodeBuddy and Claude Code also receive 9 short command workflows
+and 4 persona files. Other tools use their native skill support;
+short lifecycle commands depend on the host. Shared destinations are installed
+once. License and attribution files accompany each native installation.
+Reload the IDE window or start a new session after installation. See
+[CodeBuddy setup](docs/codebuddy-setup.md) and [Codex setup](docs/codex-setup.md).
 
-```text
-/plugin marketplace add ./i3-composer-agent
-/plugin install i3-composer-agent@i3-composer-agent
-```
-
-Use the absolute directory printed by the CLI if the host has a different
-working directory. See [CodeBuddy setup](docs/codebuddy-setup.md).
-
-### Codex
+For an explicit installation without prompts:
 
 ```bash
-codex plugin marketplace add ./i3-composer-agent
-codex plugin add i3-composer-agent@i3-composer-agent
+npx @givolt/i3-composer-agent --agents codebuddy,codex --scope project --yes
+npx @givolt/i3-composer-agent --claude --scope global --yes
+npx @givolt/i3-composer-agent --codebuddy --scope project --dry-run
 ```
 
-Start a new Codex session. Invoke the existing skills by name, using `/skills`
-or `$spec-driven-development` in CLI/IDE. This conversion preserves Codex's
-skill adapter; lifecycle slash-command adaptation is a separate task.
-See [Codex setup](docs/codex-setup.md).
+Existing assets require confirmation; use `--force` with noninteractive installs.
+Replacement preserves previous files in a `.i3-composer-agent-backup-*` directory
+under each tool configuration root. Unrelated settings are left in place.
+`npx -y` accepts npm's package download prompt; the package's own `--yes` flag
+accepts the explicit installation plan.
+
+## Prepare the complete plugin
 
-### Bundle options
+For native plugin registration, including plugin hooks, explicitly prepare a
+persistent `./i3-composer-agent/` bundle:
 
 ```bash
-npx @givolt/i3-composer-agent --extract --dir /path/to/i3-composer-agent
-npx @givolt/i3-composer-agent --codebuddy --dir /path/to/plugin --dry-run
-npx @givolt/i3-composer-agent --codebuddy --dir /path/to/plugin --force
+npx @givolt/i3-composer-agent --prepare --codebuddy
+npx @givolt/i3-composer-agent --prepare --codex
+npx @givolt/i3-composer-agent --prepare --claude
 ```
 
-An existing directory is refused unless `--force` targets an i3 Composer Agent
-bundle. Replacement keeps the previous directory as a backup. No repository
-AGENTS.md or CLAUDE.md is copied into the target project.
-
-## Commands
-
-Hosts supporting Claude-compatible plugin commands load these workflows.
-Use the namespaced form, for example `/i3-composer-agent:spec`.
-
-| Command | Workflow |
-| --- | --- |
-| `/i3-composer-agent:spec` | Define objectives, constraints, and acceptance criteria |
-| `/i3-composer-agent:plan` | Write ordered, verifiable tasks |
-| `/i3-composer-agent:build` | Implement the next task with verification |
-| `/i3-composer-agent:build auto` | Execute the approved plan with per-task verification |
-| `/i3-composer-agent:test` | Test-first development and regression checks |
-| `/i3-composer-agent:constraints` | Establish a written quality bar |
-| `/i3-composer-agent:review` | Review code quality and correctness |
-| `/i3-composer-agent:webperf` | Audit web performance |
-| `/i3-composer-agent:code-simplify` | Simplify code without changing behavior |
-| `/i3-composer-agent:ship` | Review launch readiness and rollback |
-
-## All 25 Skills
-
-The commands above are entry points. The pack includes 25 skills total — 24 lifecycle skills plus the `using-agent-skills` meta-skill. Each skill is a structured workflow with steps, verification gates, and anti-rationalization tables. You can also reference any skill directly.
-
-### Meta - Discover which skill applies
-
-| Skill | What It Does | Use When |
-|-------|-------------|----------|
-| [using-agent-skills](skills/using-agent-skills/SKILL.md) | Maps incoming work to the right skill workflow and defines shared operating rules | Starting a session or deciding which skill applies |
+The bundle includes skills, commands, personas, hooks and references. Run the
+registration commands printed by the CLI in the intended host. This preparation
+mode does not install native skills or choose the host plugin manager's scope.
 
-### Define - Clarify what to build
+CodeBuddy Code (terminal) / Claude Code:
 
-| Skill | What It Does | Use When |
-|-------|-------------|----------|
-| [interview-me](skills/interview-me/SKILL.md) | One-question-at-a-time interview that extracts what the user actually wants instead of what they think they should want, until ~95% confidence | The ask is underspecified, or the user invokes "interview me" / "grill me" |
-| [idea-refine](skills/idea-refine/SKILL.md) | Structured divergent/convergent thinking to turn vague ideas into concrete proposals | You have a rough concept that needs exploration |
-| [spec-driven-development](skills/spec-driven-development/SKILL.md) | Write a PRD covering objectives, commands, structure, code style, testing, and boundaries before any code | Starting a new project, feature, or significant change |
-| [constraint-driven-development](skills/constraint-driven-development/SKILL.md) | Interviews you for a quality bar with sane default thresholds, writes CONSTRAINTS.md, places each check by cost, and catches agents silencing checks or skipping tests to get green | No standards are written down, or an agent is producing more than anyone reads |
-
-### Plan - Break it down
-
-| Skill | What It Does | Use When |
-|-------|-------------|----------|
-| [planning-and-task-breakdown](skills/planning-and-task-breakdown/SKILL.md) | Decompose specs into small, verifiable tasks with acceptance criteria and dependency ordering | You have a spec and need implementable units |
-
-### Build - Write the code
-
-| Skill | What It Does | Use When |
-|-------|-------------|----------|
-| [incremental-implementation](skills/incremental-implementation/SKILL.md) | Thin vertical slices - implement, test, verify, commit. Feature flags, safe defaults, rollback-friendly changes | Any change touching more than one file |
-| [test-driven-development](skills/test-driven-development/SKILL.md) | Red-Green-Refactor, test pyramid (80/15/5), test sizes, DAMP over DRY, Beyonce Rule, browser testing | Implementing logic, fixing bugs, or changing behavior |
-| [context-engineering](skills/context-engineering/SKILL.md) | Feed agents the right information at the right time - rules files, context packing, MCP integrations | Starting a session, switching tasks, or when output quality drops |
-| [source-driven-development](skills/source-driven-development/SKILL.md) | Ground every framework decision in official documentation - verify, cite sources, flag what's unverified | You want authoritative, source-cited code for any framework or library |
-| [doubt-driven-development](skills/doubt-driven-development/SKILL.md) | Adversarial fresh-context review of every non-trivial decision in-flight - CLAIM → EXTRACT → DOUBT → RECONCILE → STOP, with optional user-authorized cross-model escalation | Stakes are high (production, security, irreversible), working in unfamiliar code, or a confident output is cheaper to verify now than to debug later |
-| [frontend-ui-engineering](skills/frontend-ui-engineering/SKILL.md) | Component architecture, design systems, state management, responsive design, WCAG 2.1 AA accessibility | Building or modifying user-facing interfaces |
-| [api-and-interface-design](skills/api-and-interface-design/SKILL.md) | Contract-first design, Hyrum's Law, One-Version Rule, error semantics, boundary validation | Designing APIs, module boundaries, or public interfaces |
-
-### Verify - Prove it works
-
-| Skill | What It Does | Use When |
-|-------|-------------|----------|
-| [browser-testing-with-devtools](skills/browser-testing-with-devtools/SKILL.md) | Chrome DevTools MCP for live runtime data - DOM inspection, console logs, network traces, performance profiling | Building or debugging anything that runs in a browser |
-| [debugging-and-error-recovery](skills/debugging-and-error-recovery/SKILL.md) | Five-step triage: reproduce, localize, reduce, fix, guard. Stop-the-line rule, safe fallbacks | Tests fail, builds break, or behavior is unexpected |
-
-### Review - Quality gates before merge
+```text
+/plugin marketplace add ./i3-composer-agent
+/plugin install i3-composer-agent@i3-composer-agent
+```
 
-| Skill | What It Does | Use When |
-|-------|-------------|----------|
-| [code-review-and-quality](skills/code-review-and-quality/SKILL.md) | Five-axis review, change sizing (~100 lines), severity labels (Nit/Optional/FYI), review speed norms, splitting strategies | Before merging any change |
-| [code-simplification](skills/code-simplification/SKILL.md) | Chesterton's Fence, Rule of 500, reduce complexity while preserving exact behavior | Code works but is harder to read or maintain than it should be |
-| [security-and-hardening](skills/security-and-hardening/SKILL.md) | OWASP Top 10 prevention, auth patterns, secrets management, dependency auditing, three-tier boundary system | Handling user input, auth, data storage, or external integrations |
-| [performance-optimization](skills/performance-optimization/SKILL.md) | Measure-first approach - Core Web Vitals targets, profiling workflows, bundle analysis, anti-pattern detection | Performance requirements exist or you suspect regressions |
+Codex:
 
-### Ship - Deploy with confidence
+```bash
+codex plugin marketplace add ./i3-composer-agent
+codex plugin add i3-composer-agent@i3-composer-agent
+```
 
-| Skill | What It Does | Use When |
-|-------|-------------|----------|
-| [git-workflow-and-versioning](skills/git-workflow-and-versioning/SKILL.md) | Trunk-based development, atomic commits, change sizing (~100 lines), the commit-as-save-point pattern | Making any code change (always) |
-| [ci-cd-and-automation](skills/ci-cd-and-automation/SKILL.md) | Shift Left, Faster is Safer, feature flags, quality gate pipelines, failure feedback loops | Setting up or modifying build and deploy pipelines |
-| [deprecation-and-migration](skills/deprecation-and-migration/SKILL.md) | Code-as-liability mindset, compulsory vs advisory deprecation, migration patterns, zombie code removal | Removing old systems, migrating users, or sunsetting features |
-| [documentation-and-adrs](skills/documentation-and-adrs/SKILL.md) | Architecture Decision Records, API docs, inline documentation standards - document the *why* | Making architectural decisions, changing APIs, or shipping features |
-| [observability-and-instrumentation](skills/observability-and-instrumentation/SKILL.md) | Structured logging, RED metrics, OpenTelemetry tracing, symptom-based alerting - instrument as you build | Adding telemetry, or shipping anything that runs in production |
-| [shipping-and-launch](skills/shipping-and-launch/SKILL.md) | Pre-launch checklists, feature flag lifecycle, staged rollouts, rollback procedures, monitoring setup | Preparing to deploy to production |
+Start a new session after enabling the plugin. Codex uses the existing Skill
+names, such as `$spec-driven-development`; lifecycle slash-command adaptation
+is maintained separately.
 
----
+## Commands
 
-## Personas and shared references
+Native CodeBuddy and Claude Code installations use short filenames such as
+`/spec`, `/plan`, `/build` and `/ship`. Hosts supporting Claude-compatible plugin
+commands load the same workflows under the plugin namespace:
 
-The four original personas remain in [agents/](agents/): code reviewer, security
-auditor, test engineer, and web performance auditor. Shared checklists remain in [references/](references/).
-Their relative layout is preserved across npm packaging and bundle extraction.
+| Command | Description |
+| --- | --- |
+| /i3-composer-agent:build | Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass. |
+| /i3-composer-agent:code-simplify | Simplify code for clarity and maintainability — reduce complexity without changing behavior |
+| /i3-composer-agent:constraints | Define and enforce this project's quality bar — interview, sane defaults, CONSTRAINTS.md |
+| /i3-composer-agent:plan | Break work into small verifiable tasks with acceptance criteria and dependency ordering |
+| /i3-composer-agent:review | Conduct a five-axis code review — correctness, readability, architecture, security, performance |
+| /i3-composer-agent:ship | Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision |
+| /i3-composer-agent:spec | Start spec-driven development — write a structured specification before writing code |
+| /i3-composer-agent:test | Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern. |
+| /i3-composer-agent:webperf | Run a web performance audit via the web-performance-auditor persona |
 
-## Other hosts
+`/i3-composer-agent:build auto` runs the existing approved-plan workflow.
 
-The existing [host guides](docs/other-hosts.md) describe additional integrations.
-Prepare the complete local bundle first and use its path in host-specific setup.
-Per-skill installation is separate and may omit the shared references, command
-wrappers, and personas.
+## Skills
 
-## Development and release
+| Skill | Description |
+| --- | --- |
+| [api-and-interface-design](skills/api-and-interface-design/SKILL.md) | Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend. |
+| [browser-testing-with-devtools](skills/browser-testing-with-devtools/SKILL.md) | Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured. |
+| [ci-cd-and-automation](skills/ci-cd-and-automation/SKILL.md) | Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies. |
+| [code-review-and-quality](skills/code-review-and-quality/SKILL.md) | Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline. |
+| [code-simplification](skills/code-simplification/SKILL.md) | Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity. |
+| [constraint-driven-development](skills/constraint-driven-development/SKILL.md) | Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read. |
+| [context-engineering](skills/context-engineering/SKILL.md) | Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project. |
+| [debugging-and-error-recovery](skills/debugging-and-error-recovery/SKILL.md) | Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing. |
+| [deprecation-and-migration](skills/deprecation-and-migration/SKILL.md) | Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. |
+| [documentation-and-adrs](skills/documentation-and-adrs/SKILL.md) | Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase. |
+| [doubt-driven-development](skills/doubt-driven-development/SKILL.md) | Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later. |
+| [frontend-ui-engineering](skills/frontend-ui-engineering/SKILL.md) | Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated. |
+| [git-workflow-and-versioning](skills/git-workflow-and-versioning/SKILL.md) | Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog. |
+| [idea-refine](skills/idea-refine/SKILL.md) | Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan". |
+| [incremental-implementation](skills/incremental-implementation/SKILL.md) | Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step. |
+| [interview-me](skills/interview-me/SKILL.md) | Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists. |
+| [observability-and-instrumentation](skills/observability-and-instrumentation/SKILL.md) | Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data. |
+| [performance-optimization](skills/performance-optimization/SKILL.md) | Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. |
+| [planning-and-task-breakdown](skills/planning-and-task-breakdown/SKILL.md) | Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. |
+| [security-and-hardening](skills/security-and-hardening/SKILL.md) | Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved. |
+| [shipping-and-launch](skills/shipping-and-launch/SKILL.md) | Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. |
+| [source-driven-development](skills/source-driven-development/SKILL.md) | Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. |
+| [spec-driven-development](skills/spec-driven-development/SKILL.md) | Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying. |
+| [test-driven-development](skills/test-driven-development/SKILL.md) | Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. |
+| [using-agent-skills](skills/using-agent-skills/SKILL.md) | Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked. |
+
+## Bundle options
 
 ```bash
-npm run rebrand:check
-npm run validate
-npm test
-node scripts/run-evals.js --min-rank1 95
-npm pack --pack-destination /path/to/release-directory
+npx @givolt/i3-composer-agent --extract --dir /path/to/plugin
+npx @givolt/i3-composer-agent --codebuddy --dir /path/to/plugin --dry-run
+npx @givolt/i3-composer-agent --codebuddy --dir /path/to/plugin --force
 ```
 
-[npx](https://docs.npmjs.com/cli/npm-exec/) runs the package executable;
-`npm pack` builds a tarball and `npm publish` publishes it.
-Local preparation does not establish registry publication or model behavior.
-See [brand maintenance](rebrand/MAINTENANCE.md) for source/release separation.
+Explicit `--dir` retains the original plugin preparation behavior. Replacement
+preserves the previous i3 bundle as a backup. Repository-scoped
+AGENTS.md and CLAUDE.md are not copied into business projects.
+
+## Maintaining this fork
 
-## License
+This repository is independent of the GSD-based i3 Composer Work repository.
+`agent/source` retains upstream source and the `rebrand/` rules; `main` contains
+the validated branded distribution. Create release candidates from the source
+branch, replay branding, validate, then update the release branch.
 
-MIT. Original copyright and license are retained in [LICENSE](LICENSE).
+See [maintenance](rebrand/MAINTENANCE.md), [source PR workflow](rebrand/PR-WORKFLOW.md),
+[versioning](rebrand/VERSIONING.md), [changelog](CHANGELOG.md),
+and [validation contract](rebrand/VALIDATION.md).