Review Spd
zhu1090093659/spec_driven_develop
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.
GitHub Spec-Kit integration for constitution-based spec-driven development.
$ npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Microck/ordinary-claude-skills spec-kit-skill --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_all/spec-kit-skill .claude/skills/spec-kit-skill && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spec-kit-skill" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/spec-kit-skill into .claude/skills/spec-kit-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kit-skill", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/spec-kit-skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Microck/ordinary-claude-skills spec-kit-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills_all/spec-kit-skill .agents/skills/spec-kit-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec-kit-skill" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/spec-kit-skill into .agents/skills/spec-kit-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kit-skill", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Microck/ordinary-claude-skills spec-kit-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills_all/spec-kit-skill .cursor/skills/spec-kit-skill && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spec-kit-skill" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/spec-kit-skill into .cursor/skills/spec-kit-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kit-skill", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Microck/ordinary-claude-skills.git --path skills_all/spec-kit-skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Microck/ordinary-claude-skills spec-kit-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills_all/spec-kit-skill .gemini/skills/spec-kit-skill && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spec-kit-skill" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/spec-kit-skill into .gemini/skills/spec-kit-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kit-skill", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Microck/ordinary-claude-skills spec-kit-skillInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills_all/spec-kit-skill .github/skills/spec-kit-skill && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spec-kit-skill" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/spec-kit-skill into .github/skills/spec-kit-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kit-skill", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Microck/ordinary-claude-skills spec-kit-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills_all/spec-kit-skill .opencode/skills/spec-kit-skill && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spec-kit-skill" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/spec-kit-skill into .opencode/skills/spec-kit-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kit-skill", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
spec-kit-skillGitHub Spec-Kit integration for constitution-based spec-driven development.
Spec Kit Skill is an agent skill from Microck/ordinary-claude-skills. GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).
It sits in Development, covering Spec-driven development. It works with GitHub. The repository describes itself as: An unappealing collection of Claude Skills and resources.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1056d29. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
uvuvxFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comAlso links to:
docs.astral.shFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Spec Kit Skill loads about 5k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 1,041 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,041 words (~5,028 tokens).
“Official GitHub Spec-Kit integration providing a 7-phase constitution-driven workflow for feature development.”
SKILL.md and 1 other file in skills_all/spec-kit-skill of Microck/ordinary-claude-skills.
Open the folder on GitHubat commit 1056d29
Spec Kit Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spec Kit Skill this skillMicrock/ordinary-claude-skills | 401 | — | ~5k | Automated safety check: Pass | Custom licence | |
| Review Spdzhu1090093659/spec_driven_develop | 983 | — | ~1.5k | Automated safety check: Pass | MIT | |
| React Router RFC Implementerremix-run/react-router | 57k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Spec Driven Developzhu1090093659/spec_driven_develop | 983 | — | ~5.1k | Automated safety check: Pass | MIT | |
| SddSpillwaveSolutions/sdd-skill | 105 | — | ~5.7k | Automated safety check: Pass | MIT | |
| Speckit Taskstoissueskunstmusik/blue | 154 | 17 repos | ~2k | Automated safety check: Pass | GPL-3.0 |
zhu1090093659/spec_driven_develop
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.
remix-run/react-router
Turns a React Router RFC discussion on GitHub into an implementation, weighing community feedback and settling open questions with you before coding.
zhu1090093659/spec_driven_develop
Automates pre-development workflow for large-scale complex tasks.
SpillwaveSolutions/sdd-skill
This skill should be used when users want guidance on Spec-Driven Development methodology using GitHub's Spec-Kit.
kunstmusik/blue
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
itsallcode/openfasttrace
Support spec-driven development in projects that use OpenFastTrace, a system-requirements document in doc/systemrequirements.md, an arc42-style design in doc/design.md, and per-issue task plans in…
Microck/ordinary-claude-skills
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide.
Microck/ordinary-claude-skills
Generate and edit images using the Gemini API (Nano Banana Pro).
Microck/ordinary-claude-skills
Write Ruby gems following Andrew Kane's proven patterns and philosophy.
Microck/ordinary-claude-skills
Execute Codex CLI for code analysis, refactoring, and automated code changes.
Microck/ordinary-claude-skills
Review documentation changes for compliance with the Metabase writing style guide.
Microck/ordinary-claude-skills
This skill should be used when managing the file-based todo tracking system in the todos/ directory.
Works with
Categories
GitHub Spec-Kit integration for constitution-based spec-driven development. Spec Kit Skill is an agent skill from Microck/ordinary-claude-skills. GitHub Spec-Kit integration for constitution-based spec-driven development.
Spec Kit Skill fits situations like: working with spec-kit CLI; .specify/ directories; creating specifications with constitution-driven development.
Run `npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a claude-code`. Or copy the skill folder (skills_all/spec-kit-skill in Microck/ordinary-claude-skills) into .claude/skills/spec-kit-skill in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a codex`. Or copy the skill folder (skills_all/spec-kit-skill in Microck/ordinary-claude-skills) into .agents/skills/spec-kit-skill in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Microck/ordinary-claude-skills --skill spec-kit-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-kit-skill, .gemini/skills/spec-kit-skill, .github/skills/spec-kit-skill and .opencode/skills/spec-kit-skill in your project.
Going by SKILL.md and its folder, Spec Kit Skill needs the command-line tools its instructions call (uv and uvx). Our summary lists: Python 3.
SKILL.md names 2 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: docs.astral.sh. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Spec Kit Skill has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Spec Kit Skill: Review Spd (zhu1090093659/spec_driven_develop, 983 stars), React Router RFC Implementer (remix-run/react-router, 57k stars), Spec Driven Develop (zhu1090093659/spec_driven_develop, 983 stars) and Sdd (SpillwaveSolutions/sdd-skill, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Microck (a GitHub user) maintains it in Microck/ordinary-claude-skills, which has 401 GitHub stars. The repository holds 97 skills in this directory. The repository was last updated on September 6, 2026.
Source: Microck/ordinary-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.