skillpacks 0.1.1 → 0.1.2

package/base/codex/animation-design-planner/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: animation-design-planner
+description: Plan interactive UI animations before implementation with visible motion contracts, lifecycle ownership, accessibility/performance guardrails, and proof gates
+type: planning
+version: v0.1
+invocation: orchestrator
+argument-hint: "[component, interaction, animation bug, or motion brief]"
+visual_tier: prototype
+---
+
+# Animation Design Planner
+
+Invoke as `$animation-design-planner`.
+
+Use this skill when a user asks to create, change, debug, or polish an interactive UI animation, transition, or multi-component motion sequence. This is a planning and proof skill, not a direct implementation skill: it prevents local timing tweaks from starting before the visible sequence, lifecycle owner, state phases, and proof method are named.
+
+Use it for drawers, modals, popovers, cards, route transitions, list reordering, shared-element illusions, mount/unmount choreography, staggered content, and visual regressions such as flashing, popping, jumping, duplicated layers, or broken close/open sequencing.
+
+For generated video, Remotion timelines, or non-interactive animation, produce only the transferable storyboard/timing and proof expectations, then route execution to the relevant video or media skill when available. Do not expand this skill into a full video-production workflow yet.
+
+## Workflow
+
+1. **Identify the motion surface**
+   - Name the component, route, screen, or interaction being planned.
+   - Identify the trigger: click, hover, focus, drag, route change, async state, mount, unmount, reorder, or error/recovery state.
+   - Read the relevant local component, style, animation, and test files when the user is asking about an existing codebase.
+   - Treat ambiguous requests such as "smooth this out" or "fix the animation" as requests to define the visible sequence before implementation.
+
+2. **Write the visible motion contract**
+   - Define the start state and end state in visible user terms.
+   - State what the user should see at each transition boundary.
+   - Name what must never happen: flash, pop, jump, duplicate, clipped content, stale layer, focus loss, scroll jump, layout shift, or incorrect z-order.
+   - Define accepted interruption behavior: repeated clicks, quick close after open, route away, async data arrival, resize, reduced-motion preference, or component unmount.
+   - Define the focal point and continuity target: what should keep the user's eye anchored.
+
+3. **Storyboard the timeline**
+   - Break the motion into phases or key frames with approximate timing, easing, and visible state per phase.
+   - Mark focal element, supporting elements, continuity/shared elements, and any staggered content.
+   - Include anticipation, follow-through, or settling only when it improves comprehension rather than decoration.
+   - For shared-element or layout illusions, state which element is visually continuous and which elements are entering, exiting, or temporarily hidden.
+   - Keep the storyboard implementation-neutral until the lifecycle ownership map is clear.
+
+4. **Map lifecycle ownership**
+   - Assign one explicit owner for any multi-component sequence. This can be a page-level controller, state machine, reducer, parent component, or animation coordinator.
+   - Name every state-machine phase. Use phase names that describe visible lifecycle, such as `closed`, `opening`, `drawer-open`, `closing-collapse`, `sheet-exiting`, `layout-morph-out`, and `sealed`.
+   - Map which component owns mount/unmount, visibility, identity, focus, layout measurement, and callbacks for phase completion.
+   - Define stable keys and identity rules. State which key must persist through exit and which key may change only after the exit or morph is complete.
+   - Define callback handoff points: animation complete, exit complete, layout measurement ready, focus restored, overlay dismissed, or state cleared.
+   - If ownership is split across siblings without a named coordinator, stop and redesign the ownership map before proposing timing changes.
+
+5. **Choose implementation guardrails**
+
+   **Framework detection and routing:** detect which animation framework the codebase uses, then route to the appropriate framework subskill for framework-specific guardrails. Detection order:
+   - Grep for `framer-motion` or `motion` in package.json / imports → route to `$animation-design-planner frameworks/motion-framer`
+   - Grep for `gsap` in package.json / imports → route to `frameworks/gsap` subskill
+   - Grep for `@angular/animations` → route to the appropriate Angular animation subskill when available
+   - Grep for `three` or `@react-three/fiber` → route to `frameworks/threejs` subskill
+   - Grep for `element.animate(` or Web Animations API usage → route to `frameworks/web-animations-api` subskill
+   - Grep for CSS `@keyframes`, `transition:`, `animation:` in stylesheets → route to `frameworks/css-transitions` subskill
+   - If multiple frameworks detected or ambiguous, ask the user which framework to target
+   - If no subskill exists for the detected framework, use the baseline guardrails below
+
+   **Baseline guardrails (all frameworks inherit these):**
+   - Prefer transform and opacity animation. Avoid animating layout, paint, filter, shadow, or expensive size properties unless the plan names the cost and proof.
+   - Define reduced-motion behavior for interaction-triggered motion. Nonessential motion must be suppressed or converted to instant/fade behavior when the user prefers reduced motion.
+   - Specify focus management, pointer-event behavior, scroll locking, z-index/layering, and content clipping rules when they affect the motion.
+
+6. **Define the proof gate**
+   - Write acceptance checks tied directly to the visible motion contract.
+   - Include slow-motion or debug-duration review steps for sequencing.
+   - Include Playwright screenshot or video capture when feasible, especially for close/open sequences, shared-element motion, drawer/modal transitions, and regression-prone visual states.
+   - Include reduced-motion verification.
+   - Include manual review steps for what automated screenshots cannot prove, such as perceived continuity, focal attention, and interruption feel.
+   - State the exact proof artifacts expected before the implementation is considered done.
+
+7. **Hand off implementation only after the plan**
+   - If the user asked only for planning, stop with the plan and proof gate.
+   - If the user asked for implementation too, make the implementation step conditional on the plan and proof gate. Then write the implementation plan and proof gate as the routing contract, or name the appropriate implementation skill when one owns the work.
+   - For bug-fix requests, route to `$investigate --ui` only after this skill has named the visible motion contract and likely lifecycle owner, unless the bug is a crash or data issue.
+
+## Output
+
+Produce a structured animation plan with these sections:
+
+- **Visible Motion Contract:** trigger, start state, end state, expected user-visible sequence, focal point, continuity target, forbidden artifacts, and accepted interruption behavior.
+- **Storyboard / Timeline:** phases or key frames, timing, easing, focal element, supporting elements, shared elements, stagger, anticipation, follow-through, and settling.
+- **Lifecycle Ownership Map:** single sequence owner, state phases, component mount/unmount responsibilities, stable key rules, identity persistence, callback handoffs, focus/scroll responsibilities, and interruption handling.
+- **Implementation Guardrails:** framework-specific guardrails (from the routed subskill), reduced-motion behavior, transform/opacity-first performance constraints, layout/paint risks, layering, and pointer/focus rules.
+- **Proof Gate:** slow-motion/manual review steps, Playwright screenshot or video capture plan where feasible, reduced-motion verification, regression checks, and acceptance checklist tied to the visible motion contract.
+- **Implementation Handoff:** whether implementation is ready, blocked, or should be represented by an approved task artifact, `$investigate --ui`, or another owner skill.
+
+End with:
+
+```md
+**Next work:** <specific implementation, investigation, or review step>
+**Recommended next command:** <one command or "none">
+```
+
+## Constraints
+
+- Do not start by tweaking durations, easing constants, CSS classes, or Motion props before the visible motion contract, lifecycle owner, state phases, and proof method are named.
+- Do not propose a multi-component animation without one lifecycle owner or explicit state-machine coordinator.
+- Do not clear identity, active item state, or stable keys before exit, shared layout, or close-morph phases have completed.
+- Do not rely on "looks better" as proof. Tie proof to visible contract acceptance checks and concrete artifacts.
+- Do not ignore reduced-motion behavior for interaction-triggered motion.
+- Do not use layout/paint-heavy animation properties as the default path. Prefer transform and opacity unless the plan justifies and proves otherwise.
+- Do not create or modify GitHub Actions workflows.
+
+## 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/animation-design-planner-{topic}.html`.
+
+## Default Shipping Contract
+
+- This skill is planning-first. Normally it should not mutate implementation files directly.
+- If the user explicitly asks this skill to create or modify tracked files, finish by committing and pushing all intended changes to the repository primary branch (`main` when present, otherwise `master`) before stopping.
+- This contract does not override stricter safety rules about secrets, destructive history changes, release publication/tag confirmation, production deploy confirmation, paid actions, or public visibility changes.

