← ClaudeAtlas

specs-skillslisted

Use when asked to spec out a feature, write a spec, create spec.md / plan.md / tasks.md, do spec-driven development, use GitHub Spec Kit or speckit, or set up .specify/ in a repo. Works in repos that have never been initialized with spec-kit. Triggers on "spec this out", "specify", "SDD", "write the spec and plan", "generate tasks from the spec".
rohitguta2432/agentic-os-skills · ★ 0 · AI & Automation · score 60
Install: claude install-skill rohitguta2432/agentic-os-skills
# specs-skills — one invocation, the whole Spec Kit set Turn a one-line requirement into a complete `specs/NNN-slug/` artifact set using the real `github/spec-kit`, in any repo, whether or not it has been initialized. ## Step 0 — Ensure the kit is present Check for `.specify/` in the repo root. **Missing?** Install it (needs `uvx`, already on PATH): ```bash uvx --from git+https://github.com/github/spec-kit.git specify init --here \ --integration claude --script sh --force --ignore-agent-tools ``` This writes `.specify/` (templates + bash scripts + `memory/constitution.md`) and the ten `speckit-*` skills into `.claude/skills/`. **Install fails** (no network, uvx gone, flag renamed)? Say so in one line, then fall back: read `~/.claude/skills/specs-skill/SKILL.md` and follow it instead. It is self-contained and produces the same artifacts without spec-kit. Stop after that — do not attempt the stages below. ## Step 1 — Run the stages <HARD-GATE> Skills installed in Step 0 are NOT invocable this session. Claude Code loads `.claude/skills/` at session start, so the `speckit-*` skills you just wrote to disk do not exist as far as the Skill tool is concerned. Calling `Skill(speckit-specify)` fails or silently picks up nothing. **Read each `SKILL.md` with the Read tool and follow its instructions yourself.** This is the only mechanism that works on a fresh install. Use it unconditionally so behavior does not differ between fresh and already-initialized repos. </HARD-GATE>