skillpacks 0.1.0

package/packs/project-fleet/claude/clone-spec-store/archive/v0.0/SKILL.md

@@ -0,0 +1,262 @@
+---
+name: clone-spec-store
+description: Build a canonical lawful-functional-parity spec store for N software ideas in any domain, then use portfolio gates to seed only implementation-ready or explicit scaffold-only downstream repos.
+type: planning
+version: v0.0
+argument-hint: "[--domain <label>] [--count <N>] [--owner <github-owner>] [--repo-slug-suffix <suffix>]"
+---
+
+# Clone Spec Store
+
+Produce a canonical specification store for N "clone" software ideas, then move selected ideas through a portfolio-gated downstream implementation pipeline using lawful functional-parity research only. Works for any software domain — mobile apps, web apps, desktop apps, CLIs, devtools, games, services, libraries.
+
+This skill generalizes the `GeorgeQLe/mobile-ideas` pattern, but corrects the default operating model: broad exploration is cheap, while implementation-ready specs, downstream repos, and active builds are gated portfolio assets.
+
+## Invocation
+
+Default arguments (ask the user only if missing):
+
+- `--domain`: human label for the target software class. Examples: `mobile apps`, `web apps`, `CLI tools`, `Obsidian plugins`, `VS Code extensions`, `indie games`, `SaaS products`, `Rust crates`. Default: `mobile apps`.
+- `--count`: number of ideas. Default: `100`. Must be ≥1.
+- `--owner`: GitHub owner (user or org) for downstream repos. Required before Phase 6 execution.
+- `--repo-slug-suffix`: suffix for each downstream repo name. Default derived from domain: mobile apps → `-mobile-clone`, web apps → `-web-clone`, CLI tools → `-cli-clone`, games → `-game-clone`, generic → `-clone`.
+
+If the user says "like `GeorgeQLe/mobile-ideas`" or similar, mirror that pipeline exactly with substituted tokens.
+
+## Guardrails (apply throughout)
+
+- **Lawful functional parity only.** Reproduce workflows, interaction models, data contracts, and edge cases — never copy proprietary source code, private APIs, trademarks as branding, logos, screenshots, store media, copyrighted content, paywalled content, production credentials, or real user data.
+- **Non-affiliation.** Every artifact must explicitly state the project is independent and not affiliated with, endorsed by, sponsored by, certified by, or connected to the inspiration product owner.
+- **Manual verification blockers.** Any behavior requiring a real account, paid subscription, regional availability, device permission, regulated sandbox, physical hardware, or sensitive-data handling stays marked blocked until lawful hands-on evidence exists.
+- **Downstream repos private by default.** No `--public` visibility until the downstream repo has original code, original assets, and passes its own legal/name/license/attribution review.
+- **Spec-ready seeding by default.** Do not seed downstream repos until the source spec is implementation-ready unless the item is explicitly marked `scaffold-only`.
+- **Portfolio caps before implementation.** Do not move a seeded item into active build work unless it is `spec-ready` and fits the active-build cap recorded by the fleet workflow.
+- **Spec store private until release approved.** The top-level spec store stays private until the open-source checklist is complete and publication is explicitly approved.
+- **Category-specific risk review** for finance, health, location, marketplace, communications, media, minors, smart-home, education, security, identity.
+
+## Pipeline (Six Phases)
+
+Execute phases in order. Mark each phase complete in `tasks/roadmap.md` before advancing.
+
+### Phase 1 — Backlog and Draft 0
+
+1. Create repo scaffold:
+   - `CLAUDE.md` — project conventions (copy structure below).
+   - `README.md` — purpose, repo map, legal scope.
+   - `tasks/ideas.md` — backlog table of N ideas.
+   - `tasks/roadmap.md` — six-phase plan.
+   - `tasks/history.md`, `tasks/todo.md` — lifecycle docs.
+   - `specs/README.md` — spec index.
+2. Brainstorm N inspiration products in `--domain` ranked by public visibility (public marketplace rankings, community lists, public download counts). Record each as a row in `ideas.md` with columns: `#`, `Inspiration`, `Category`, `Clone-Spec Focus`, `Planning Prompt`.
+3. Create Draft 0 specs under `specs/batch-XX/NNN-<slug>.md` (20 per batch). One H1, one-paragraph summary, placeholder sections — enough to reserve IDs.
+4. Record Draft 0 gaps in `tasks/spec-quality-audit.md`.
+
+### Phase 2 — Draft 1 Normalization
+
+Rewrite every spec to canonical sections (exactly one H1, stable Markdown headings):
+
+```
+# <Original Project Name>-Style Clone Spec
+
+> Metadata
+> - Inspiration: <product>
+> - Category: <category>
+> - Readiness status: <Draft 1 | Implementation-ready as of YYYY-MM-DD>
+> - Verification basis: <public sources used>
+> - Manual verification blockers: <blockers>
+> - Legal scope: functional parity only; original code, brand, copy, assets, integrations.
+
+## Overview
+## Goals
+## Non-Goals
+## Research Sources        (table: Source | Exact URL | Evidence Used | Status)
+## Detailed Design
+## Core User Journeys
+## Screen Inventory        (or "Surface Inventory" for non-GUI domains; table: Surface | Purpose | Inputs | Required States | Edge/Failure)
+## Data Model
+## API And Backend Contracts
+## Realtime, Push, And Offline Behavior   (or "Runtime And Offline Behavior")
+## Permissions, Privacy, And Safety
+## Analytics And Monetization
+## Edge Cases
+## Test Plan
+## Acceptance Criteria
+## Open Questions
+## Build Plan
+## Next Steps
+```
+
+Validate: exactly one H1 per file, every ID `001`–`NNN` present, every spec has Research Sources, Open Questions, Next Steps.
+
+### Phase 3 — Portfolio Scoring And Implementation Readiness
+
+Score candidates before deepening all specs. Use project-specific criteria when present; otherwise score implementation leverage, demo value, legal/provider risk, reusable components, data/API availability, user or market signal, and build cost. Mark each item as `candidate`, `shortlisted`, `archived`, or `blocked`.
+
+For shortlisted specs, upgrade to implementation-ready:
+
+- Replace any discovery link with exact first-party URLs (official marketplace listing, vendor help center, policy pages, official docs).
+- Distinguish verified behavior from inferred requirements.
+- Enumerate concrete screens/surfaces, data entities, API routes, permissions, subscription states, edge cases, analytics events, test matrix, and build plan phases.
+- Add category-specific risk review notes where applicable.
+- Mark blocked flows with explicit owner/path for later verification.
+
+Pilot one app first (e.g., the most architecturally-teaching example), then extend the same structure to the top scored candidates in batches. The pilot becomes the reference template for the other specs. Do not treat N implementation-ready specs as required unless the user explicitly wants a complete spec encyclopedia rather than a portfolio funnel.
+
+### Phase 4 — Downstream Planning Pilot And Active Cap
+
+- Pick one top-scored, implementation-ready candidate from the backlog.
+- Produce a build plan inside its spec: route map, API schema, data model, seed-data policy, test checklist.
+- Create the first downstream implementation repo manually (private) and seed it with the source spec copy plus `tasks/roadmap.md` + `tasks/todo.md`.
+- Use this pilot to finalize the downstream seed template.
+- Record the active-build cap. Default to 5 active downstream repos if the project has no explicit cap.
+
+### Phase 5 — Portfolio Implementation Queue
+
+Populate `tasks/roadmap.md` Phase 5 with a portfolio queue table:
+
+```
+| ID | <Product> | State | Score | Source Spec | Downstream Repo | Next Milestone |
+```
+
+Each row references `specs/batch-XX/NNN-<slug>.md` and records whether the item is `candidate`, `shortlisted`, `spec-ready`, `seeded`, `active-build`, `shipped`, `archived`, or `blocked`. Purpose: the fleet workflow can select the next highest-return item without re-reading the whole spec store.
+
+### Phase 6 — Downstream Repo Seeding And Spec-Store Release
+
+1. **Manifest.** Create `tasks/repo-seeding.md` with a `## Per-Repo Checklist` table for `spec-ready` targets and explicit `scaffold-only` exceptions:
+   ```
+   | Done | ID  | App | State | Target Repo | Source Spec | Gate |
+   | :--: | :-: | --- | ----- | ----------- | ----------- | ---- |
+   | [ ]  | 001 | ... | spec-ready | `<owner>/<slug><suffix>` | `specs/batch-01/001-<slug>.md` | spec-ready |
+   ```
+   Include a `### Failures And Blockers` subsection and a `## Open-Source Spec Store Checklist`.
+
+2. **Templates** under `templates/downstream/`:
+   - `README.md` with placeholders: `{{PROJECT_NAME}}`, `{{PROJECT_SUMMARY}}`, `{{APP_ID}}`, `{{APP_NAME}}`, `{{TARGET_REPO}}`, `{{SOURCE_SPEC_PATH}}`, `{{SOURCE_SPEC_FILENAME}}`, `{{SOURCE_SPEC_STORE_URL}}`, `{{NON_AFFILIATION_NOTICE}}`, `{{LEGAL_SCOPE}}`, `{{ORIGINAL_ASSETS_REQUIREMENT}}`, `{{MANUAL_VERIFICATION_BLOCKERS}}`.
+   - `docs/plans/README.md` — empty phase-plan scaffold.
+   - `tasks/roadmap.md` — three-phase downstream roadmap (Plan → Build → Parity Review).
+   - `tasks/todo.md` — executable Phase 1 tasks.
+   - `.gitignore` — stack-neutral defaults.
+
+3. **Seeding utility** at `scripts/seed-downstream-repos.mjs`:
+   - Parses `tasks/repo-seeding.md` manifest, validating every listed row.
+   - Single-target only (`--target <id|app|owner/repo>`); batch creation is intentionally unsupported.
+   - Modes: `--dry-run` (writes preview dir, prints exact `gh`/`git` commands, never runs remote); `--execute` (checks `gh auth status`, refuses `--public`/`--visibility public`/`--all`, creates private via `gh repo create … --private --clone=false`, clones, seeds, commits, pushes).
+   - Refuses existing target repos unless `--reconcile-existing` is supplied.
+   - Refuses non-`spec-ready` rows unless the manifest gate is explicitly `scaffold-only`.
+   - Extracts `Manual verification blockers` and `Legal scope` from the source-spec metadata block to fill placeholders.
+   - Fails fast on unresolved `{{PLACEHOLDER}}` tokens.
+   - Appends failure evidence to `### Failures And Blockers` unless `--no-record-blockers`.
+
+4. **Execution order:**
+   - Step 6.1: Audit manifest.
+   - Step 6.2: Add templates.
+   - Step 6.3: Add seeding utility, run local dry-run on one low-risk non-pilot target.
+   - Step 6.4: Add public-release docs to spec store (`README.md`, `LICENSE` — CC BY 4.0 recommended for docs with explicit exclusions for third-party marks/media/APIs/data, `CONTRIBUTING.md`, `SECURITY.md`).
+   - Step 6.5: Run one private non-pilot dry-run seed end-to-end. Record created repo URL, seeded files, commit SHA.
+   - Step 6.6: Reconcile the Phase 4 pilot repo with the shared seed structure.
+   - Step 6.7: Seed remaining eligible repos in controlled private batches. Stop on any auth/permission/naming/rate-limit/template-validation failure and record the blocker.
+   - Step 6.8: Verify every target repo either exists privately with expected seeded files and source-spec backlink, or has an explicit blocker note. Confirm no downstream repo is public and no proprietary assets were seeded.
+   - Step 6.9: Spec-store publication — complete the open-source checklist (license, README scope, contribution policy, non-affiliation, content audit for secrets/assets/proprietary copy/private APIs/ambiguous affiliation) and run `gh repo edit <owner>/<spec-store-repo> --visibility public` only after explicit user approval.
+   - Step 6.10: Route ongoing queue execution through the fleet workflow so scoring, active-build caps, blockers, and runnable milestones govern future work.
+
+## Canonical CLAUDE.md (spec store)
+
+Use this structure (substitute domain):
+
+```
+# <Domain> Ideas Project Conventions
+
+## Overview
+Planning and specification workspace for <domain> clone ideas. Not runtime code.
+
+## Goals
+- Lawful backlog of <domain> clone ideas.
+- Turn each idea into a detailed technical specification before implementation.
+- `tasks/` for planning; `specs/` for specifications.
+- Preserve distinction between public-source research, inferred requirements, and hands-on verified behavior.
+
+## Non-Goals
+- No runtime app code here.
+- No proprietary source code, private APIs, trademarks, logos, screenshots, copyrighted media, paywalled content, or unlicensed datasets.
+- Do not treat inferred product behavior as verified one-for-one clone requirements.
+
+## Detailed Design
+- "Clone" = lawful functional parity with original implementation and original assets.
+- Every numbered spec must include source orientation, legal scope, privacy/safety, edge cases, test plan, acceptance criteria, open questions, next steps.
+- Every source-discovery link must be replaced with exact first-party URLs before implementation.
+- Account-, subscription-, region-, permission-, hardware-, or regulator-gated behavior stays blocked until verified.
+- Generated docs must use one H1 and stable Markdown headings.
+
+## Test Plan
+- Run hygiene checks after structural doc changes.
+- Run spec-structure checks after bulk spec rewrites.
+- Verify every numbered spec has canonical sections and one H1.
+```
+
+## Domain Adaptation Notes
+
+- **Mobile apps / desktop apps / web apps**: use "Screen Inventory"; include iOS/Android/OS platform sections; map permission prompts, push, offline, store listings.
+- **CLI tools / devtools / libraries**: rename "Screen Inventory" → "Command/Surface Inventory"; replace "Push/Offline" with "Runtime/Error-Handling Behavior"; add "CLI Contracts" (flag/subcommand matrix) and "Install/Distribution" sections.
+- **Games**: add "Core Loop", "Progression", "Content Pipeline"; keep "Screen Inventory" for menus/HUD.
+- **Services/APIs**: replace "Screen Inventory" with "Endpoint Inventory"; expand "API And Backend Contracts"; add "Deployment/Ops" section.
+- **Browser extensions / plugins**: add "Host Integration Points", "Permissions Manifest", "Marketplace Review Risk".
+
+In every case, keep: Metadata block, Research Sources, Goals/Non-Goals, Data Model, Permissions/Privacy/Safety, Edge Cases, Test Plan, Acceptance Criteria, Open Questions, Build Plan, Next Steps.
+
+## Process When Invoked
+
+1. Confirm `--domain`, `--count`, `--owner`, `--repo-slug-suffix`. Ask for any missing required values.
+2. Check if the current directory already has a partial pipeline (look for `tasks/ideas.md`, `specs/`, `tasks/repo-seeding.md`). Resume at the earliest incomplete phase rather than restarting.
+3. Work one phase at a time. After each phase: update `tasks/roadmap.md`, commit with a conventional message (`feat(seeding): complete Phase N step X.Y …`), push if `--owner` is configured.
+4. Never advance to Phase 6 remote execution without explicit user approval for each batch.
+5. Never flip the spec store to public visibility without explicit user approval.
+6. After Phase 5 exists and the user's request is about selecting candidates, continuing batches, enforcing active caps, repairing blockers, summarizing cross-repo status, or advancing downstream repos, route through the fleet workflow unless the requested change is clone/spec specific.
+
+## Reference Implementation
+
+The exact pattern this skill reproduces: `GeorgeQLe/mobile-ideas`. Key artifacts to mirror structurally:
+
+- `CLAUDE.md`, root `README.md`, `LICENSE`, `CONTRIBUTING.md`, `SECURITY.md`
+- `tasks/ideas.md`, `tasks/roadmap.md`, `tasks/repo-seeding.md`, `tasks/history.md`, `tasks/todo.md`, `tasks/spec-quality-audit.md`
+- `specs/batch-NN/NNN-<slug>.md` (20 per batch by convention; adjust if N ≠ 100)
+- `templates/downstream/{README.md,docs/plans/README.md,tasks/roadmap.md,tasks/todo.md,.gitignore}`
+- `scripts/seed-downstream-repos.mjs`
+
+If accessible, read those files for the exact wording and reuse structure verbatim with domain-appropriate substitutions.
+
+## Acceptance Criteria for the Skill Output
+
+- N ideas in `tasks/ideas.md`.
+- N numbered specs under `specs/batch-*/`, each with canonical sections; shortlisted specs have implementation-ready content before downstream build work.
+- `tasks/roadmap.md` with all six phases; Phase 5 table populated with all N portfolio rows, states, scores, source specs, downstream repo fields, and next milestones.
+- `tasks/repo-seeding.md` with eligible `spec-ready` rows and explicit `scaffold-only` exceptions, command pattern, open-source checklist, and blocker log.
+- `templates/downstream/` complete and placeholder-safe.
+- `scripts/seed-downstream-repos.mjs` passes a local dry-run for at least one target.
+- Private downstream repos exist only for eligible `spec-ready` rows or explicit `scaffold-only` exceptions, with source-spec copy and scaffolded planning docs, or explicit blocker notes in the manifest.
+- No proprietary assets committed anywhere. No public visibility changes without explicit user approval.
+
+## Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page at `alignment/clone-spec-store-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
+
+**Full content requirement.** The alignment page must contain the complete content of every proposed markdown deliverable -- every section, every finding, every detail, every list item. It is a thorough interactive review document, not a summary. Render the full deliverable content in clean, readable HTML with appropriate hierarchy, styling, and navigation. If the skill writes multiple scoped deliverables in one run, build one alignment page that contains all deliverables with anchor-linked navigation. Durable tracker artifacts, such as `research/assumption-tracker.md`, remain canonical markdown outputs but must also be fully rendered into the alignment page before approval.
+
+**Dark-mode styling.** Use a dark color scheme by default. Base CSS variables: `--bg: #0d1117; --surface: #161b22; --border: #30363d; --text: #c9d1d9; --text-muted: #8b949e; --accent: #58a6ff; --green: #3fb950; --red: #f85149; --orange: #d29922; --purple: #bc8cff;`. Apply `background: var(--bg); color: var(--text);` on body. Use `--surface` for cards, nav, and table headers. Use `--border` for all borders. Use `--purple` for question blocks and gate headings. Use `--accent` for links and section headings. Keep headings `color: #fff` or `var(--accent)` for hierarchy. Question block backgrounds should use `#1c2333`.
+
+**Alignment gates.** Treat gates as explicit review sections inside the HTML page. A gate blocks finalization until its required inline questions are answered and compiled into YAML. Include every gate that applies to the skill output, and include these gate types whenever relevant: evidence coverage, assumptions/confidence, scope/non-goals, candidate/verdict decisions, artifact destination, proposed file changes, coverage checkpoint, and post-approval route.
+
+**Report-only research gates.** For report-only or pre-approval research skills, the alignment page must explicitly contain evidence coverage, assumptions/confidence, recommended path, proposed file changes, and approval gates before any canonical research, spec, or task file is created or updated.
+
+
+**Required inline questions.** Each gate must contain at least one required inline question placed directly under the content it governs, inside a visually distinct question block. Each question must use radio-button inputs and include two standing options after the skill-generated choices: "Other / None of the above" backed by a multi-line text box for free-form input, and "Need clarification" backed by an optional notes box where the user can explain what is unclear. When any radio option other than "Other" or "Need clarification" is selected, show an optional "Additional notes" text box beneath it so the user can qualify their choice. Generate questions based on what genuinely needs user input -- do not add filler questions. Do not create a separate bottom "Decisions & Clarifications" section.
+
+**Gate YAML contract.** At the bottom of the page, include a "Compile Answers" button that aggregates answers from all inline gate questions throughout the page, including free-text notes. The button remains disabled until every required question has a selection, shows a count of remaining unanswered questions, and scrolls to the first unanswered question if clicked early. When every question is answered, generate a structured YAML block with one item per gate answer using this stable shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit "Copy YAML" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.
+
+**Pre-approval stop.** Before user approval, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide the compiled YAML answers. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after compiled YAML has been provided and the approved artifacts have been written or updated.
+
+**Diff highlighting on updates.** When the agent updates an existing alignment page after receiving compiled answers, highlight what changed since the previous version. The agent chooses inline annotation or side-by-side layout per situation.
+
+**Archiving.** Before replacing an existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/clone-spec-store-{topic}.html`.
+
+**Browser open.** Attempt to open the resulting HTML page in the browser and report whether the open succeeded or was blocked. A blocked browser-open attempt does not make the skill fail when the files were written correctly.
+

package/packs/project-fleet/claude/skill-inventory/ALIGNMENT-PAGE.md

@@ -0,0 +1,84 @@
+# Alignment Page — skill-inventory
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page at `alignment/skill-inventory-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
+
+**Visual rendering tier.** Each alignment page declares a rendering tier:
+- `document` (default) — text, tables, approval gates. No charts or interactive elements.
+- `visual` — adds inline charts, diagrams, and spatial layouts rendered via self-contained Canvas/SVG. Data is embedded as inline JSON. No external fetches.
+- `prototype` — adds functional interactive components (clickable flows, live CSS previews, drag interactions). Prototypes are ephemeral previews, not production code.
+
+The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected by the upgrade script). The bundled ALIGNMENT-PAGE.md receives tier-appropriate rendering guidance from the generator.
+
+**Alignment lifecycle.** Alignment pages have three lifecycle states. `review` is the draft/pre-approval page: it contains the complete deliverable preview, evidence, required inline gate questions, section feedback controls, feedback-only YAML, and final compile controls. `confirmed` is the post-approval page after the agent has consumed final compiled YAML, made any approved user-requested edits, and written or updated the approved canonical artifacts. A confirmed page is finished and current for the completed alignment cycle, but it remains amendable when later research changes or extends the conclusions. `amended` is a future revision of a confirmed page: archive the previous confirmed page first, mark what changed, preserve the prior approval record, and highlight the new evidence, decisions, or scope that changed the earlier conclusion.
+
+**Central alignment index.** When a research-producing skill writes or updates an HTML alignment page, also maintain the repository's central alignment index. Look for `alignment/index.html` at the repository root; if the target repo documents a different central alignment-index path, use that path and report it. If the index does not exist, create it as a self-contained HTML page that works from `file://`, links to every active `alignment/*.html` page except itself, and includes the newly written page. Every index entry must include the page's alignment date in a muted meta span after the link, formatted `YYYY-MM-DD`, for example `<a href="page.html">Title</a> <span class="meta">2026-06-09</span>`. The alignment date is the review or confirmed date written inside the page itself; new pages use today's date. If the index exists, update it instead of blindly appending: preserve valid existing entries, metadata, and entry dates; remove duplicate entries for the same page path; keep links repo-relative; and include the new or updated page. When updating an existing index, add a date only to entries that are missing one, deriving it from the page's internal alignment date, or from file history when the page has no internal date. If a `new` marker is used, combine it with the date as `<span class="meta">new · YYYY-MM-DD</span>`, and remove stale `new` markers from entries that are no longer the latest addition.
+
+**Alignment index categories.** The index groups alignment pages into five categories. Each alignment page belongs to exactly one category. When writing or updating the index, assign each page to a category and render the index grouped by category in the order listed below.
+
+1. **Research** (`research`) — market research, competitive analysis, investigative reports. Skill prefixes: `devtool-positioning`, `devtool-adoption`, `devtool-monetization`, `devtool-user-map`, `devtool-workflow`, `devtool-dx-journey`, `devtool-integration-map`, `deep-research`, `repo-glossary`.
+2. **Product Design & Spec** (`product-design`) — product scoping, idea briefs, design plans, specifications. Skill prefixes: `idea-scope-brief`, `fork-idea-branch`, `animation-design-planner`, `skills-showcase`, `skills-inventory`.
+3. **Utility & Maintenance** (`utility`) — diagnostics, triage, incident investigation, infrastructure maintenance. Skill prefixes: `investigate`, `session-triage`, `prompt-history-backfill`.
+4. **QA & Meta-Skill Improvement** (`qa-meta`) — code review, benchmarking, skill building/fixing, expert review. Skill prefixes: `expert-review`, `benchmark`, `targeted-skill-builder`, `devtool-docs-audit`.
+5. **Ops & Session Analysis** (`ops-analysis`) — operational intelligence, session history analysis, cost/token/workflow analysis. Skill prefixes: `analyze-sessions`, `canonical-workflow`, `run-batch`.
+
+**Category assignment rule.** Match the skill name that produced the alignment page against the prefix lists above; use the first matching category. When no prefix matches, read the page title and summary to assign the best-fit category. When the category is ambiguous, default to **Research**.
+
+**Visual tier badge.** When writing or updating the alignment index, display a visual tier badge next to each linked page: `[doc]` for document tier, `[visual]` for visual tier (pages with charts/diagrams), `[proto]` for prototype tier (interactive pages). Read the tier from the alignment page's `data-visual-tier` attribute on the `<html>` element. When the attribute is missing, default to `[doc]`.
+
+**Category data attribute.** Set `data-alignment-category` on the `<html>` element of each alignment page with the category slug (`research`, `product-design`, `utility`, `qa-meta`, or `ops-analysis`). Also set `data-visual-tier` on the `<html>` element with the rendering tier (`document`, `visual`, or `prototype`). When an existing alignment page lacks the attribute, infer the category from the skill-name prefix or page content and add it on the next update. The index should read this attribute when available; when it is missing, apply the prefix-matching rule to assign a category for display.
+
+**Category and product-path grouping.** In product-line or product-path repositories, identify product from `research/.progress.yaml` `product_paths[]`, active `research/{slug}/` or `specs/{slug}/` scopes, page metadata, page title, or the alignment page path. Group index entries by category first, then by product/product path within each category, with the repo's existing secondary sort preserved when clear. In flat repositories, group by category, then preserve the existing index organization within each category or use a clear newest-first or title order when creating a new index.
+
+**Research quality contract.** For research-producing outputs, do not synthesize research findings, recommendations, candidate rankings, or working packets until the user approves the research scope from the `review` alignment page's final compiled YAML. Before scope approval, do only minimal discovery needed to propose the research scope, source plan, assumptions, output paths, and approval questions; label any observed files or source availability as scope evidence, not findings. After scope approval, perform the synthesized research and separate and label `claims` (what the report concludes), `evidence` (source, repo artifact or file path, quote or observation, date, and confidence), `inference` (why that evidence supports the claim), `assumptions` (what remains unproven), and `decision impact` (what the user should approve, reject, or correct). Do not collapse evidence and inference into unsupported summary prose.
+
+**Embed prohibition.** Do not use `<object>`, `<iframe>`, `<embed>`, or "open working packet" / "view full document" links as the primary rendering of any proposed deliverable, evidence matrix, interview log, or manifest entry. The alignment page HTML must contain the rendered content directly. Embedded or linked external documents are permitted only as supplemental references alongside the fully rendered content already present in the page. **Exception:** Self-contained inline `<canvas>` and `<svg>` elements are permitted for charts and diagrams within the same HTML file.
+
+**Visual accessibility contract.** Every chart or diagram in a `visual` or `prototype` tier alignment page must include: (1) a `<table>` or text fallback rendering the same data, (2) an `aria-label` attribute on every `<canvas>` and `<svg>` element describing the chart type and data summary, and (3) a "View as table" toggle button that swaps between the chart and its table fallback. The toggle must default to showing the chart, with the table hidden via a `hidden` attribute that is toggled by the button.
+
+**Inline chart contract.** Visual and prototype tier pages must inline all chart rendering code as a `<script>` block within the HTML file. No external CDN references, relative file imports, or `<script src="...">` tags for chart libraries. Use the alignment chart snippet library (`scripts/alignment-chart-snippets.js`) as the reference implementation — copy the needed functions directly into the page's `<script>` block. Charts must read CSS variables (`--chart-1` through `--chart-8`) for colors and adapt to the dark-mode palette.
+
+**No context loss rule.** The alignment page must contain the complete content of every proposed markdown deliverable -- every section, every finding, every detail, every list item -- plus the decision-relevant substance from search logs, interview logs, source notes, repo scans, and approval notes. If a fact, source, caveat, uncertainty, alternative, rejected or lower-confidence finding, or decision rationale appears in a proposed deliverable or research log, it must either appear in the HTML page or be explicitly linked from the exact section that depends on it. The page is a thorough interactive review document, not a summary. Render the full deliverable content in clean, readable HTML with appropriate hierarchy, styling, and navigation. If the skill writes multiple scoped deliverables in one run, build one alignment page that contains all deliverables with anchor-linked navigation. Durable tracker artifacts, such as `research/assumption-tracker.md`, remain canonical markdown outputs but must also be fully rendered into the alignment page before approval.
+
+**Page layout contract.** After the page title and short summary, include a top-of-page "Table of Contents" section with anchor links to the major review sections and the bottom compile section. Keep the Table of Contents in normal document flow. Do not use a sidebar, side rail, drawer, split-shell layout, or sticky navigation for the Table of Contents unless the user explicitly asks for that layout. Do not place compile, copy, feedback, or answer controls in a sticky or fixed bottom banner/footer. Bottom compile controls must appear as ordinary content in a bottom compile section, so they scroll with the page and do not cover content at high zoom.
+
+**Research translation requirements.** For research outputs, the HTML page must include an evidence matrix, confidence/assumption register, alternatives considered, rejected or lower-confidence findings, source coverage gaps, and downstream implications. The evidence matrix must map each major claim to source or repo evidence, inference, confidence, assumption status, and decision impact. The confidence/assumption register must show which conclusions are evidence-backed, which are provisional, and what evidence would change them.
+
+**Dark-mode styling.** Use a dark color scheme by default. Base CSS variables: `--bg: #0d1117; --surface: #161b22; --border: #30363d; --text: #c9d1d9; --text-muted: #8b949e; --accent: #58a6ff; --green: #3fb950; --red: #f85149; --orange: #d29922; --purple: #bc8cff;`. Data visualization palette (for `visual` and `prototype` tier pages): `--chart-1: #58a6ff; --chart-2: #3fb950; --chart-3: #d29922; --chart-4: #bc8cff; --chart-5: #f85149; --chart-6: #79c0ff; --chart-7: #f0883e; --chart-8: #a5d6ff;`. Apply `background: var(--bg); color: var(--text);` on body. Use `--surface` for cards, the top Table of Contents, and table headers. Use `--border` for all borders. Use `--purple` for question blocks and gate headings. Use `--accent` for links and section headings. Keep headings `color: #fff` or `var(--accent)` for hierarchy. Question block backgrounds should use `#1c2333`.
+
+**Responsive layout.** Include `<meta name="viewport" content="width=device-width, initial-scale=1">` in the head. Use at most two breakpoints: `@media (max-width: 860px)` for tablet and `@media (max-width: 560px)` for phone. Wrap every `<table>` in a `<div style="overflow-x: auto">` so tables scroll horizontally instead of breaking layout. All interactive elements (buttons, radio labels, feedback controls) must have a minimum touch target of `44px` height and at least `10px 16px` padding. Use `rem` for font sizes and respect the user's base font size — do not set a fixed `font-size` on `html` or `body`. Flex containers that place a heading beside controls (`display: flex; justify-content: space-between`) must include `flex-wrap: wrap; gap: 8px` so controls drop below the heading on narrow screens. Grid layouts must use `minmax(min(210px, 100%), 1fr)` instead of bare `minmax(210px, 1fr)` to prevent horizontal overflow when the viewport is narrower than the minimum. Set `max-width: 100%; overflow-wrap: break-word;` on `main` and any fixed-width container so no element forces a horizontal scrollbar at any zoom level.
+
+**Alignment gates.** In `review` pages, treat gates as explicit review sections inside the HTML page. A gate blocks finalization only while the page is in `review`, until its required inline questions are answered and compiled into YAML. Include every gate that applies to the skill output, and include these gate types whenever relevant: evidence coverage, assumptions/confidence, scope/non-goals, candidate/verdict decisions, artifact destination, proposed file changes, coverage checkpoint, and post-approval route. In `confirmed` pages, preserve the gate decisions as read-only approval records instead of active approval controls.
+
+**Output gate semantics and de-duplication.** The `artifact destination` gate approves the durable or review artifact location, such as the alignment page, working packet, report, spec, plan, prototype, or document path. The `proposed file changes` gate approves downstream mutation scope, timing, and the allowed file set after review. Keep these as separate approval concepts. If both gate concepts ask only the same path-destination question, render one combined visual section such as `Artifact Destination & Proposed File Changes` instead of duplicating path-only sections. If the decisions differ, render separate gates. Do not duplicate YAML entries solely because one visual section title names both concepts: emit separate YAML items only when the page asked separate decisions, and keep each item's `gate_type` equal to the decision it controls (`artifact destination` or `proposed file changes`).
+
+**Research completeness gate.** For research outputs, include a research completeness gate with inline questions asking whether the evidence is sufficient for the recommendation, which claims need more support, and whether missing context could change the recommendation. Place these questions directly under the evidence matrix or recommendation section they govern.
+
+**Source coverage expectations.** For web research, organize source coverage by category rather than citation list alone; use categories such as competitors, pricing, user sentiment, positioning, integrations, and recent activity when relevant to the topic. For repo or codebase research, include file/path evidence and clearly distinguish observed code facts from inferred product, workflow, or user conclusions.
+
+**Report-only research gates.** For report-only or pre-approval research skills, the first `review` alignment page must explicitly contain proposed research scope, source plan, assumptions/confidence, recommended output path, proposed file changes, and approval gates before synthesized research begins and before any working packet, canonical research, spec, or task file is created or updated.
+
+**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-skill-inventory-research.md`; product-path mode uses `research/{slug}/_working/preliminary-skill-inventory-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Feedback-only YAML revises the working packet and review page, then remains in Stage 2. Stage 3 consumes final compiled YAML for artifact approval only when it has no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+
+**Required inline questions.** In `review` pages, each gate must contain at least one required inline question placed directly under the content it governs, inside a visually distinct question block. Each question must use radio-button inputs and include two standing options after the skill-generated choices: "Other / None of the above" backed by a multi-line text box for free-form input, and "Need clarification" backed by an optional notes box where the user can explain what is unclear. When any radio option other than "Other" or "Need clarification" is selected, show an optional "Additional notes" text box beneath it so the user can qualify their choice. Generate questions based on what genuinely needs user input -- do not add filler questions. Do not create a separate bottom "Decisions & Clarifications" section. Confirmed pages must not keep these as required input controls; render the answered decisions as read-only records.
+
+**Section feedback controls.** Every major section of the page (each deliverable section, evidence matrix, confidence register, gate, and any anchor-linked top-level heading) carries a lightweight section-feedback control near its heading: three mutually exclusive choices -- "emphasize" (add more weight to this section or to the point named in the notes), thumbs down (reject or flag a concern), and "clarification needed". Selecting any one reveals a multi-line section-feedback textarea placed directly under or beside that section's emphasize/down/clarify controls; deselecting hides the textarea and any local feedback YAML output for that section. This textarea is separate from required gate-question text inputs: even when the same section has gate questions with their own text boxes, selecting emphasize/down/clarify must still reveal the section-feedback textarea near the feedback controls. Use `--green` for active "emphasize", `--red` for the active thumbs-down, and `--orange` for active "clarification needed", with muted/inactive states otherwise. These controls are optional for final approval and do not replace required gate questions. They also power the separate feedback-only YAML path so the user can send emphasis requests, concerns, or clarification requests before answering every required gate question. When a section contains nested subsections (h3 or deeper), duplicate the section-feedback control at the bottom of the section, just before the closing `</section>` tag. The bottom copy mirrors the top copy — same `data-section`, same id with a `-bottom` suffix, same button set. Sections without nested subsections keep only the top control. Pair top and bottom controls by matching `data-section` attribute. When a feedback button is clicked on one copy, mirror the active state, `has-feedback` class, and `dataset.feedback` value to the paired copy. Textarea content should sync on compile — whichever textarea has content takes precedence (prefer the one the user last typed in). Both copies' local compile/copy buttons produce the same YAML. Use the top copy's `id` (without `-bottom`) as the canonical feedback id for YAML output.
+
+**Feedback-only YAML contract.** Provide feedback-only YAML in two places: locally under each selected section-feedback textarea, and globally in the bottom compile section. When a section-feedback control is selected, show local "Compile Feedback YAML" and "Copy YAML" controls plus a read-only YAML textarea directly under that section's feedback textarea. The local feedback compile generates YAML with `alignment_page: alignment/skill-inventory-{topic}.html`, `feedback_status: revision-request`, `approval_status: not-approved`, `unanswered_required_questions`, and a `section_feedback` list containing the single selected section-feedback entry for that local control. The bottom "Compile Feedback YAML" control generates the same YAML shape but aggregates every selected section-feedback entry on the page. Enable both local and bottom feedback compile controls as soon as at least one section-feedback control is set, even if required inline gate questions are unanswered. Populate `alignment_page` from the known repo-relative output path used to write the HTML page, not from the page title, browser URL, window location, or any display label. Each feedback entry uses the shape `section`, `feedback` (`emphasize`, `down`, or `needs-clarification`), optional `notes` from that section's feedback textarea, and `requested_agent_action` (`add-weight-to-section`, `investigate-and-revise`, or `clarify-before-approval`). For `emphasize` feedback, the YAML must make clear that the agent should add more weight, prominence, evidence, detail, or recommendation emphasis to that section or to the specific point named in the notes; this is a revision request, not approval of the section as-is. For `down` and `needs-clarification` feedback, the YAML must make clear that the agent should evaluate the feedback, investigate further when needed, and contextually amend the HTML alignment page before asking again for final approval answers. Automatically attempt to copy feedback YAML to the clipboard, display local or bottom copy status, display it in the matching read-only textarea, and provide a "Copy YAML" button with the same retry and fallback behavior as final gate YAML. Do not render the bottom feedback compile controls as a sticky or fixed banner.
+
+**Gate YAML contract.** In `review` pages, at the bottom of the page, include an ordinary in-flow compile section with a "Compile Feedback YAML" button for selected section feedback and a separate "Compile Answers" button for final approval answers. The bottom compile section must not be sticky, fixed, floating, or styled as a persistent banner. The "Compile Answers" button aggregates answers from all inline gate questions throughout the page, including free-text notes. The final approval button remains disabled until every required question has a selection, shows a count of remaining unanswered questions, and scrolls to the first unanswered question if clicked early. When every question is answered, generate a structured YAML block with `alignment_page: alignment/skill-inventory-{topic}.html`, `approval_status: ready-for-agent-review`, one item per gate answer using this stable shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. Populate `alignment_page` from the known repo-relative output path used to write the HTML page, not from the page title, browser URL, window location, or any display label. The same final compiled output also includes any section-feedback controls that the user set, using the `section_feedback` shape from the feedback-only YAML contract. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit "Copy YAML" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.
+
+**Confirmed page contract.** After final approval has been applied, convert the active alignment page from `review` to `confirmed`. Include a visible status block with `alignment_status: confirmed`, confirmation date, confirmed artifact paths, approval source summary, and explicit finished but amendable language: the page is current for the completed alignment cycle, and later research can amend it only by archiving the prior confirmed page and highlighting the amendment. Remove required gate-question controls, the final "Compile Answers" button, unanswered-question counters, disabled approval buttons, and approval-blocking language. Preserve the full research and approval record: answered decisions, user requests, evidence matrix, assumptions/confidence register, source gaps, proposed file changes, final compiled YAML or faithful approval summary, and what changed during confirmation. Keep research caveats visible; `confirmed` means approved/current, not immutable or permanently true.
+
+**Pre-approval stop.** While an alignment page is in `review`, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide either local or bottom feedback-only YAML for emphasis requests, concerns, or clarification, or final compiled YAML answers when ready. Do not require the user to answer every gate before sending emphasis requests, negative feedback, or clarification needs. When feedback-only YAML is provided, treat it as a revision request: evaluate the feedback, investigate further when needed, archive and amend the HTML page contextually, highlight the changes, and ask again for review. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after final compiled YAML has been provided and the approved artifacts have been written or updated.
+
+**After approval handling.** When final compiled YAML is provided, inspect it before confirming the page. If it contains approvals plus user-requested edits, first update the page, research, and proposed canonical artifacts to satisfy the request; then write or update the approved canonical artifacts and confirm the page. If it contains `needs-clarification`, unresolved `down` feedback, or any unresolved negative feedback, revise the page and return it to `review` instead of marking it `confirmed`. Before replacing any existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/skill-inventory-{topic}.html`. Future amendments to confirmed pages follow the same archive-first rule and must show what changed from the prior confirmed record.
+
+**Diff highlighting on updates.** When the agent updates an existing alignment page after receiving feedback, compiled answers, confirmation edits, or later amendment evidence, the rendered HTML must visibly indicate what changed since the previous version. Highlight changed sections or blocks in-place with a `Changed`/`Updated` badge, distinct border or background, `<ins>`/`<del>` markup, or a side-by-side before/after comparison when that is clearer. A top-level change summary is useful but not sufficient by itself unless the changed content is also visibly marked where the reader reviews it. Remove or refresh stale change markers on later updates so the highlights describe the current revision only.
+
+**Archiving.** Before replacing an existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/skill-inventory-{topic}.html`.
+
+**Brief Me (text-to-speech).** Every alignment page must include a `<script src="../scripts/alignment-tts-kokoro.js"></script>` tag before `</body>`. The script adds a "Brief Me" button that reads the page aloud section-by-section using Kokoro TTS (an 82M-parameter model running client-side via WebGPU/WASM from `kokoro-js`). The transport bar includes play/pause/stop/skip controls, a voice selector (persisted in localStorage), and speed selection. On first click the voice model downloads (~92MB quantized on WASM; ~326MB fp32 on WebGPU). Weights persist between visits via Cache API origin storage, and this works on `file://` origins in Chrome — including `file://wsl.localhost` UNC paths (verified 2026-06-09 with an instrumented probe in Windows Chrome: `caches` is available, entries survive reloads and browser restarts, and Chrome shares a single `file://` origin across all local pages, so one download serves every alignment page). Repeat visits pay model initialization only, not re-download. If `caches` is undefined (non-Chromium or locked-down browsers), the model re-downloads each visit; serving pages from a local HTTP origin (e.g. `node scripts/serve-alignment.mjs` in the repo root, then `http://localhost:8907/alignment/<page>.html`) guarantees caching there — note `http://localhost` is a separate origin from `file://`, so the first localhost visit downloads once even when the `file://` cache is already warm. After the first successful load on a machine, the script preloads the model during browser idle time on later page loads (gated by a `tts-kokoro-used` localStorage flag, so users who never click pay nothing). Text is prepared for speech before synthesis: block boundaries (headings, paragraphs, list items, table cells) get sentence punctuation so the model does not read them as run-ons, and speech-hostile symbols are normalized (`~92MB` reads as "approximately 92MB", `v0.3` as "version 0.3", em-dashes as comma pauses, `e.g.`/`i.e.`/`vs.` expanded). Synthesis is pipelined with small chunks: the first audio chunk is kept short (~250 chars) for fast time-to-first-audio, later chunks stay small (~300 chars, cut at sentence or clause boundaries) with up to two chunks synthesizing ahead during playback, and the next section's opening chunk is prefetched while the current section's last chunk plays, so chunk and section boundaries are gapless. If Kokoro fails to load (old browser, network error), it falls back to the Web Speech API automatically. It skips gate controls, compile UI, feedback textareas, and stat grids. Charts and tables use narrative summaries instead of raw data: containers with a `data-tts-narrative` attribute have the narrative read aloud; containers without the attribute are silently skipped. To inject TTS into existing pages, run `node scripts/inject-tts.mjs` (idempotent). Use `--force` to replace the existing TTS block with an updated version. Do not inline the TTS script; always use the `src` tag. Do not use `type="module"` — module scripts are blocked by CORS on `file://` URLs.
+
+**TTS narrative contract.** Every `.chart-container` and `.table-wrap` element should carry a `data-tts-narrative` attribute with a 1-3 sentence human-readable summary of what the chart or table shows. Chart functions in `scripts/alignment-chart-snippets.js` auto-generate a baseline narrative from their data; author-provided `data-tts-narrative` attributes take precedence. When authoring alignment pages manually, add `data-tts-narrative` to chart containers and table wrappers so that Brief Me reads a meaningful summary instead of skipping the element.
+
+**Browser open.** After writing the resulting HTML page, run `node scripts/open-html-page.mjs alignment/skill-inventory-{topic}.html --browser auto` from the repository root, replacing the path with the actual page path when needed. Report the script status (`focused`, `opened`, `fallback-opened`, `blocked`, or `failed`) in the handoff. Continue when opening is `blocked` if the files were written and verified correctly; a blocked browser-open attempt does not make the skill fail.

