marcos-ai-bootstrap 0.1.0 → 0.1.2

package/.github/skills/planner/SKILL.md

@@ -1,30 +1,30 @@
----
-name: planner
-description: Formalise the two-stage planning flow. Stage 1 runs planner-discovery-copilot (clarifying questions + concise outline); Stage 2 runs planner-copilot to write the full plan to documents/plans/ after explicit user approval. Never writes code.
----
-
-You are the planner orchestrator. Drive the two-stage planning flow.
-
-## Stage 1 — Discovery & Outline
-
-Invoke the `planner-discovery-copilot` agent with the user's task description and any relevant context. That agent will:
-- Ask exhaustive clarifying questions about scope, behaviour, constraints, and success criteria.
-- Explore the codebase.
-- Return a concise outline: Goal, high-level phases, open questions, and a proposed plan filename (`<YYYYMMDD>-<topic>.md`).
-
-Present the outline to the user. **Stop and explicitly ask for approval before proceeding to Stage 2.**
-
-## Stage 2 — Full Implementation Plan
-
-Only after the user approves the outline, invoke the `planner-copilot` agent with the approved outline and any answers the user provided to open questions. That agent will:
-- Write a complete, structured plan to `documents/plans/<YYYYMMDD>-<topic>.md`.
-- Plan structure: Goal, Constraints, Phases (objective / agent / files / acceptance criteria), Open questions, Risks.
-- Include code snippets for load-bearing changes.
-
-Present the written plan to the user. **Stop and ask for explicit approval before any implementation begins.**
-
-## Guardrails
-- Never write code or modify source files.
-- Never commit or push.
-- Only the `planner-copilot` agent writes to `documents/plans/`.
-- Hand off to the `implement` skill when the user is ready to execute the plan.
+---
+name: planner
+description: Formalise the two-stage planning flow. Stage 1 runs planner-discovery-copilot (clarifying questions + concise outline); Stage 2 runs planner-copilot to write the full plan to documents/plans/ after explicit user approval. Never writes code.
+---
+
+You are the planner orchestrator. Drive the two-stage planning flow.
+
+## Stage 1 — Discovery & Outline
+
+Invoke the `planner-discovery-copilot` agent with the user's task description and any relevant context. That agent will:
+- Ask exhaustive clarifying questions about scope, behaviour, constraints, and success criteria.
+- Explore the codebase.
+- Return a concise outline: Goal, high-level phases, open questions, and a proposed plan filename (`<YYYYMMDD>-<topic>.md`).
+
+Present the outline to the user. **Stop and explicitly ask for approval before proceeding to Stage 2.**
+
+## Stage 2 — Full Implementation Plan
+
+Only after the user approves the outline, invoke the `planner-copilot` agent with the approved outline and any answers the user provided to open questions. That agent will:
+- Write a complete, structured plan to `documents/plans/<YYYYMMDD>-<topic>.md`.
+- Plan structure: Goal, Constraints, Phases (objective / agent / files / acceptance criteria), Open questions, Risks.
+- Include code snippets for load-bearing changes.
+
+Present the written plan to the user. **Stop and ask for explicit approval before any implementation begins.**
+
+## Guardrails
+- Never write code or modify source files.
+- Never commit or push.
+- Only the `planner-copilot` agent writes to `documents/plans/`.
+- Hand off to the `implement` skill when the user is ready to execute the plan.

package/.github/skills/watch-ci/SKILL.md

