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`).
approaches/lean.md
View on GitHub# Lean
The outcome: the smallest skill that does the job, tried once on the user's real input before it is polished, at `{target}`.
## Scaffold
`uv run {skill-root}/scripts/init_skill.py --name <name> --dest <parent folder> --shape <shape> --description "<approved description>"`, with `--dirs` for only the folders the execution plan listed and `--bmod <record> --source <update_source>` when the execution plan registers it as a member.
A single-skill module, the default, gets its `bmod.toml` and `help/help.md` from `shapes/single-skill-module/shape.md` at the write step.
Then load `shapes/<shape>/shape.md`.
## Write the smallest version
Write `SKILL.md` to `canon.md`. Show the draft and the description in chat before writing any further file, because a user who moves the bar now saves every file written after it.
## Try it
When the user has a real input, run the skill on it once through a subagent that sees only `{target}` and the input, and read the trace, not just the output.
What the trace means:
- Several approaches tried before one worked, or stalling between alternatives: no default was named. Name one.
- An instruction followed where it did not apply: narrow its condition.
- The same helper rewritten each run: bundle it as a script.
- A line the run never needed: cut it.
Fix what the trace shows, once, and record the decision.
Where discovery ran the trigger phrase bare, compare against it: a line that changed nothing goes. Otherwise judge the trace against the execution plan's outcome and bar.
Without a real input, ask for one; if none exists, apply the canon's tests line by line and tell the user the skill has not run.
## Then
Load `ship.md`, which runs the lenses and offers evals; run neither here.
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 |