package/{global → base}/codex/codebase-status/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## v0.10 - 2026-06-13
+
+- Removed direct execution-loop command handoffs from non-exec routing; route through approved YAML, task, or roadmap artifacts instead.
+
+
+## v0.9 - 2026-06-12
+
+- Updated canonical AFPS status routing to use the flow-tree prototype default: `$user-flow-map` -> `$ux-variations [specific-user-flow]` -> `$ui-interview [specific-ux-variation]`, with requirements-only/layout-mode as explicit bounded detours.
+
+## v0.8 - 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.7 - 2026-06-11
 
 - Updated optional business research detour pack checks from `business-discovery` to `business-research` after the pack rename.

package/base/codex/codebase-status/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: codebase-status
+description: Report what a repository is, what recent conversation history says about it, current application status, and outstanding work
+type: analysis
+version: v0.10
+argument-hint: "[optional repo path, focus, or --no-history]"
+---
+
+# Codebase Status
+
+Invoke as `$codebase-status`.
+
+Use this skill when the user asks what a repo or application is, where work was left, what is outstanding, whether it is ready/stable, or wants a detailed status report that combines codebase evidence with local Claude/Codex conversation history.
+
+This is read-only status synthesis. It does not replace `$roadmap`: `roadmap` maintains the task pipeline and priority queue; `codebase-status` explains the actual current state of the repo and relevant prior conversations.
+
+## Process
+
+1. Resolve target repo:
+   - Default to the current working directory.
+   - If the user provides a path, use that repo.
+   - Confirm it is a git worktree when possible; if not, continue with filesystem evidence and report that git evidence is unavailable.
+2. Read project orientation:
+   - `README.md`, `AGENTS.md`, `CLAUDE.md`, `.agents/project.json`, package/workspace files, app entrypoints, and high-signal docs.
+   - Identify project type, main apps/packages, runtime, tests, and likely user-facing or developer-facing purpose.
+3. Read planning and status docs when present:
+   - `tasks/roadmap.md`, `tasks/todo.md`, `tasks/manual-todo.md`, `tasks/record-todo.md`, `tasks/recurring-todo.md`, `tasks/history.md`, `tasks/lessons.md`, `tasks/phases/`, `specs/`, `spec.md`, and `research/`.
+   - Distinguish checked-off work, active work, manual blockers, advisory work, stale docs, and missing docs.
+4. Read routing evidence for product, research, or spec repos:
+   - When `research/`, `specs/`, `spec.md`, product docs, or prototype artifacts exist, read `docs/pack-workflow-matrix.md` and `docs/skill-next-step-contracts.md` if present.
+   - Identify the last completed relevant research/product skill from artifacts, task history, or conversation history. Before recommending another research/product skill, consult that skill's active `SKILL.md` `## Next Steps` contract and any `## Next Steps` section in its output artifact.
+   - Treat those route contracts as stronger evidence than a generic status impression. If docs disagree, report the contradiction and prefer the newest active skill contract or route matrix with file evidence.
+   - For pack-local recommendations, check `.agents/project.json` `enabled_packs` first. If the target skill's pack is not enabled, recommend `npx skillpacks install <pack-name>` from the project shell, before the skill.
+5. Inspect git evidence:
+   - `git status --short`
+   - current branch and upstream status
+   - last 20 commits
+   - unpushed commits when an upstream exists
+   - changed files in the working tree
+6. Inspect codebase health signals:
+   - Project structure and primary modules.
+   - Test/build/lint scripts from package manifests or equivalent tool files.
+   - Obvious TODO/FIXME markers, failing-test notes, disabled tests, and local quality scripts.
+   - Do not run expensive commands by default. Run cheap read-only inspections freely; ask or state assumptions before long builds, network installs, destructive commands, or mutation.
+7. Find related conversation history unless `--no-history` is passed:
+   - Read full available local prompt history, not a sample:
+     - `~/.claude/history.jsonl`
+     - `~/.codex/history.jsonl`
+     - `~/.codex/sessions/**/*.jsonl` for Codex session metadata only when needed to map session IDs to cwd.
+   - Filter to records whose project/cwd matches the target repo or whose text mentions the absolute path, repo directory name, package/app name, or repository URL.
+   - Exclude system, developer, tool output, injected skill payloads, and base instruction text from examples.
+   - Use line-by-line parsing for scale and deduplicate Codex prompt records when compact and rich histories overlap.
+   - Extract recent user goals, repeated requests, unresolved questions, blockers, and prior recommendations.
+8. Synthesize status:
+   - What this repo/app is.
+   - What has happened recently.
+   - Current implementation status by major area.
+   - Outstanding work, grouped as blocking, next execution, advisory, manual/human-only, and uncertain.
+   - Mismatches between conversation history, task docs, git history, and code reality.
+   - Confidence level for each major conclusion: high, medium, or low, with evidence.
+9. Recommend next route:
+   - Use phase-aware routing before naming a command:
+     - If `tasks/todo.md` or active phase docs contain actionable implementation work, recommend the approved task artifact route. Do not route back to research merely because advisory gaps exist.
+     - If finished work is dirty, unpushed, unvalidated, or needs packaging/review before handoff, recommend `$ship`.
+     - If user-facing product research/prototype artifacts are missing and no implementation/shipping queue is active, follow the canonical AFPS route from the routing evidence: `customer-discovery -> competitive-analysis -> journey-map -> positioning -> user-flow-map -> ux-variations [specific-user-flow] -> ui-interview [specific-ux-variation] -> prototype -> uat --variant-evaluation -> consolidate-variations -> research-roadmap --post-prototype -> spec-interview -> research-roadmap --post-spec -> roadmap`. Use `$ui-interview --requirements-only` and `$ux-variations --layout-mode` only when the user explicitly needs a fixed content/data/action contract and layout-only alternatives.
+     - If `research/icp.md` and `research/competitive-analysis.md` exist but `research/journey-map.md` is missing, check `customer-lifecycle` availability. If it is not enabled, recommend `npx skillpacks install customer-lifecycle` from the project shell, before `$journey-map`; if enabled, recommend `$journey-map`.
+     - Treat `value-prop-canvas` and `lean-canvas` as optional risk-driven detours only. Before recommending either, check `business-research` availability; if it is not enabled, recommend `npx skillpacks install business-research` from the project shell, before `$value-prop-canvas` or `$lean-canvas`. Recommend `$value-prop-canvas` only for contested solution-fit evidence, and `$lean-canvas` only for material business-model risk; do not make either a default blocker before `journey-map`, `positioning`, `user-flow-map`, or layout-mode UX variations.
+     - If no research, spec, task, implementation, validation, dirty, or unpushed work remains, recommend `$brainstorm` to discover new AFPS work.
+   - Approved task artifact route when the next task is already clear and executable.
+   - `$roadmap` when specs exist but sequencing or task queue health needs updating.
+   - `$feature-interview` when the next idea/direction is not yet represented in specs or tasks.
+   - `$reconcile-dev-docs audit` or `$reconcile-dev-docs fix tasks` when task docs contradict git/code reality.
+   - `$spec-drift` when specs and code appear out of sync.
+   - `$guide` only for human-only external blockers.
+   - `$brainstorm` when the repo is complete/current and the next step is discovering a new phase.
+
+## Output
+
+Produce a structured report with:
+
+- **Overview:** repo path, project purpose, project type, primary apps/packages, branch, dirty/unpushed status.
+- **History Signal:** number of Claude/Codex prompt records scanned, number matched to this repo, date range, and 3-8 concise real examples.
+- **Recent Work:** last commits and task/history evidence.
+- **Current Status:** major areas and whether each appears complete, in progress, blocked, stale, or unknown.
+- **Outstanding Work:** prioritized list with evidence and recommended owner/skill.
+- **Risks And Drift:** contradictions, stale docs, missing tests, manual blockers, or uncertain claims.
+- **Recommended Next Step:** one concrete next work item and one command.
+
+End with exactly:
+
+```md
+**Next work:** <specific task, blocker, discovery task, or "none">
+**Recommended next command:** <one command or route>
+```
+
+## Constraints
+
+- Read-only by default. Do not modify files, create commits, run installs, or execute long test suites unless the user explicitly asks.
+- Do not include private conversation history unrelated to the target repo.
+- Quote only short prompt excerpts. Prefer paraphrase plus timestamp/source/project.
+- Do not treat `tasks/record-todo.md` or `tasks/recurring-todo.md` as execution queues unless an item has clearly become concrete work.
+- Do not put agent-executable work in `tasks/manual-todo.md` or route it to `$guide`.
+- Do not recommend `$roadmap` if the finding is only "tell me the status"; use `$roadmap` only when the task pipeline itself needs queue maintenance or roadmap extension.
+- When recommending a pack skill, first check `.agents/project.json` for `enabled_packs`. If the target skill's pack is not enabled, include `npx skillpacks install <pack-name>` from the project shell, as a prerequisite in the recommendation.
+- Do not create or modify GitHub Actions workflows.
+
+## Default Shipping Contract
+
+- **Default next-step routing:** when reporting completion, include either `Recommended next skill: <command>` or the two-line pair `**Next work:** <specific task or "none">` and `**Recommended next command:** <one command or route>` so the next caller has a concrete handoff.
+- Normally read-only and should not create or modify tracked repository files.
+- If the user explicitly asks this skill to create or modify tracked files, finish by committing and pushing all intended changes to the repository primary branch (`main` when present, otherwise `master`) before stopping.
+- This contract does not override stricter safety rules about secrets, destructive history changes, release publication/tag confirmation, production deploy confirmation, paid actions, or public visibility changes.

