skillpacks 0.1.0 → 0.1.2

package/packs/remotion/codex/youtube-format-research/SKILL.md

@@ -2,14 +2,14 @@
 name: youtube-format-research
 description: Break down a YouTube video's format, visual system, pacing, editing grammar, motion, audio, and Remotion-ready production patterns
 type: research
-version: v0.4
+version: v0.6
 argument-hint: "<video URL or ID> [--target remotion|script|style-guide] [--compare <video URL or ID...>]"
-interview_depth: none
+context_intake: artifact_only
 ---
 
 ## Pack Availability Guard
 
-Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `$pack install <pack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install <pack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
 
 # YouTube Format Research
 
@@ -30,7 +30,7 @@ Do not include `Recommended next skill`, `Recommended next command`, or downstre
 Use this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.
 
 1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML 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 perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.
-2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML 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>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page with the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
+2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML 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>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `<pre><code>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
 3. **Stage 3 - Finalize approved artifacts.** Consume 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 below, and convert the alignment page to `confirmed` with the approval record preserved.
 
 Canonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.

package/packs/remotion/codex/youtube-format-research/archive/v0.4/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: youtube-format-research
+description: Break down a YouTube video's format, visual system, pacing, editing grammar, motion, audio, and Remotion-ready production patterns
+type: research
+version: v0.4
+argument-hint: "<video URL or ID> [--target remotion|script|style-guide] [--compare <video URL or ID...>]"
+interview_depth: none
+---
+
+## Pack Availability Guard
+
+Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `$pack install <pack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+
+# YouTube Format Research
+
+Invoke as `$youtube-format-research`.
+
+## Report-First Approval Gate
+
+Default to scope-first approval: before synthesized research, inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions in a `review` alignment page plus a concise conversation summary.
+
+Do not perform synthesized research, rank candidates, make recommendations, or write working packets or canonical deliverables until final compiled YAML approves the research scope. Minimal pre-approval discovery may identify available files, source categories, and open questions; label it as scope evidence, not findings.
+
+After approved research-scope YAML, perform the research and write only the non-canonical working packet defined in the staged workflow. Then update the `review` alignment page with findings and stop again for feedback-only YAML or final compiled YAML artifact approval before creating or updating canonical research, spec, or task files.
+
+Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.
+
+## Staged Research Workflow
+
+Use this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.
+
+1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML 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 perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.
+2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML 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>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page with the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
+3. **Stage 3 - Finalize approved artifacts.** Consume 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 below, and convert the alignment page to `confirmed` with the approval record preserved.
+
+Canonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.
+
+## Evidence And Feedback Handling
+
+Treat user feedback as input to evaluate, not as automatic ground truth.
+
+- For factual, evidentiary, technical, or source-backed claims: verify against available evidence. If the user appears to misunderstand the evidence or states something factually incorrect, push back clearly and cite the evidence. Do not rewrite findings merely to agree.
+- For taste, brand, positioning preference, risk appetite, prioritization, or other subjective judgment calls: weigh user feedback heavily and adapt the recommendation unless it conflicts with verified evidence.
+- When feedback mixes facts and preference, separate them explicitly: correct the factual part, then incorporate the preference where it is a legitimate judgment call.
+- When uncertain, say what is known, what is inferred, and what would change the conclusion.
+
+## Inputs
+
+- Required: one YouTube video URL or video ID.
+- Optional `--target remotion|script|style-guide`: default `remotion`.
+- Optional `--compare <video URL or ID...>`: additional references to distinguish repeatable format rules from one-off choices.
+
+## Process
+
+1. Resolve all video targets into video IDs from watch URLs, Shorts URLs, youtu.be URLs, embed URLs, or raw 11-character IDs.
+2. Require `yt-dlp` for public metadata:
+
+   ```bash
+   command -v yt-dlp
+   ```
+
+3. Select a transcript Python interpreter. Prefer a workspace-local `.venv`; create it if missing. Install `youtube-transcript-api` into `.venv` only when the import check fails and network access is available.
+4. Persist raw evidence under `research/youtube/data/<video-id>/`:
+   - `metadata-YYYY-MM-DD.json`: raw `yt-dlp --dump-json "VIDEO_URL"` output.
+   - `transcript/<video-id>.json`: raw transcript JSON when available.
+   - `transcript/transcript-summary.json`: transcript text or failure reason.
+5. Inspect available metadata, transcript, chapters, thumbnail URLs, description, and any user-provided screenshots or notes. If visual details cannot be verified from available evidence, mark them as gaps instead of guessing.
+6. Analyze:
+   - Scene grammar: opener, recurring segments, transitions, title cards, examples, proof moments, CTA, outro.
+   - Timing and pacing: section durations, speaking density, cut rhythm, beats, visual resets, and retention support.
+   - Visual system: typography, color, layout, framing, captions, lower thirds, callouts, charts, browser frames, code blocks, or product shots.
+   - Motion language: camera moves, zooms, wipes, kinetic text, object movement, reveal timing, and transition rules.
+   - Audio language: music bed, silence, sound effects, emphasis beats, voiceover style, and mix notes when evidence supports them.
+   - Production assets: required footage, screenshots, diagrams, logos, fonts, icons, stock, B-roll, music, SFX, and licensing checks.
+7. Translate the reference into reusable format rules without copying copyrighted assets or pretending the exact source project is available.
+
+## Output
+
+Create the `research/youtube/` directory if it does not exist.
+
+Write:
+
+```text
+research/youtube/format-research-<video-id>-YYYY-MM-DD.md
+```
+
+Use this structure:
+
+```markdown
+# YouTube Format Research - [Title]
+
+> Video: [URL]
+> Target: remotion / script / style-guide
+> Date captured: YYYY-MM-DD
+> Evidence: [raw paths used]
+
+## Evidence Coverage
+
+| Evidence | Status | Path or gap |
+|---|---|---|
+| Public metadata | Available / Missing | ... |
+| Transcript | Available / Missing | ... |
+| Chapters | Available / Missing | ... |
+| Visual references | Available / Missing | ... |
+| Audio references | Available / Missing | ... |
+
+## Format Summary
+
+[The repeatable format in one concise brief.]
+
+## Scene And Timing Map
+
+| Segment | Approx time | Purpose | Visual treatment | Audio / motion notes |
+|---|---:|---|---|---|
+| ... | ... | ... | ... | ... |
+
+## Visual And Motion System
+
+- **Typography**: ...
+- **Color and layout**: ...
+- **Captions / callouts**: ...
+- **Transitions**: ...
+- **Recurring components**: ...
+
+## Production Grammar
+
+[Rules for pacing, proof, examples, visual resets, CTA placement, and when to change scenes.]
+
+## Remotion Handoff
+
+| Component / asset | Role | Inputs | Notes |
+|---|---|---|---|
+| ... | ... | ... | ... |
+
+## Adaptation Guidance
+
+[What to copy as a pattern, what to avoid copying directly, and what to change for the user's brand or series.]
+
+## Evidence Gaps And Human Checks
+
+[Missing screenshots, unavailable fonts, uncertain audio details, licensing checks, or manual review needs.]
+```
+
+## Constraints
+
+- Do not copy or embed copyrighted assets, music, fonts, footage, or thumbnails unless the user confirms licensing.
+- Do not invent visual details that are not evident from metadata, transcript, screenshots, or user-provided notes.
+- Distinguish repeatable format rules from one-off creative choices.
+- Keep Remotion handoff at the component/spec level; actual scaffold and render planning belongs to `$video-build`.
+- Do not bypass login walls, bot protections, access controls, or private YouTube Studio data.
+- Archive existing canonical artifacts before replacing them under `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-relative-path>`.
+
+## Approved Artifact Handoff
+
+After an approved synthesized write, explicit write/update mode, or any direct artifact mutation:
+
+- List every created or updated synthesized artifact path in the final response.
+- State the verification performed, such as readback, schema/check command, or why no executable verification applies for a Markdown-only strategy artifact.
+- Check and report the relevant git status for intended artifacts when the project is a git repository. If intended artifacts are modified or untracked, make the next action shipping, committing, or an explicit dirty-artifact handoff before recommending downstream strategy work.
+- Do not imply the research workflow is complete while approved artifacts remain untracked or uncommitted unless the user explicitly asked not to ship.
+- If stopping for approval before writing, the approval request remains the next action; do not include downstream routing.
+
+## Intent-Aware Routing
+
+Before applying the default `## Next-Skill Routing` sequence, classify the user's immediate intent and route to the missing action that best serves that intent:
+
+- Strategy refresh: recommend the missing or stale positioning, programming, portfolio, metrics, or product-media artifact.
+- Recording prep: recommend the missing series spec, script, build proof, walkthrough guide, or validation artifact needed before recording.
+- Upload prep: recommend packaging, title/thumbnail, description, chapters, or final metadata work before broader strategy work.
+- Performance review: recommend metrics, cadence, portfolio, peer benchmark, or owner-analytics export work before new content planning.
+- Owner analytics or private/manual platform evidence: route to an explicit manual/guide handoff instead of inventing unavailable metrics.
+- Dirty intended artifacts: route to shipping/commit/handoff first, not another creator strategy skill.
+
+Use the default next-skill sequence only when no stronger user intent, missing artifact, manual blocker, or dirty-artifact handoff applies.
+
+## 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/youtube-format-research-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/remotion/codex/youtube-format-research/archive/v0.5/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: youtube-format-research
+description: Break down a YouTube video's format, visual system, pacing, editing grammar, motion, audio, and Remotion-ready production patterns
+type: research
+version: v0.5
+argument-hint: "<video URL or ID> [--target remotion|script|style-guide] [--compare <video URL or ID...>]"
+interview_depth: none
+---
+
+## Pack Availability Guard
+
+Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install <pack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+
+# YouTube Format Research
+
+Invoke as `$youtube-format-research`.
+
+## Report-First Approval Gate
+
+Default to scope-first approval: before synthesized research, inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions in a `review` alignment page plus a concise conversation summary.
+
+Do not perform synthesized research, rank candidates, make recommendations, or write working packets or canonical deliverables until final compiled YAML approves the research scope. Minimal pre-approval discovery may identify available files, source categories, and open questions; label it as scope evidence, not findings.
+
+After approved research-scope YAML, perform the research and write only the non-canonical working packet defined in the staged workflow. Then update the `review` alignment page with findings and stop again for feedback-only YAML or final compiled YAML artifact approval before creating or updating canonical research, spec, or task files.
+
+Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.
+
+## Staged Research Workflow
+
+Use this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.
+
+1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML 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 perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.
+2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML 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>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page with the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
+3. **Stage 3 - Finalize approved artifacts.** Consume 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 below, and convert the alignment page to `confirmed` with the approval record preserved.
+
+Canonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.
+
+## Evidence And Feedback Handling
+
+Treat user feedback as input to evaluate, not as automatic ground truth.
+
+- For factual, evidentiary, technical, or source-backed claims: verify against available evidence. If the user appears to misunderstand the evidence or states something factually incorrect, push back clearly and cite the evidence. Do not rewrite findings merely to agree.
+- For taste, brand, positioning preference, risk appetite, prioritization, or other subjective judgment calls: weigh user feedback heavily and adapt the recommendation unless it conflicts with verified evidence.
+- When feedback mixes facts and preference, separate them explicitly: correct the factual part, then incorporate the preference where it is a legitimate judgment call.
+- When uncertain, say what is known, what is inferred, and what would change the conclusion.
+
+## Inputs
+
+- Required: one YouTube video URL or video ID.
+- Optional `--target remotion|script|style-guide`: default `remotion`.
+- Optional `--compare <video URL or ID...>`: additional references to distinguish repeatable format rules from one-off choices.
+
+## Process
+
+1. Resolve all video targets into video IDs from watch URLs, Shorts URLs, youtu.be URLs, embed URLs, or raw 11-character IDs.
+2. Require `yt-dlp` for public metadata:
+
+   ```bash
+   command -v yt-dlp
+   ```
+
+3. Select a transcript Python interpreter. Prefer a workspace-local `.venv`; create it if missing. Install `youtube-transcript-api` into `.venv` only when the import check fails and network access is available.
+4. Persist raw evidence under `research/youtube/data/<video-id>/`:
+   - `metadata-YYYY-MM-DD.json`: raw `yt-dlp --dump-json "VIDEO_URL"` output.
+   - `transcript/<video-id>.json`: raw transcript JSON when available.
+   - `transcript/transcript-summary.json`: transcript text or failure reason.
+5. Inspect available metadata, transcript, chapters, thumbnail URLs, description, and any user-provided screenshots or notes. If visual details cannot be verified from available evidence, mark them as gaps instead of guessing.
+6. Analyze:
+   - Scene grammar: opener, recurring segments, transitions, title cards, examples, proof moments, CTA, outro.
+   - Timing and pacing: section durations, speaking density, cut rhythm, beats, visual resets, and retention support.
+   - Visual system: typography, color, layout, framing, captions, lower thirds, callouts, charts, browser frames, code blocks, or product shots.
+   - Motion language: camera moves, zooms, wipes, kinetic text, object movement, reveal timing, and transition rules.
+   - Audio language: music bed, silence, sound effects, emphasis beats, voiceover style, and mix notes when evidence supports them.
+   - Production assets: required footage, screenshots, diagrams, logos, fonts, icons, stock, B-roll, music, SFX, and licensing checks.
+7. Translate the reference into reusable format rules without copying copyrighted assets or pretending the exact source project is available.
+
+## Output
+
+Create the `research/youtube/` directory if it does not exist.
+
+Write:
+
+```text
+research/youtube/format-research-<video-id>-YYYY-MM-DD.md
+```
+
+Use this structure:
+
+```markdown
+# YouTube Format Research - [Title]
+
+> Video: [URL]
+> Target: remotion / script / style-guide
+> Date captured: YYYY-MM-DD
+> Evidence: [raw paths used]
+
+## Evidence Coverage
+
+| Evidence | Status | Path or gap |
+|---|---|---|
+| Public metadata | Available / Missing | ... |
+| Transcript | Available / Missing | ... |
+| Chapters | Available / Missing | ... |
+| Visual references | Available / Missing | ... |
+| Audio references | Available / Missing | ... |
+
+## Format Summary
+
+[The repeatable format in one concise brief.]
+
+## Scene And Timing Map
+
+| Segment | Approx time | Purpose | Visual treatment | Audio / motion notes |
+|---|---:|---|---|---|
+| ... | ... | ... | ... | ... |
+
+## Visual And Motion System
+
+- **Typography**: ...
+- **Color and layout**: ...
+- **Captions / callouts**: ...
+- **Transitions**: ...
+- **Recurring components**: ...
+
+## Production Grammar
+
+[Rules for pacing, proof, examples, visual resets, CTA placement, and when to change scenes.]
+
+## Remotion Handoff
+
+| Component / asset | Role | Inputs | Notes |
+|---|---|---|---|
+| ... | ... | ... | ... |
+
+## Adaptation Guidance
+
+[What to copy as a pattern, what to avoid copying directly, and what to change for the user's brand or series.]
+
+## Evidence Gaps And Human Checks
+
+[Missing screenshots, unavailable fonts, uncertain audio details, licensing checks, or manual review needs.]
+```
+
+## Constraints
+
+- Do not copy or embed copyrighted assets, music, fonts, footage, or thumbnails unless the user confirms licensing.
+- Do not invent visual details that are not evident from metadata, transcript, screenshots, or user-provided notes.
+- Distinguish repeatable format rules from one-off creative choices.
+- Keep Remotion handoff at the component/spec level; actual scaffold and render planning belongs to `$video-build`.
+- Do not bypass login walls, bot protections, access controls, or private YouTube Studio data.
+- Archive existing canonical artifacts before replacing them under `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-relative-path>`.
+
+## Approved Artifact Handoff
+
+After an approved synthesized write, explicit write/update mode, or any direct artifact mutation:
+
+- List every created or updated synthesized artifact path in the final response.
+- State the verification performed, such as readback, schema/check command, or why no executable verification applies for a Markdown-only strategy artifact.
+- Check and report the relevant git status for intended artifacts when the project is a git repository. If intended artifacts are modified or untracked, make the next action shipping, committing, or an explicit dirty-artifact handoff before recommending downstream strategy work.
+- Do not imply the research workflow is complete while approved artifacts remain untracked or uncommitted unless the user explicitly asked not to ship.
+- If stopping for approval before writing, the approval request remains the next action; do not include downstream routing.
+
+## Intent-Aware Routing
+
+Before applying the default `## Next-Skill Routing` sequence, classify the user's immediate intent and route to the missing action that best serves that intent:
+
+- Strategy refresh: recommend the missing or stale positioning, programming, portfolio, metrics, or product-media artifact.
+- Recording prep: recommend the missing series spec, script, build proof, walkthrough guide, or validation artifact needed before recording.
+- Upload prep: recommend packaging, title/thumbnail, description, chapters, or final metadata work before broader strategy work.
+- Performance review: recommend metrics, cadence, portfolio, peer benchmark, or owner-analytics export work before new content planning.
+- Owner analytics or private/manual platform evidence: route to an explicit manual/guide handoff instead of inventing unavailable metrics.
+- Dirty intended artifacts: route to shipping/commit/handoff first, not another creator strategy skill.
+
+Use the default next-skill sequence only when no stronger user intent, missing artifact, manual blocker, or dirty-artifact handoff applies.
+
+## 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/youtube-format-research-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/repo-maintenance/claude/bootstrap-repo/CHANGELOG.md

@@ -1,5 +1,17 @@
 # bootstrap-repo changelog (claude)
 
+## v0.5 - 2026-06-12
+
+- Updated product bootstrap routing to use the AFPS prototype flow tree: `/user-flow-map` -> `/ux-variations [specific-user-flow]` -> `/ui-interview [specific-ux-variation]`, with requirements-only/layout-mode as explicit bounded detours.
+
+## v0.4 - 2026-06-12
+
+- Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.
+
+## v0.3 - 2026-06-11
+
+- Updated product bootstrap pack checks from `business-discovery` to `business-research` after the pack rename.
+
 ## v0.2 - 2026-06-07
 
 - Routed product bootstrap next-command guidance from retired `/icp` to `/customer-discovery` while preserving `research/icp.md` as accepted evidence.

package/packs/repo-maintenance/claude/bootstrap-repo/SKILL.md

@@ -2,7 +2,7 @@
 name: bootstrap-repo
 description: Initialize or reset a repository README and agent workflow docs from a short project brief
 type: execution
-version: v0.2
+version: v0.5
 argument-hint: "<project brief>"
 ---
 
@@ -56,14 +56,15 @@ Initialize a repository with a useful `README.md` and the standard agent workflo
 
 7. **Route research-first after product bootstrap:**
    - If this is a product, app, SaaS, dashboard, internal tool, marketplace, website, or other user-facing restart, rebuild market and lifecycle alignment from the high-level concept before UI requirements or prototypes.
-   - Check `.agents/project.json.enabled_packs` when present. If `business-discovery` is not enabled, recommend `/pack install business-discovery` before `/customer-discovery`. If `customer-lifecycle` is not enabled, include `/pack install customer-lifecycle` before `/journey-map`.
-   - When required packs are available, recommend `/customer-discovery <concept>` as the next command. After `/customer-discovery`, the intended sequence is `/competitive-analysis` -> `/journey-map` -> `/positioning` -> `/user-flow-map` -> `/ui-interview --requirements-only` -> `/ux-variations --layout-mode` -> prototype work.
+   - Check `.agents/project.json.enabled_packs` when present. If `business-research` is not enabled, recommend `npx skillpacks install business-research` from the project shell, before `/customer-discovery`. If `customer-lifecycle` is not enabled, include `npx skillpacks install customer-lifecycle` before `/journey-map`.
+   - When required packs are available, recommend `/customer-discovery <concept>` as the next command. After `/customer-discovery`, the intended sequence is `/competitive-analysis` -> `/journey-map` -> `/positioning` -> `/user-flow-map` -> `/ux-variations [specific-user-flow]` -> `/ui-interview [specific-ux-variation]` -> prototype work.
    - If current, accepted `research/icp.md`, `research/competitive-analysis.md`, and `research/journey-map.md` already exist from the fresh reset but positioning is missing, then recommend `/positioning <topic>`.
    - If positioning exists but a flow map is missing, recommend `/user-flow-map <topic>`.
-   - If a flow map exists but UI requirements are missing, recommend `/ui-interview --requirements-only <topic>`.
-   - If UI requirements exist but layout variations are missing, recommend `/ux-variations --layout-mode <topic>`.
+   - If a flow map exists but UX variation branches are missing, recommend `/ux-variations [specific-user-flow]`.
+   - If UX variation branches exist but no branch has an approved UI direction, recommend `/ui-interview [specific-ux-variation]`.
+   - Recommend `/ui-interview --requirements-only <topic>` only when the user explicitly needs a fixed content/data/action contract before `/ux-variations --layout-mode <topic>`.
    - Only route directly to `/roadmap` or `/exec` when the project is non-UI/non-product work or already has accepted alignment artifacts and a consolidated prototype.
-   - The intended product sequence after reset is: `/customer-discovery` -> `/competitive-analysis` -> `/journey-map` -> `/positioning` -> `/user-flow-map` -> `/ui-interview --requirements-only` -> `/ux-variations --layout-mode` -> build variants/prototypes via `/exec` or the applicable prototype-building route -> `/uat --variant-evaluation` -> `/consolidate-variations` -> `/research-roadmap --post-prototype` -> `/spec-interview` or `/roadmap`.
+   - The intended product sequence after reset is: `/customer-discovery` -> `/competitive-analysis` -> `/journey-map` -> `/positioning` -> `/user-flow-map` -> `/ux-variations [specific-user-flow]` -> `/ui-interview [specific-ux-variation]` -> build variants/prototypes via `/exec` or the applicable prototype-building route -> `/uat --variant-evaluation` -> `/consolidate-variations` -> `/research-roadmap --post-prototype` -> `/spec-interview` or `/roadmap`.
 
 ## Output
 
@@ -76,7 +77,7 @@ Bootstrapped repository
 - AGENTS.md: [created | updated | unchanged], corresponding workflow block appears once
 - Monorepo safety block: [included (<heuristic>) | skipped]
 - Verification: [commands/checks run]
-- Recommended next command: [/pack install business-discovery | /pack install customer-lifecycle | /pack install product-design | /customer-discovery <concept> | /positioning <topic> | /user-flow-map <topic> | /ui-interview --requirements-only <topic> | /ux-variations --layout-mode <topic> | /roadmap | /exec]
+- Recommended next command: [npx skillpacks install business-research | npx skillpacks install customer-lifecycle | npx skillpacks install product-design | /customer-discovery <concept> | /positioning <topic> | /user-flow-map <topic> | /ux-variations [specific-user-flow] | /ui-interview [specific-ux-variation] | /roadmap | /exec]
 ```
 
 ## Constraints

package/packs/repo-maintenance/claude/bootstrap-repo/archive/v0.2/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: bootstrap-repo
+description: Initialize or reset a repository README and agent workflow docs from a short project brief
+type: execution
+version: v0.2
+argument-hint: "<project brief>"
+---
+
+# Bootstrap Repo
+
+Initialize a repository with a useful `README.md` and the standard agent workflow docs. When invoked with `--reset-existing`, first archive stale implementation and documentation files from a non-empty stuck repo so the fresh start is not built on old code or old assumptions by accident.
+
+## Process
+
+1. **Parse the project brief and mode** from `$ARGUMENTS`:
+   - Detect `--reset-existing`, `--in-place-reset`, or an explicit request to archive/reset the current codebase before bootstrap.
+   - Extract the project name, purpose, setup instructions, run/test commands, and any constraints.
+   - If the brief is missing or too thin to write a useful README, ask for the project name and one-sentence purpose. Ask for setup or run instructions only when the repository does not make them discoverable.
+
+2. **Inspect the target repository:**
+   - Read existing `README.md`, `CLAUDE.md`, `AGENTS.md`, package manifests, obvious build files, and directory names.
+   - Preserve discovered commands and facts. Do not invent dependency managers, deployment targets, or product claims.
+
+3. **Reset existing stale repo when explicitly requested:**
+   - Only perform this step when reset mode is explicit. Never archive or move files during ordinary bootstrap.
+   - Confirm the repo is non-empty and contains stale implementation, docs, research, specs, task files, design notes, or generated app structure. If it is already empty or freshly initialized, skip archival and note why.
+   - Create `archive/YYYY-MM-DD-HHMMSS/` and move stale implementation and documentation files/directories there before writing fresh bootstrap docs.
+   - Archive old docs by default, including `docs/`, `alignment/`, `research/`, `specs/`, `tasks/`, planning reports, implementation notes, design docs, old README content, and prior roadmap/todo/history files. These may remain useful as historical evidence in the archive, but they must not stay active as source-of-truth inputs.
+   - Do not archive `.git/`, `.agents/`, `archive/`, `desk-flip-report.md`, root agent config files needed for the current session, or the newly written high-level concept artifact.
+   - Preserve exactly one active concept seed, such as `concept.md` or `README.md` `## Concept`, derived from the bootstrap brief or `desk-flip-report.md`. Keep it high level: product name, target user, core problem, value proposition, non-goals, and open questions. Do not preserve old research/spec detail as active files.
+   - Preserve a manifest at `archive/YYYY-MM-DD-HHMMSS/MANIFEST.md` listing every moved path, every intentionally preserved path, and the high-level concept source that justified the reset.
+   - Prefer `git mv` for tracked paths so history remains understandable. Use ordinary moves only for untracked paths.
+   - Do not delete old files outright. If a path cannot be moved safely, stop and report the blocker instead of partially resetting further.
+   - After archival, the root should contain only the fresh-start sources of truth: git metadata, agent config, the archive directory, `desk-flip-report.md`, the high-level concept artifact, and any newly written bootstrap docs. Old docs/research/specs belong in the archive.
+
+4. **Create or update `README.md`:**
+   - If `README.md` is absent, empty, or placeholder-like, write a concise README with:
+     - `# <Project Name>`
+     - A short purpose summary.
+     - `## Getting Started`
+     - `## Development`
+     - `## Notes`
+   - If `README.md` already has substantial content, preserve it. Ask before replacing it; otherwise add a small bootstrap section only when it improves the file.
+   - Use the project brief as the primary source and repository inspection as supporting evidence.
+
+5. **Provision agent workflow docs:**
+   - Run `/provision-agentic-config` for the same repository.
+   - Confirm `CLAUDE.md` and `AGENTS.md` exist after provisioning.
+   - Preserve unrelated existing content in both files.
+
+6. **Verify the result:**
+   - Check that `README.md`, `CLAUDE.md`, and `AGENTS.md` exist.
+   - Confirm the corresponding workflow orchestration block appears exactly once in each of `CLAUDE.md` and `AGENTS.md`.
+   - Report whether the monorepo safety block was included or skipped by `/provision-agentic-config`.
+   - In reset mode, check that `archive/YYYY-MM-DD-HHMMSS/MANIFEST.md` exists and lists moved and preserved paths, and verify old docs/research/specs/tasks were archived rather than left active.
+
+7. **Route research-first after product bootstrap:**
+   - If this is a product, app, SaaS, dashboard, internal tool, marketplace, website, or other user-facing restart, rebuild market and lifecycle alignment from the high-level concept before UI requirements or prototypes.
+   - Check `.agents/project.json.enabled_packs` when present. If `business-discovery` is not enabled, recommend `/pack install business-discovery` before `/customer-discovery`. If `customer-lifecycle` is not enabled, include `/pack install customer-lifecycle` before `/journey-map`.
+   - When required packs are available, recommend `/customer-discovery <concept>` as the next command. After `/customer-discovery`, the intended sequence is `/competitive-analysis` -> `/journey-map` -> `/positioning` -> `/user-flow-map` -> `/ui-interview --requirements-only` -> `/ux-variations --layout-mode` -> prototype work.
+   - If current, accepted `research/icp.md`, `research/competitive-analysis.md`, and `research/journey-map.md` already exist from the fresh reset but positioning is missing, then recommend `/positioning <topic>`.
+   - If positioning exists but a flow map is missing, recommend `/user-flow-map <topic>`.
+   - If a flow map exists but UI requirements are missing, recommend `/ui-interview --requirements-only <topic>`.
+   - If UI requirements exist but layout variations are missing, recommend `/ux-variations --layout-mode <topic>`.
+   - Only route directly to `/roadmap` or `/exec` when the project is non-UI/non-product work or already has accepted alignment artifacts and a consolidated prototype.
+   - The intended product sequence after reset is: `/customer-discovery` -> `/competitive-analysis` -> `/journey-map` -> `/positioning` -> `/user-flow-map` -> `/ui-interview --requirements-only` -> `/ux-variations --layout-mode` -> build variants/prototypes via `/exec` or the applicable prototype-building route -> `/uat --variant-evaluation` -> `/consolidate-variations` -> `/research-roadmap --post-prototype` -> `/spec-interview` or `/roadmap`.
+
+## Output
+
+```markdown
+Bootstrapped repository
+- README.md: [created | updated | preserved], source: [arguments | prompts | existing content]
+- Reset archive: [created archive/YYYY-MM-DD-HHMMSS | skipped (<reason>)]
+- Active concept seed: [concept.md | README.md ## Concept | other]
+- CLAUDE.md: [created | updated | unchanged], corresponding workflow block appears once
+- AGENTS.md: [created | updated | unchanged], corresponding workflow block appears once
+- Monorepo safety block: [included (<heuristic>) | skipped]
+- Verification: [commands/checks run]
+- Recommended next command: [/pack install business-discovery | /pack install customer-lifecycle | /pack install product-design | /customer-discovery <concept> | /positioning <topic> | /user-flow-map <topic> | /ui-interview --requirements-only <topic> | /ux-variations --layout-mode <topic> | /roadmap | /exec]
+```
+
+## Constraints
+
+- Do not overwrite substantial existing `README.md` content without explicit user confirmation.
+- Do not invent setup, test, deploy, or architecture details that are not in the brief or repository.
+- Keep the README concise and useful for a new contributor.
+- Do not modify files other than `README.md`, `CLAUDE.md`, and `AGENTS.md` unless the user explicitly asks or invokes reset mode.
+- Reset mode may move stale files, including old docs/research/specs/tasks, into `archive/YYYY-MM-DD-HHMMSS/` and write that archive's `MANIFEST.md`; it may not delete files outright.
+- In reset mode, do not preserve old docs as active files just because they were marked salvageable. Use them only as archived historical evidence; active research and requirements restart from the high-level concept.
+- Do not create, modify, or suggest GitHub Actions workflows.
+
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.