source-command-plan-product

Name: source-command-plan-product
Availability: InStock
Author: CHRONiiC

Execute the migrated plan-product command to plan and install Agent OS.

Updated May 14, 2026

Search Tags:#migration #slash command #command execution #product planning #codex skills #agent os

Ready to run

npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-plan-product-chroniicallydiistracted

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-command-plan-product
Source: https://github.com/chroniicallydiistracted/LorcanaChamp/tree/main/references/lorcana-simulator/.agents/skills/source-command-plan-product
Command: npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-plan-product-chroniicallydiistracted

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you execute the migrated plan-product slash command without reimplementing the original behavior from scratch.

Core Features & Use Cases

Plans and installs Agent OS in a product codebase: Generates a migration-aware plan that targets the destination repository and its Agent OS setup.
Routes to the correct canonical instructions: Uses the referenced plan-product guidance in the core instruction file to keep behavior consistent.
Flags manual migration gaps: Calls out that any provider-specific slash-command runtime expansion must be manually rewritten for the Codex skill workflow.

Quick Start

Use this skill when you want to run the migrated source command plan-product and produce an Agent OS setup plan for a product repository.

Frequently Asked Questions about source-command-plan-product

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate and run the plan-product command in Codex skills?▼

To migrate the plan-product command, invoke the canonical instructions from the referenced core file to execute the slash command and generate an Agent OS setup plan in your target codebase.

What does the migrated plan-product slash command do for my codebase?▼

The plan-product command generates a migration-aware workflow plan that targets your destination repository to install and configure Agent OS for product planning.

Do I need to manually rewrite provider-specific slash-command behavior for Codex?▼

Yes, you must manually rewrite any provider-specific slash-command runtime expansion as explicit skill instructions to achieve Codex-aligned behavior instead of relying on provider expansion.

How do I install Agent OS in a product repository using a migrated command?▼

Installing Agent OS requires running the migrated plan-product command, which routes to the referenced canonical guidance and produces a targeted setup plan for your destination repository.

Can I use this skill if my original slash command relies on provider runtime expansion?▼

Yes, but the skill flags manual migration gaps where provider-specific slash-command runtime expansion must be explicitly rewritten as skill instructions to ensure Codex-aligned behavior.

Why does my migrated slash command need canonical instruction references?▼

Canonical instruction references keep behavior consistent by routing the migrated plan-product command to the original guidance in the core instruction file rather than reimplementing it from scratch.