package/base/codex/codebase-status/archive/v0.8/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: codebase-status
+description: Report what a repository is, what recent conversation history says about it, current application status, and outstanding work
+type: analysis
+version: v0.8
+argument-hint: "[optional repo path, focus, or --no-history]"
+---
+
+# Codebase Status
+
+Invoke as `$codebase-status`.
+
+Use this skill when the user asks what a repo or application is, where work was left, what is outstanding, whether it is ready/stable, or wants a detailed status report that combines codebase evidence with local Claude/Codex conversation history.
+
+This is read-only status synthesis. It does not replace `$roadmap`: `roadmap` maintains the task pipeline and priority queue; `codebase-status` explains the actual current state of the repo and relevant prior conversations.
+
+## Process
+
+1. Resolve target repo:
+   - Default to the current working directory.
+   - If the user provides a path, use that repo.
+   - Confirm it is a git worktree when possible; if not, continue with filesystem evidence and report that git evidence is unavailable.
+2. Read project orientation:
+   - `README.md`, `AGENTS.md`, `CLAUDE.md`, `.agents/project.json`, package/workspace files, app entrypoints, and high-signal docs.
+   - Identify project type, main apps/packages, runtime, tests, and likely user-facing or developer-facing purpose.
+3. Read planning and status docs when present:
+   - `tasks/roadmap.md`, `tasks/todo.md`, `tasks/manual-todo.md`, `tasks/record-todo.md`, `tasks/recurring-todo.md`, `tasks/history.md`, `tasks/lessons.md`, `tasks/phases/`, `specs/`, `spec.md`, and `research/`.
+   - Distinguish checked-off work, active work, manual blockers, advisory work, stale docs, and missing docs.
+4. Read routing evidence for product, research, or spec repos:
+   - When `research/`, `specs/`, `spec.md`, product docs, or prototype artifacts exist, read `docs/pack-workflow-matrix.md` and `docs/skill-next-step-contracts.md` if present.
+   - Identify the last completed relevant research/product skill from artifacts, task history, or conversation history. Before recommending another research/product skill, consult that skill's active `SKILL.md` `## Next Steps` contract and any `## Next Steps` section in its output artifact.
+   - Treat those route contracts as stronger evidence than a generic status impression. If docs disagree, report the contradiction and prefer the newest active skill contract or route matrix with file evidence.
+   - For pack-local recommendations, check `.agents/project.json` `enabled_packs` first. If the target skill's pack is not enabled, recommend `npx skillpacks install <pack-name>` from the project shell, before the skill.
+5. Inspect git evidence:
+   - `git status --short`
+   - current branch and upstream status
+   - last 20 commits
+   - unpushed commits when an upstream exists
+   - changed files in the working tree
+6. Inspect codebase health signals:
+   - Project structure and primary modules.
+   - Test/build/lint scripts from package manifests or equivalent tool files.
+   - Obvious TODO/FIXME markers, failing-test notes, disabled tests, and local quality scripts.
+   - Do not run expensive commands by default. Run cheap read-only inspections freely; ask or state assumptions before long builds, network installs, destructive commands, or mutation.
+7. Find related conversation history unless `--no-history` is passed:
+   - Read full available local prompt history, not a sample:
+     - `~/.claude/history.jsonl`
+     - `~/.codex/history.jsonl`
+     - `~/.codex/sessions/**/*.jsonl` for Codex session metadata only when needed to map session IDs to cwd.
+   - Filter to records whose project/cwd matches the target repo or whose text mentions the absolute path, repo directory name, package/app name, or repository URL.
+   - Exclude system, developer, tool output, injected skill payloads, and base instruction text from examples.
+   - Use line-by-line parsing for scale and deduplicate Codex prompt records when compact and rich histories overlap.
+   - Extract recent user goals, repeated requests, unresolved questions, blockers, and prior recommendations.
+8. Synthesize status:
+   - What this repo/app is.
+   - What has happened recently.
+   - Current implementation status by major area.
+   - Outstanding work, grouped as blocking, next execution, advisory, manual/human-only, and uncertain.
+   - Mismatches between conversation history, task docs, git history, and code reality.
+   - Confidence level for each major conclusion: high, medium, or low, with evidence.
+9. Recommend next route:
+   - Use phase-aware routing before naming a command:
+     - If `tasks/todo.md` or active phase docs contain actionable implementation work, recommend `$exec`. Do not route back to research merely because advisory gaps exist.
+     - If finished work is dirty, unpushed, unvalidated, or needs packaging/review before handoff, recommend `$ship`.
+     - If user-facing product research/prototype artifacts are missing and no implementation/shipping queue is active, follow the canonical AFPS route from the routing evidence: `customer-discovery -> competitive-analysis -> journey-map -> positioning -> user-flow-map -> ui-interview --requirements-only -> ux-variations --layout-mode -> prototype -> uat --variant-evaluation -> consolidate-variations -> research-roadmap --post-prototype -> spec-interview -> research-roadmap --post-spec -> roadmap`.
+     - If `research/icp.md` and `research/competitive-analysis.md` exist but `research/journey-map.md` is missing, check `customer-lifecycle` availability. If it is not enabled, recommend `npx skillpacks install customer-lifecycle` from the project shell, before `$journey-map`; if enabled, recommend `$journey-map`.
+     - Treat `value-prop-canvas` and `lean-canvas` as optional risk-driven detours only. Before recommending either, check `business-research` availability; if it is not enabled, recommend `npx skillpacks install business-research` from the project shell, before `$value-prop-canvas` or `$lean-canvas`. Recommend `$value-prop-canvas` only for contested solution-fit evidence, and `$lean-canvas` only for material business-model risk; do not make either a default blocker before `journey-map`, `positioning`, `user-flow-map`, or layout-mode UX variations.
+     - If no research, spec, task, implementation, validation, dirty, or unpushed work remains, recommend `$brainstorm` to discover new AFPS work.
+   - `$exec` when the next task is already clear and executable.
+   - `$roadmap` when specs exist but sequencing or task queue health needs updating.
+   - `$feature-interview` when the next idea/direction is not yet represented in specs or tasks.
+   - `$reconcile-dev-docs audit` or `$reconcile-dev-docs fix tasks` when task docs contradict git/code reality.
+   - `$spec-drift` when specs and code appear out of sync.
+   - `$guide` only for human-only external blockers.
+   - `$brainstorm` when the repo is complete/current and the next step is discovering a new phase.
+
+## Output
+
+Produce a structured report with:
+
+- **Overview:** repo path, project purpose, project type, primary apps/packages, branch, dirty/unpushed status.
+- **History Signal:** number of Claude/Codex prompt records scanned, number matched to this repo, date range, and 3-8 concise real examples.
+- **Recent Work:** last commits and task/history evidence.
+- **Current Status:** major areas and whether each appears complete, in progress, blocked, stale, or unknown.
+- **Outstanding Work:** prioritized list with evidence and recommended owner/skill.
+- **Risks And Drift:** contradictions, stale docs, missing tests, manual blockers, or uncertain claims.
+- **Recommended Next Step:** one concrete next work item and one command.
+
+End with exactly:
+
+```md
+**Next work:** <specific task, blocker, discovery task, or "none">
+**Recommended next command:** <one command or route>
+```
+
+## Constraints
+
+- Read-only by default. Do not modify files, create commits, run installs, or execute long test suites unless the user explicitly asks.
+- Do not include private conversation history unrelated to the target repo.
+- Quote only short prompt excerpts. Prefer paraphrase plus timestamp/source/project.
+- Do not treat `tasks/record-todo.md` or `tasks/recurring-todo.md` as execution queues unless an item has clearly become concrete work.
+- Do not put agent-executable work in `tasks/manual-todo.md` or route it to `$guide`.
+- Do not recommend `$roadmap` if the finding is only "tell me the status"; use `$roadmap` only when the task pipeline itself needs queue maintenance or roadmap extension.
+- When recommending a pack skill, first check `.agents/project.json` for `enabled_packs`. If the target skill's pack is not enabled, include `npx skillpacks install <pack-name>` from the project shell, as a prerequisite in the recommendation.
+- Do not create or modify GitHub Actions workflows.
+
+## Default Shipping Contract
+
+- **Default next-step routing:** when reporting completion, include either `Recommended next skill: <command>` or the two-line pair `**Next work:** <specific task or "none">` and `**Recommended next command:** <one command or route>` so the next caller has a concrete handoff.
+- Normally read-only and should not create or modify tracked repository files.
+- If the user explicitly asks this skill to create or modify tracked files, finish by committing and pushing all intended changes to the repository primary branch (`main` when present, otherwise `master`) before stopping.
+- This contract does not override stricter safety rules about secrets, destructive history changes, release publication/tag confirmation, production deploy confirmation, paid actions, or public visibility changes.