package/packs/project-fleet/claude/skill-inventory/CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changelog
+
+## v0.0 - 2026-05-31
+
+- Added initial report-only downstream skill inventory workflow with bundled scanner guidance.

package/packs/project-fleet/claude/skill-inventory/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: skill-inventory
+description: Inventory downstream repository Claude and Codex skill installs from a control-repo manifest, classify managed local skill-copy drift against canonical agentic-skills sources, and produce report-only Markdown or JSON guidance without refreshing, deleting, or mutating downstream repos.
+type: ops
+version: v0.0
+argument-hint: "[--manifest <path>] [--repo <path>] [--format markdown|json]"
+---
+
+# Skill Inventory
+
+Invoke as `/skill-inventory`.
+
+Use this skill from a control repository that manages downstream repositories and needs to know whether copied local skill roots are current, stale, pinned, unmanaged, or missing their canonical source.
+
+## V1 Contract
+
+Report-only — do not modify tracked files.
+
+- Do not run `scripts/pack.sh refresh`.
+- Do not run delete, cleanup, remove, prune, or reinstall commands.
+- Do not edit `.claude/skills/**`, `.codex/skills/**`, `.agents/project.json`, or any file inside downstream repositories.
+- Do not add an apply route in v1. Suggest exact follow-up commands only after the inventory report shows what is needed.
+- Only write control-repo artifacts: `tasks/skill-inventory.md`, `alignment/skill-inventory-{topic}.html`, task notes, prompt history, and normal shipping docs.
+
+## Process
+
+1. Read repo instructions first: `AGENTS.md`, `CLAUDE.md`, or the local equivalent.
+2. Capture the visible `/skill-inventory` invocation under `prompts/skill-inventory/` before substantive work, following the repo prompt-history convention.
+3. Resolve downstream repos from a manifest before scanning. Default manifest search order:
+   - `tasks/downstream-repos.md`
+   - `tasks/fleet-queue.md`
+   - `tasks/repo-seeding.md`
+4. Require a Markdown table column named `Local Path` or `Path` for local checkout paths. Remote-only `owner/repo` cells are not scannable; ask for a local path instead of guessing.
+5. Run the bundled scanner from this skill directory. Default output is the durable Markdown report:
+
+   ```bash
+   bash scripts/skill-inventory.sh --out tasks/skill-inventory.md --format markdown
+   ```
+
+   Useful variants:
+
+   ```bash
+   bash scripts/skill-inventory.sh --manifest tasks/downstream-repos.md --out tasks/skill-inventory.md
+   bash scripts/skill-inventory.sh --repo ../downstream-app --out -
+   bash scripts/skill-inventory.sh --format json --out -
+   ```
+
+6. The scanner sources the control repo's canonical `scripts/skill-links.sh` and uses `skill_install_status` for status classification. Do not reimplement the drift semantics manually.
+7. Review the report and build `alignment/skill-inventory-{topic}.html` using `ALIGNMENT-PAGE.md` when producing a durable report. The page must render the report, evidence, assumptions, action hints, and approval gates without context loss.
+8. End with:
+   - **Next work:** the most specific inventory follow-up, usually adding missing local paths or reviewing stale rows.
+   - **Recommended next command:** usually `/skill-inventory --manifest <path>` to rerun after manifest fixes, or `/project-fleet --status` when no inventory remediation is needed.
+
+## Status Categories
+
+Use the exact categories emitted by `skill_install_status`:
+
+- `ok`: managed copy matches the canonical source content.
+- `stale`: canonical source content changed since the managed copy was installed.
+- `unknown`: marker exists but lacks `source_sha`; refresh is needed later to enable deterministic tracking.
+- `missing-source`: marker points to a source directory that no longer exists.
+- `pinned`: symlinked install, usually to `archive/<version>`, intentionally frozen.
+- `not-managed`: skill directory is not an agentic-skills managed install.
+
+## Report Expectations
+
+`tasks/skill-inventory.md` should include:
+
+- control repo, manifest path, generated timestamp, and report-only notice;
+- repo-level totals across Claude and Codex skill roots;
+- per-agent rows for `.claude/skills/*` and `.codex/skills/*`;
+- installed and canonical version fields when available;
+- source path evidence for managed or pinned installs;
+- action hints for `stale`, `unknown`, and `missing-source`, including exact suggested follow-ups such as `scripts/pack.sh refresh`;
+- a clear statement that the scan did not run refresh, delete, cleanup, install, or other mutation commands.
+
+If no local paths are found, the scanner must fail non-destructively and print a manifest template with a `Local Path` column.
+
+## Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/skill-inventory-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.
+