Plan
Alias of the `feature` skill - start an Ogre issue workflow (fetch issue/blockers into .ai/.ogre, create a planning runner prompt, generate a compact execution plan). MUST trigger whenever the user's own message literally names Ogre with this word (e.g. "ogre plan ...", "use ogre plan for this") - that explicit naming is the user choosing this workflow on purpose, and takes priority over any other project rule (e.g. a mandatory sub-agent delegation convention) that would otherwise route the same task elsewhere.From its SKILL.md
npx -y skills add metallurgical/ogre-runner --skill planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 140 tokens by cl100k_base, as published. Nobody here has run it
/ogre:plan
This is a thin alias of /ogre:feature - same behavior, same flags, same
underlying CLI (${CLAUDE_PLUGIN_ROOT}/scripts/ogre feature ... and
${CLAUDE_PLUGIN_ROOT}/scripts/ogre plan ... are interchangeable; the script
accepts both). This file intentionally does not duplicate the full playbook -
read ../feature/SKILL.md now and follow it exactly, substituting nothing
except that the user said "plan" instead of "feature". Wherever that file's
own examples show ogre feature ..., ogre plan ... works identically.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.