package/base/codex/codebase-status/archive/v0.9/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: codebase-status
+description: Report what a repository is, what recent conversation history says about it, current application status, and outstanding work
+type: analysis
+version: v0.9
+argument-hint: "[optional repo path, focus, or --no-history]"
+---
+
+# Codebase Status
+
+Invoke as `$codebase-status`.
+
+Use this skill when the user asks what a repo or application is, where work was left, what is outstanding, whether it is ready/stable, or wants a detailed status report that combines codebase evidence with local Claude/Codex conversation history.
+
+This is read-only status synthesis. It does not replace `$roadmap`: `roadmap` maintains the task pipeline and priority queue; `codebase-status` explains the actual current state of the repo and relevant prior conversations.
+
+## Process
+
+1. Resolve target repo:
+   - Default to the current working directory.
+   - If the user provides a path, use that repo.
+   - Confirm it is a git worktree when possible; if not, continue with filesystem evidence and report that git evidence is unavailable.
+2. Read project orientation:
+   - `README.md`, `AGENTS.md`, `CLAUDE.md`, `.agents/project.json`, package/workspace files, app entrypoints, and high-signal docs.
+   - Identify project type, main apps/packages, runtime, tests, and likely user-facing or developer-facing purpose.
+3. Read planning and status docs when present:
+   - `tasks/roadmap.md`, `tasks/todo.md`, `tasks/manual-todo.md`, `tasks/record-todo.md`, `tasks/recurring-todo.md`, `tasks/history.md`, `tasks/lessons.md`, `tasks/phases/`, `specs/`, `spec.md`, and `research/`.
+   - Distinguish checked-off work, active work, manual blockers, advisory work, stale docs, and missing docs.
+4. Read routing evidence for product, research, or spec repos:
+   - When `research/`, `specs/`, `spec.md`, product docs, or prototype artifacts exist, read `docs/pack-workflow-matrix.md` and `docs/skill-next-step-contracts.md` if present.
+   - Identify the last completed relevant research/product skill from artifacts, task history, or conversation history. Before recommending another research/product skill, consult that skill's active `SKILL.md` `## Next Steps` contract and any `## Next Steps` section in its output artifact.
+   - Treat those route contracts as stronger evidence than a generic status impression. If docs disagree, report the contradiction and prefer the newest active skill contract or route matrix with file evidence.
+   - For pack-local recommendations, check `.agents/project.json` `enabled_packs` first. If the target skill's pack is not enabled, recommend `npx skillpacks install <pack-name>` from the project shell, before the skill.
+5. Inspect git evidence:
+   - `git status --short`
+   - current branch and upstream status
+   - last 20 commits
+   - unpushed commits when an upstream exists
+   - changed files in the working tree
+6. Inspect codebase health signals:
+   - Project structure and primary modules.
+   - Test/build/lint scripts from package manifests or equivalent tool files.
+   - Obvious TODO/FIXME markers, failing-test notes, disabled tests, and local quality scripts.
+   - Do not run expensive commands by default. Run cheap read-only inspections freely; ask or state assumptions before long builds, network installs, destructive commands, or mutation.
+7. Find related conversation history unless `--no-history` is passed:
+   - Read full available local prompt history, not a sample:
+     - `~/.claude/history.jsonl`
+     - `~/.codex/history.jsonl`
+     - `~/.codex/sessions/**/*.jsonl` for Codex session metadata only when needed to map session IDs to cwd.
+   - Filter to records whose project/cwd matches the target repo or whose text mentions the absolute path, repo directory name, package/app name, or repository URL.
+   - Exclude system, developer, tool output, injected skill payloads, and base instruction text from examples.
+   - Use line-by-line parsing for scale and deduplicate Codex prompt records when compact and rich histories overlap.
+   - Extract recent user goals, repeated requests, unresolved questions, blockers, and prior recommendations.
+8. Synthesize status:
+   - What this repo/app is.
+   - What has happened recently.
+   - Current implementation status by major area.
+   - Outstanding work, grouped as blocking, next execution, advisory, manual/human-only, and uncertain.
+   - Mismatches between conversation history, task docs, git history, and code reality.
+   - Confidence level for each major conclusion: high, medium, or low, with evidence.
+9. Recommend next route:
+   - Use phase-aware routing before naming a command:
+     - If `tasks/todo.md` or active phase docs contain actionable implementation work, recommend `$exec`. Do not route back to research merely because advisory gaps exist.
+     - If finished work is dirty, unpushed, unvalidated, or needs packaging/review before handoff, recommend `$ship`.
+     - If user-facing product research/prototype artifacts are missing and no implementation/shipping queue is active, follow the canonical AFPS route from the routing evidence: `customer-discovery -> competitive-analysis -> journey-map -> positioning -> user-flow-map -> ux-variations [specific-user-flow] -> ui-interview [specific-ux-variation] -> prototype -> uat --variant-evaluation -> consolidate-variations -> research-roadmap --post-prototype -> spec-interview -> research-roadmap --post-spec -> roadmap`. Use `$ui-interview --requirements-only` and `$ux-variations --layout-mode` only when the user explicitly needs a fixed content/data/action contract and layout-only alternatives.
+     - If `research/icp.md` and `research/competitive-analysis.md` exist but `research/journey-map.md` is missing, check `customer-lifecycle` availability. If it is not enabled, recommend `npx skillpacks install customer-lifecycle` from the project shell, before `$journey-map`; if enabled, recommend `$journey-map`.
+     - Treat `value-prop-canvas` and `lean-canvas` as optional risk-driven detours only. Before recommending either, check `business-research` availability; if it is not enabled, recommend `npx skillpacks install business-research` from the project shell, before `$value-prop-canvas` or `$lean-canvas`. Recommend `$value-prop-canvas` only for contested solution-fit evidence, and `$lean-canvas` only for material business-model risk; do not make either a default blocker before `journey-map`, `positioning`, `user-flow-map`, or layout-mode UX variations.
+     - If no research, spec, task, implementation, validation, dirty, or unpushed work remains, recommend `$brainstorm` to discover new AFPS work.
+   - `$exec` when the next task is already clear and executable.
+   - `$roadmap` when specs exist but sequencing or task queue health needs updating.
+   - `$feature-interview` when the next idea/direction is not yet represented in specs or tasks.
+   - `$reconcile-dev-docs audit` or `$reconcile-dev-docs fix tasks` when task docs contradict git/code reality.
+   - `$spec-drift` when specs and code appear out of sync.
+   - `$guide` only for human-only external blockers.
+   - `$brainstorm` when the repo is complete/current and the next step is discovering a new phase.
+
+## Output
+
+Produce a structured report with:
+
+- **Overview:** repo path, project purpose, project type, primary apps/packages, branch, dirty/unpushed status.
+- **History Signal:** number of Claude/Codex prompt records scanned, number matched to this repo, date range, and 3-8 concise real examples.
+- **Recent Work:** last commits and task/history evidence.
+- **Current Status:** major areas and whether each appears complete, in progress, blocked, stale, or unknown.
+- **Outstanding Work:** prioritized list with evidence and recommended owner/skill.
+- **Risks And Drift:** contradictions, stale docs, missing tests, manual blockers, or uncertain claims.
+- **Recommended Next Step:** one concrete next work item and one command.
+
+End with exactly:
+
+```md
+**Next work:** <specific task, blocker, discovery task, or "none">
+**Recommended next command:** <one command or route>
+```
+
+## Constraints
+
+- Read-only by default. Do not modify files, create commits, run installs, or execute long test suites unless the user explicitly asks.
+- Do not include private conversation history unrelated to the target repo.
+- Quote only short prompt excerpts. Prefer paraphrase plus timestamp/source/project.
+- Do not treat `tasks/record-todo.md` or `tasks/recurring-todo.md` as execution queues unless an item has clearly become concrete work.
+- Do not put agent-executable work in `tasks/manual-todo.md` or route it to `$guide`.
+- Do not recommend `$roadmap` if the finding is only "tell me the status"; use `$roadmap` only when the task pipeline itself needs queue maintenance or roadmap extension.
+- When recommending a pack skill, first check `.agents/project.json` for `enabled_packs`. If the target skill's pack is not enabled, include `npx skillpacks install <pack-name>` from the project shell, as a prerequisite in the recommendation.
+- Do not create or modify GitHub Actions workflows.
+
+## Default Shipping Contract
+
+- **Default next-step routing:** when reporting completion, include either `Recommended next skill: <command>` or the two-line pair `**Next work:** <specific task or "none">` and `**Recommended next command:** <one command or route>` so the next caller has a concrete handoff.
+- Normally read-only and should not create or modify tracked repository files.
+- If the user explicitly asks this skill to create or modify tracked files, finish by committing and pushing all intended changes to the repository primary branch (`main` when present, otherwise `master`) before stopping.
+- This contract does not override stricter safety rules about secrets, destructive history changes, release publication/tag confirmation, production deploy confirmation, paid actions, or public visibility changes.

