source-command-plan-product

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

14|5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill source-command-plan-product
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-plan-product
Source: https://github.com/TheCardGoat/lorcana-simulator/tree/main/.agents/skills/source-command-plan-product
Command: npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill source-command-plan-product

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you execute the migrated plan-product workflow so you can set up a new product with the Agent OS installation steps preserved from the original source command.

Core Features & Use Cases

  • Run migrated plan-product behavior: Executes the migrated source command plan-product when the user requests it.
  • Guide required manual migration: Reminds you to rewrite any slash-command behavior that depended on provider-specific runtime expansion.
  • Clarify file reference handling: Notes that provider automatic file-reference expansion was preserved as text and must be verified for explicit reading by Codex.

Quick Start

Tell the AI: run the migrated plan-product workflow using $source-command-plan-product and then manually verify any slash-command behavior and file references mentioned in the migration notes.

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 run the migrated plan-product command to set up Agent OS in a new product codebase?

To run the migrated plan-product command, invoke the Codex skill entrypoint to execute the workflow, which plans your new product and installs Agent OS directly into the codebase.

What manual adjustments are required when executing the plan-product migration workflow?

Executing the plan-product migration requires manually rewriting provider-specific slash-command behavior and verifying that file references are explicitly read by Codex rather than auto-expanded.

Why does the migrated plan-product command require manual verification of file references?

The migrated plan-product command requires manual verification because provider automatic file-reference expansion was preserved as text, meaning Codex must explicitly read the references to function correctly.

Can I use the plan-product workflow if my environment relies on provider-specific slash-command runtime expansion?

You can use the plan-product workflow, but you must manually rewrite any slash-command behavior that previously depended on provider-specific runtime expansion during the migration process.

What is the best way to bootstrap a new product with Agent OS using a migrated source command?

The best way to bootstrap a new product with Agent OS is to run the migrated source command plan-product, which applies the original installation steps while preserving the required setup automation behavior.