@@ -1,47 +1,47 @@
----
-name: watch-ci
-description: Watch a GitHub Actions workflow, auto-fix failures via the agent pipeline (log-reader-copilot → triage-copilot → investigate-copilot → code-copilot), and re-trigger until green. Accepts nothing (current-branch PR), a PR number, or a PR/workflow-run/workflow-file URL.
----
-
-You are the watch-ci orchestrator. Drive the CI fix loop until the target workflow is green.
-
-## Target resolution
-
-Parse the optional input argument:
-- **Empty** → look up the current-branch PR with `gh pr view`.
-- **Digits only** → treat as a PR number on the current repo.
-- **URL containing `/pull/<n>`** → PR URL; extract `owner/repo` from the URL and pass `--repo owner/repo` to all `gh` calls.
-- **URL containing `/actions/runs/<id>`** → direct run URL; extract the run ID and `owner/repo`.
-- **URL containing `/actions/workflows/<file>`** or **`/blob/<ref>/.github/workflows/<file>`** → workflow-file URL; extract `owner/repo` and the workflow file name.
-
-## Trigger-type detection
-
-After identifying the failing workflow file, fetch its `on:` block and classify:
-
-| `on:` block | Trigger type | Re-trigger method |
-|---|---|---|
-| Contains `push` or `pull_request` | auto-on-push | Commit and push on the feature branch |
-| Contains `workflow_dispatch` (without push/PR) | manual-dispatch | `gh workflow run <file> --repo owner/repo` |
-| Only `schedule` | scheduled-only | **Stop** — cannot force; report the fix to the user |
-| Anything else | manual-dispatch | `gh workflow run <file> --repo owner/repo` |
-
-## Fix loop (max 5 iterations)
-
-Repeat until green or 5 iterations reached:
-
-1. **Collect** — invoke the `log-reader-copilot` agent to gather logs and produce a structured diagnostic report.
-2. **Triage** — invoke the `triage-copilot` agent with the diagnostic report; receive EASY or HARD classification.
-3. **Investigate** (HARD only) — invoke the `investigate-copilot` agent with the diagnostic report and triage output; receive a root-cause analysis and fix strategy.
-4. **Fix** — invoke the `code-copilot` agent with the triage fix suggestion (EASY) or investigate fix strategy (HARD) to apply the change.
-5. **Commit & push** — commit the fix on the current feature branch and push; never push to `main`.
-6. **Re-trigger** — use the trigger method determined above.
-7. **Wait** — poll `gh run watch` until the new run completes.
-8. If still failing, go to step 1.
-
-After 5 iterations without green, stop and report the current state and last error to the user.
-
-## Guardrails
-- Never push to `main`.
-- Never force-push.
-- Never use `--no-verify`.
-- For remote-repo targets this agent cannot edit locally: diagnose, propose the fix, and report back to the user without pushing.
+---
+name: watch-ci
+description: Watch a GitHub Actions workflow, auto-fix failures via the agent pipeline (log-reader-copilot → triage-copilot → investigate-copilot → code-copilot), and re-trigger until green. Accepts nothing (current-branch PR), a PR number, or a PR/workflow-run/workflow-file URL.
+---
+
+You are the watch-ci orchestrator. Drive the CI fix loop until the target workflow is green.
+
+## Target resolution
+
+Parse the optional input argument:
+- **Empty** → look up the current-branch PR with `gh pr view`.
+- **Digits only** → treat as a PR number on the current repo.
+- **URL containing `/pull/<n>`** → PR URL; extract `owner/repo` from the URL and pass `--repo owner/repo` to all `gh` calls.
+- **URL containing `/actions/runs/<id>`** → direct run URL; extract the run ID and `owner/repo`.
+- **URL containing `/actions/workflows/<file>`** or **`/blob/<ref>/.github/workflows/<file>`** → workflow-file URL; extract `owner/repo` and the workflow file name.
+
+## Trigger-type detection
+
+After identifying the failing workflow file, fetch its `on:` block and classify:
+
+| `on:` block | Trigger type | Re-trigger method |
+|---|---|---|
+| Contains `push` or `pull_request` | auto-on-push | Commit and push on the feature branch |
+| Contains `workflow_dispatch` (without push/PR) | manual-dispatch | `gh workflow run <file> --repo owner/repo` |
+| Only `schedule` | scheduled-only | **Stop** — cannot force; report the fix to the user |
+| Anything else | manual-dispatch | `gh workflow run <file> --repo owner/repo` |
+
+## Fix loop (max 5 iterations)
+
+Repeat until green or 5 iterations reached:
+
+1. **Collect** — invoke the `log-reader-copilot` agent to gather logs and produce a structured diagnostic report.
+2. **Triage** — invoke the `triage-copilot` agent with the diagnostic report; receive EASY or HARD classification.
+3. **Investigate** (HARD only) — invoke the `investigate-copilot` agent with the diagnostic report and triage output; receive a root-cause analysis and fix strategy.
+4. **Fix** — invoke the `code-copilot` agent with the triage fix suggestion (EASY) or investigate fix strategy (HARD) to apply the change.
+5. **Commit & push** — commit the fix on the current feature branch and push; never push to `main`.
+6. **Re-trigger** — use the trigger method determined above.
+7. **Wait** — poll `gh run watch` until the new run completes.
+8. If still failing, go to step 1.
+
+After 5 iterations without green, stop and report the current state and last error to the user.
+
+## Guardrails
+- Never push to `main`.
+- Never force-push.
+- Never use `--no-verify`.
+- For remote-repo targets this agent cannot edit locally: diagnose, propose the fix, and report back to the user without pushing.

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Marco Petralia
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Marco Petralia
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,117 +1,116 @@
-# marcos-ai-bootstrap
-
-AI tools for doing work. No overcomplications.
-
-Tool-agnostic agent/skill network that is built around a basic flow of plan -> implement -> deploy -> fix -> deploy etc.
-
-Currently supporting **Claude Code**, **Codex**, and **GitHub Copilot CLI** but easily adjustable to fit your workflow.
-
-See [`HUMAN.md`](./HUMAN.md) for the day-to-day workflow once the network is set up.
-
-## Quick start: the `marcos-ai-bootstrap` CLI
-
-The fastest way to bring this agent network into any repository — no AI turn required,
-works the same on Windows/Mac/Linux, and doesn't care whether the target project is
-Node, Python, Go, or anything else:
-
-```bash
-npx marcos-ai-bootstrap --copilot        # GitHub Copilot CLI agents + skills
-npx marcos-ai-bootstrap --claude         # Claude Code agents + skills
-npx marcos-ai-bootstrap --codex          # Codex agents + skills
-npx marcos-ai-bootstrap --claude --codex # combine any subset
-npx marcos-ai-bootstrap --all            # every tool at once
-```
-
-Run it from the root of the repository you want to bootstrap. It writes `AGENTS.md`
-and `HUMAN.md` (the tool-agnostic rules + human guide) alongside
-the agent/skill files for whichever tool(s) you selected:
-
-| Flag | Writes |
-|---|---|
-| `--claude` | `.claude/agents/*.md`, `.claude/skills/**/SKILL.md`, `CLAUDE.md` (`@AGENTS.md` stub) |
-| `--codex` | `.codex/agents/*.toml`, `.agents/skills/**/SKILL.md` |
-| `--copilot` | `.github/agents/*.agent.md`, `.github/skills/**/SKILL.md`, `.github/copilot-instructions.md` |
-| `--all` | all of the above |
-
-### Options
-
-| Flag | Effect |
-|---|---|
-| `--dest <path>` | Target directory (default: current working directory) |
-| `--force` | Overwrite files that already exist (default: skip existing files) |
-| `--dry-run` | Print what would be written without touching disk |
-| `-h`, `--help` | Show usage |
-
-Existing files are never clobbered unless you pass `--force`, so it's safe to re-run
-`marcos-ai-bootstrap` in a repo that already has some of the network materialised (e.g. to add
-`--codex` support to a repo that only had `--copilot` before).
-
-### Installing globally instead of via `npx`
-
-```bash
-npm install -g marcos-ai-bootstrap
-marcos-ai-bootstrap --all
-```
-
-## Repository layout
-
-- `src/AGENTS.md`, `src/HUMAN.md` — the **canonical, shipped** copies. These are the source
-  of truth the CLI reads and writes into target repos (as root-level `AGENTS.md`/`HUMAN.md`).
-- `AGENTS.md`, `HUMAN.md` (repo root) — this repository's **own self-hosting** copies, used
-  by the agent network running against this repo. Kept separate from the shipped `src/` copies
-  and not published to npm.
-- `.claude/`, `.codex/`, `.github/`, `.agents/` — the already-materialised, checked-in
-  agent/skill files for this repo itself, and the templates the `marcos-ai-bootstrap` CLI ships
-  and copies into other repositories.
-- `src/bin/ai-bootstrap.js`, `src/lib/materialize.js` — the CLI implementation.
-- `src/AGENTS-BOOTSTRAP.md` — maintainer-only source of truth for each tool's
-  materialised agent/skill prompt bodies, model tier mappings, and MCP server
-  discovery/policy flow. **Not published to npm and not copied into target repos** —
-  the materialised agent/skill files under `.claude/`, `.codex/`, `.github/`, `.agents/`
-  are the shipped source of truth.
-- `src/extract-agents.py` — maintainer tool: regenerates the `.claude/`, `.codex/`,
-  `.github/`, `.agents/` template files at the repo root from `src/AGENTS-BOOTSTRAP.md`
-  after editing it. Run this after changing `src/AGENTS-BOOTSTRAP.md`, then commit the
-  regenerated templates so `marcos-ai-bootstrap` ships the update.
-
-## Maintaining this repo
-
-1. Edit `src/AGENTS-BOOTSTRAP.md` (the source of truth for agent/skill prompt bodies).
-2. Run `python src/extract-agents.py` to regenerate the materialised template files.
-3. Run `node src/bin/ai-bootstrap.js --all --dry-run --dest <scratch-dir>` to sanity-check
-   the CLI still packages everything correctly.
-4. Commit the changes.
-
-## Releasing to npm
-
-Releases are automated with [release-please](https://github.com/googleapis/release-please)
-via `.github/workflows/release.yml`, so no one commits a version bump or pushes to `main`
-directly.
-
-How it works:
-
-1. On every push to `main`, release-please opens/updates a **Release PR** that bumps the
-   version in `package.json` and updates `CHANGELOG.md`, based on the conventional-commit
-   messages since the last release.
-2. When you're ready to ship, **merge the Release PR**. That merge creates the git tag and
-   a GitHub Release.
-3. The same workflow then publishes to npm with `npm publish --provenance --access public`
-   using OIDC **trusted publishing** (no stored `NPM_TOKEN`).
-
-Bump size is derived from your commit messages:
-
-| Commit type | Result |
-|---|---|
-| `fix:` / `chore:` / `refactor:` … | patch (`0.0.1`) |
-| `feat:` … | minor |
-| `feat!:` or a `BREAKING CHANGE:` footer | major |
-| any commit with a `Release-As: X.Y.Z` footer | forces exactly that version |
-
-So the default cadence is a patch per batch of merged fixes; larger releases happen simply
-by using `feat:` or a breaking-change marker. Non-releasable commits (e.g. `docs:`, `ci:`)
-won't create a Release PR on their own.
-
-**One-time setup on npmjs.com:** configure this repository and the `Release` workflow as a
-[trusted publisher](https://docs.npmjs.com/trusted-publishers) for the `marcos-ai-bootstrap`
-package so OIDC auth works without a token. Also enable "Allow GitHub Actions to create and
-approve pull requests" in the repo's Actions settings so release-please can open the Release PR.
+# marcos-ai-bootstrap
+
+AI tools for doing work. No overcomplications.
+
+Tool-agnostic agent/skill network that is built around a basic flow of plan -> implement -> deploy -> fix -> deploy etc.
+
+Currently supporting **Claude Code**, **Codex**, and **GitHub Copilot CLI** but easily adjustable to fit your workflow.
+
+See [`HUMAN.md`](./HUMAN.md) for the day-to-day workflow once the network is set up.
+
+## Quick start: the `marcos-ai-bootstrap` CLI
+
+The fastest way to bring this agent network into any repository — no AI turn required,
+works the same on Windows/Mac/Linux, and doesn't care whether the target project is
+Node, Python, Go, or anything else:
+
+```bash
+npx marcos-ai-bootstrap --copilot        # GitHub Copilot CLI agents + skills
+npx marcos-ai-bootstrap --claude         # Claude Code agents + skills
+npx marcos-ai-bootstrap --codex          # Codex agents + skills
+npx marcos-ai-bootstrap --claude --codex # combine any subset
+npx marcos-ai-bootstrap --all            # every tool at once
+```
+
+Run it from the root of the repository you want to bootstrap. It writes `AGENTS.md`
+and `HUMAN.md` (the tool-agnostic rules + human guide) alongside
+the agent/skill files for whichever tool(s) you selected:
+
+| Flag | Writes |
+|---|---|
+| `--claude` | `.claude/agents/*.md`, `.claude/skills/**/SKILL.md`, `CLAUDE.md` (`@AGENTS.md` stub) |
+| `--codex` | `.codex/agents/*.toml`, `.agents/skills/**/SKILL.md` |
+| `--copilot` | `.github/agents/*.agent.md`, `.github/skills/**/SKILL.md`, `.github/copilot-instructions.md` |
+| `--all` | all of the above |
+
+### Options
+
+| Flag | Effect |
+|---|---|
+| `--dest <path>` | Target directory (default: current working directory) |
+| `--force` | Overwrite files that already exist (default: skip existing files) |
+| `--dry-run` | Print what would be written without touching disk |
+| `-h`, `--help` | Show usage |
+
+Existing files are never clobbered unless you pass `--force`, so it's safe to re-run
+`marcos-ai-bootstrap` in a repo that already has some of the network materialised (e.g. to add
+`--codex` support to a repo that only had `--copilot` before).
+
+### Installing globally instead of via `npx`
+
+```bash
+npm install -g marcos-ai-bootstrap
+marcos-ai-bootstrap --all
+```
+
+## Repository layout
+
+- `src/AGENTS.md`, `src/HUMAN.md` — the **canonical, shipped** copies. These are the source
+  of truth the CLI reads and writes into target repos (as root-level `AGENTS.md`/`HUMAN.md`).
+- `AGENTS.md`, `HUMAN.md` (repo root) — this repository's **own self-hosting** copies, used
+  by the agent network running against this repo. Kept separate from the shipped `src/` copies
+  and not published to npm.
+- `.claude/`, `.codex/`, `.github/`, `.agents/` — the already-materialised, checked-in
+  agent/skill files for this repo itself, and the templates the `marcos-ai-bootstrap` CLI ships
+  and copies into other repositories.
+- `src/bin/ai-bootstrap.js`, `src/lib/materialize.js` — the CLI implementation.
+- `src/AGENTS-BOOTSTRAP.md` — maintainer-only source of truth for each tool's
+  materialised agent/skill prompt bodies, model tier mappings, and MCP server
+  discovery/policy flow. **Not published to npm and not copied into target repos** —
+  the materialised agent/skill files under `.claude/`, `.codex/`, `.github/`, `.agents/`
+  are the shipped source of truth.
+- `src/extract-agents.py` — maintainer tool: regenerates the `.claude/`, `.codex/`,
+  `.github/`, `.agents/` template files at the repo root from `src/AGENTS-BOOTSTRAP.md`
+  after editing it. Run this after changing `src/AGENTS-BOOTSTRAP.md`, then commit the
+  regenerated templates so `marcos-ai-bootstrap` ships the update.
+
+## Maintaining this repo
+
+1. Edit `src/AGENTS-BOOTSTRAP.md` (the source of truth for agent/skill prompt bodies).
+2. Run `python src/extract-agents.py` to regenerate the materialised template files.
+3. Run `node src/bin/ai-bootstrap.js --all --dry-run --dest <scratch-dir>` to sanity-check
+   the CLI still packages everything correctly.
+4. Commit the changes.
+
+## Releasing to npm
+
+Releases are automated with [release-please](https://github.com/googleapis/release-please)
+via `.github/workflows/release.yml`, so no one commits a version bump or pushes to `main`
+directly.
+
+How it works:
+
+1. On every push to `main`, release-please opens/updates a **Release PR** that bumps the
+   version in `package.json` and updates `CHANGELOG.md`, based on the conventional-commit
+   messages since the last release.
+2. When you're ready to ship, **merge the Release PR**. That merge creates the git tag and
+   a GitHub Release.
+3. The same workflow then publishes to npm with `npm publish --provenance --access public`
+   using OIDC **trusted publishing** (no stored `NPM_TOKEN`).
+
+The published package appears at
+[npmjs.com/package/marcos-ai-bootstrap](https://www.npmjs.com/package/marcos-ai-bootstrap).
+
+Bump size is derived from your commit messages. While the package is pre-1.0, the config
+(`bump-minor-pre-major`, `bump-patch-for-minor-pre-major`) keeps breaking changes off the
+major version:
+
+| Commit type | Result (pre-1.0) |
+|---|---|
+| `fix:` / `feat:` / `refactor:` … | patch (e.g. `0.1.0` → `0.1.1`) |
+| `feat!:` or a `BREAKING CHANGE:` footer | minor (e.g. `0.1.0` → `0.2.0`) |
+| any commit with a `Release-As: X.Y.Z` footer | forces exactly that version |
+
+Cut `1.0.0` with a `Release-As: 1.0.0` commit when the API is stable; after that, standard
+SemVer applies (`feat:` → minor, breaking → major). Non-releasable commits (e.g. `docs:`,
+`ci:`) won't create a Release PR on their own.

package/package.json

@@ -1,37 +1,37 @@
-{
-  "name": "marcos-ai-bootstrap",
-  "version": "0.1.0",
-  "description": "Materialise the AI-Bootstrap agent/skill network (Claude Code, Codex, GitHub Copilot CLI) into any repository from the command line.",
-  "bin": {
-    "marcos-ai-bootstrap": "src/bin/ai-bootstrap.js"
-  },
-  "main": "src/lib/materialize.js",
-  "files": [
-    "src/bin",
-    "src/lib",
-    "src/AGENTS.md",
-    "src/HUMAN.md",
-    ".claude",
-    ".codex",
-    ".agents",
-    ".github/agents",
-    ".github/skills"
-  ],
-  "engines": {
-    "node": ">=16"
-  },
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/marcorpetralia/marcos-ai-bootstrap"
-  },
-  "keywords": [
-    "ai",
-    "agents",
-    "copilot",
-    "claude",
-    "codex",
-    "bootstrap",
-    "cli"
-  ]
-}
+{
+  "name": "marcos-ai-bootstrap",
+  "version": "0.1.2",
+  "description": "Materialise the AI-Bootstrap agent/skill network (Claude Code, Codex, GitHub Copilot CLI) into any repository from the command line.",
+  "bin": {
+    "marcos-ai-bootstrap": "src/bin/ai-bootstrap.js"
+  },
+  "main": "src/lib/materialize.js",
+  "files": [
+    "src/bin",
+    "src/lib",
+    "src/AGENTS.md",
+    "src/HUMAN.md",
+    ".claude",
+    ".codex",
+    ".agents",
+    ".github/agents",
+    ".github/skills"
+  ],
+  "engines": {
+    "node": ">=16"
+  },
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/marcorpetralia/marcos-ai-bootstrap"
+  },
+  "keywords": [
+    "ai",
+    "agents",
+    "copilot",
+    "claude",
+    "codex",
+    "bootstrap",
+    "cli"
+  ]
+}