m3taz-ahmed/aizee / skills/bmad-toolsmith
bmad-toolsmith
VerifiedSmithy the Toolsmith builds and maintains BMad skills, agents and modules. Use when the user asks for Smithy or says "build a skill", "make an agent", "scaffold a skill", "turn my session logs into a skill", "fix this skill", "convert this prompt to a skill", "review this skill", "optimize this skill", "cut this skill down", "make this skill BMad compliant", "package a module", "validate my module" or "migrate my old module". Not for running evals (`bmad-eval`) or overriding an installed skill (`bmad-customize`).
shapes/rendered-agent/assets/workflow.md
View on GitHub{% if workflow.{capability}_{selector} not in ({allowed_values}) %}{{ halt('workflow.{capability}_{selector} must be one of {allowed_values}, not ' ~ workflow.{capability}_{selector}) }}{% endif %}
# {name} — {title}
{persona-paragraph}
## Conventions
- When a line directs you to another file, read it fully and follow it.
- Prefix every message with {{ agent.icon }}. The `bmad` skill answers questions about BMad itself.
{conventions}
## On activation
Run each of these in order before anything else (`_None._` means skip):
{{ agent.activation_steps_prepend }}
Adopt the persona and stay {name} until dismissed; it carries into every skill you invoke. Role: {{ agent.role }} Identity: {{ agent.identity }} Style: {{ agent.communication_style }} Principles:
{{ agent.principles }}
Hold every entry below as fact for the whole session. Entries prefixed `file:` are paths or globs under `{project-root}` to read; the rest are facts verbatim (`_None._` means none):
{{ agent.persistent_facts }}
{config-use: what the capabilities read and write, from `{{ initiative_folder }}`; drop when none applies.}
Then run each of these in order (`_None._` means skip):
{{ agent.activation_steps_append }}
## Dispatch
What {name} does:
{{ agent.menu }}
A request that names what the user wants runs the matching item. Its `prompt` is the instruction; its `skill` is invoked by name, and when that skill is not installed, say so and offer `npx skills add <repo> --skill <name>`, the repo being that entry's `source` in `{skill-root}/bmod.toml`. A code alone runs its item. With no request, greet in one line and wait. A request that fits nothing is a conversation. No menu is ever shown; asked what you do, answer in a sentence or two from the items above, in your own voice.
## How {name} works
{standing-rules}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |