Specsmith init
Scaffolds the Specsmith specs/ structure into the current project — copies the specs/ README and the spec/plan/tasks templates from the installed plugin into the project root so prompt-grill and the spec-driven flow have a local home. Use when the user installs Specsmith and wants the specs/ scaffold in their project, says "init specsmith", "set up specs", "add the spec template", or before starting the spec-driven flow in a project that has no specs/ folder yet.From its SKILL.md
npx -y skills add murilobauck/specsmith --skill specsmith-initAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 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.9 KB, as published. Nobody here has run it
Specsmith Init
Goal: drop the Specsmith specs/ scaffold into the user's project so the
spec-driven flow has a local home (a README explaining the cycle and a
_template/ with validated spec.md, plan.md, tasks.md templates).
What to do
- Locate the plugin's bundled scaffold. It lives at
specs/inside the installed Specsmith plugin. Resolve the plugin root via the${CLAUDE_PLUGIN_ROOT}environment variable. If it is not set in the shell, find the plugin under~/.claude/plugins/cache/(look for thespecsmithplugin directory containingspecs/README.mdandspecs/_template/). - Copy into the user's project root:
specs/README.mdspecs/_template/spec.mdspecs/_template/plan.mdspecs/_template/tasks.md
- Never overwrite existing files. If a target already exists, leave it untouched and report which files were skipped. Create directories as needed.
- Report what was created vs. skipped, then point the user at the next step:
run
prompt-grillto producespecs/<feature>/spec.md.
Notes
- This is a one-time, opt-in scaffold — not a wizard and not per-project generated config. It only copies static files.
- The scaffold is optional:
prompt-grillworks without it (it carries the spec structure itself). The local scaffold is for teams who want the README and theplan.md/tasks.mdtemplates checked into their repo.