package/{global/claude → base/codex}/idea-scope-brief/ALIGNMENT-PAGE.md

@@ -9,6 +9,8 @@ When this skill produces durable deliverables (research, specs, plans, reports,
 
 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.
 
+**Context intake.** This skill declares `context_intake: deep` (Deep interview). Gather repo/project context before asking, present an assumptions manifest when the contract requires it, ask focused questions, and confirm coverage before building review artifacts.
+
 **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, local section-feedback YAML only after a section feedback choice is selected, and one bottom `Compile Responses` control. `confirmed` is the post-approval page after the agent has consumed final compiled response 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.
@@ -57,7 +59,9 @@ The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected
 
 **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 response 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 response 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-idea-scope-brief-research.md`; product-path mode uses `research/{slug}/_working/preliminary-idea-scope-brief-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. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and 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.
+**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, research-scope approval gates, and a `Stage 2 Preview / Expected Review Format` section that shows the future Stage 2 review shape before research starts. Stop for final compiled response 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 response 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-idea-scope-brief-research.md`; product-path mode uses `research/{slug}/_working/preliminary-idea-scope-brief-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 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. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and 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.
+
+**Stage 2 review-page template.** Stage 1 scope-review pages must include a `Stage 2 Preview / Expected Review Format` section that previews the exact section sequence, table shapes, evidence treatment, visual density, and approval gates the user will see after research; make it specific enough for the user to flag preferred content formats, grouping, labels, visuals, and evidence density before the agent does heavy research. After scope approval and research, the Stage 2 review page must include these sections as structured HTML, not as raw Markdown dumps: `Research Scope Approved` status block with approved scope, source plan, output paths, and unresolved caveats; `Executive Findings` or a skill-specific top-findings section with confidence labels; `Evidence Matrix` mapping claim, evidence/source/path, inference, confidence, assumptions, and decision impact; `Working Packet Review` with the complete working-packet substance rendered as purpose-built HTML sections, lists, tables, matrices, cards, and tier-appropriate charts or diagrams; `Alternatives / Rejected or Lower-Confidence Findings`; `Source Coverage & Gaps`; `Assumptions / Confidence Register`; `Proposed Canonical Artifacts & File Changes`; a required `User Format Preferences` gate asking whether the layout, tables, grouping, visuals, labels, and evidence density match expectations; and a required `Final Artifact Approval` gate for Stage 3 readiness. Raw Markdown packet text, search logs, or source notes may appear only as supplemental source views after the rendered review UI and never replace the Stage 2 review sections.
 
 **Idea-specific gates.** Render the Idea Assumptions Manifest as a first-class assumptions/confidence gate inside the alignment page before proposed deliverables. The idea identity, slug, scope/non-goals, ICP readiness, and output-location/change-scope decisions must each be reviewable gates. Apply the shared artifact-destination/proposed-file-changes de-duplication rule: combine them into one visual gate when they ask only the same path-destination question, and render separate gates when destination approval differs from downstream mutation scope, timing, or allowed files.
 

package/{global → base}/codex/idea-scope-brief/CHANGELOG.md

@@ -1,5 +1,9 @@
 # idea-scope-brief Changelog
 
+## v0.17 - 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.16 - 2026-06-11
 
 - Added Deck Fit Handoff routing so completed idea briefs prefer matching saved repo decks from `.agents/project.json` `saved_decks` / `decks`, then fall back to canonical decks (`vard`, `ord`, `business-afps`, `devtool-afps`, `game-afps`).