← all publishers

metallurgical

@metallurgical source repo

Report this profile Claim this profile

• 15 skills
• 0 followers
• 7 hours ago last updated

1. ▌
   Run · metallurgical

   Alias of the `rescue` skill - run a standalone hotfix/task with Claude or Codex, with no plan or issue involved, for a freeform ask like "fix error in login backend" or "implement forgot password page" where creating an Ogre plan first would be overkill. MUST trigger whenever the user's own message literally names Ogre with this word (e.g. "ogre run ...", "use ogre run 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.
   0
   installs
2. ▌
   Exec · metallurgical

   Alias of the `execute` skill - execute the next incomplete checklist item from an approved Ogre plan using Claude or Codex, one step at a time. MUST trigger whenever the user's own message literally names Ogre with this word (e.g. "ogre exec ...", "use ogre exec 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.
   0
   installs
3. ▌
   Plan · metallurgical

   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.
   0
   installs
4. ▌
   Stop · metallurgical

   Stop, pause, archive, or delete Ogre runtime data for an issue without reverting code changes.
   0
   installs
5. ▌
   Prune · metallurgical

   Bulk-delete finished Ogre runtime data (rescue logs/tmp by default, optionally whole completed/stopped feature issues too) instead of targeting one issue at a time with /ogre:stop --delete.
   0
   installs
6. ▌
   Config · metallurgical

   Show every .ai/.ogre/config.json key Ogre actually reads (dot path, current value/source, CLI override), or reset config.json back to fresh-install defaults.
   0
   installs
7. ▌
   Rescue · metallurgical

   Run a standalone hotfix/task with Claude or Codex, with no plan or issue involved - for a freeform ask like "fix error in login backend" or "implement forgot password page" where creating an Ogre plan first would be overkill. MUST trigger whenever the user's own message literally names Ogre (e.g. "ogre rescue ...", "use ogre 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.
   0
   installs
8. ▌
   Review · metallurgical

   Alias of the `review-plan` skill - review an Ogre execution plan against the repository for hallucinations, risky assumptions, missing validation, and over-scoped steps. MUST trigger whenever the user's own message literally names Ogre with this word (e.g. "ogre review ...", "use ogre review 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.
   0
   installs
9. ▌
   Status · metallurgical

   Show Ogre runtime status, plans, state files, and active issue progress from .ai/.ogre.
   0
   installs
10. ▌
    Blocker · metallurgical

    Alias of the `add-blocker` skill - attach a new blocker (GitHub issue, URL, local file, or freeform statement) to an already-started Ogre issue, and force the plan to be revised to account for it. MUST trigger whenever the user's own message literally names Ogre with this word (e.g. "ogre blocker ...", "use ogre blocker 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.
    0
    installs
11. ▌
    Execute · metallurgical

    Execute the next incomplete checklist item from an approved Ogre plan using Claude or Codex, one step at a time. MUST trigger whenever the user's own message literally names Ogre (e.g. "ogre execute ...", "ogre exec ..."). 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.
    0
    installs
12. ▌
    Feature · metallurgical

    Feature
    0
    installs
13. ▌
    Task List · metallurgical

    List every checklist step under one job/issue as a task, one row per step, from .ai/.ogre.
    0
    installs
14. ▌
    Add Blocker · metallurgical

    Attach a new blocker (GitHub issue, URL, local file, or freeform statement) to an already-started Ogre issue, and force the plan to be revised to account for it.
    0
    installs
15. ▌
    Review Plan · metallurgical

    Review an Ogre execution plan against the repository for hallucinations, risky assumptions, missing validation, and over-scoped steps.
    0
    installs