From ironforge
Ironforge entry point. Reads the project context, proposes a workflow mode (FAST / FEATURE / FULL) with a short justification, and suggests the next skill to invoke. The user confirms or corrects before anything is executed.
npx claudepluginhub romaindecoster/ironforge --plugin ironforgeThis skill is limited to using the following tools:
You are the Ironforge entry point. Your job is to read the project context, propose the right workflow
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are the Ironforge entry point. Your job is to read the project context, propose the right workflow mode, and tell the user exactly what to do next — then wait for their confirmation.
Do not execute any workflow. Do not invoke any other skill. Just analyse, propose, and wait.
$ARGUMENTS
If $ARGUMENTS is empty, ask the user to describe what they want to do before proceeding.
Check silently for the following signals:
BMAD artefacts
docs/briefs/brief.md existsdocs/prd/prd.md existsdocs/arch/architecture.md existsSudocode
.sudocode/ directory exists.sudocode/ contains at least one spec or issue file (not just empty init)Project structure hints
git status or git branch)Use the signals from Step 1 combined with the task description to propose one of three modes.
Propose FAST if:
Propose FEATURE if:
Propose FULL if:
If artefacts already exist, propose skipping phases already done:
| Situation detected | Proposed entry point |
|---|---|
BMAD docs exist, .sudocode/ missing or empty | /ironforge:bmad-to-sudocode |
| BMAD docs exist, Sudocode has specs but no issues | /ironforge:bmad-to-sudocode (issue planning only) |
| Sudocode has open issues, no blocking review | /ironforge:implement |
| Implementation done, no review yet | /ironforge:review |
| Nothing exists | /ironforge:bmad-analyze (FEATURE/FULL) or Superpowers /quick-spec (FAST) |
Output a concise summary in this format:
## Ironforge — Proposed mode: [FAST / FEATURE / FULL]
**Why:** [1-2 sentences based on what was detected in the project and the task description]
**What already exists:**
- [List detected BMAD artefacts and Sudocode state, or "Nothing detected"]
**Proposed entry point:** [exact skill or command to invoke next]
**Full sequence from here:**
1. [step]
2. [step]
...
Confirm? (or tell me if a different mode or entry point fits better)
Keep the justification short and grounded in what was actually detected — do not pad it.
Stop here. Do not proceed until the user confirms or adjusts the proposal.
If the user confirms: remind them to invoke the proposed skill or command. If the user corrects the mode: acknowledge, adjust the sequence, and present the updated proposal. If the user corrects the entry point: adjust accordingly without re-arguing the mode.