Spec Driven Development
FredAntB/Spec-Driven-Development
A skill your agent uses to scaffold Spec Driven Development: requirements.md, design.md, tasks.md, and cross-compatible AI config files (CLAUDE.md, .cursorrules, .windsurfrules…
ACEHarness Spec Coding skill for generating, reviewing, revising, and executing spec-first requirements/design/tasks artifacts tied to workflow steps.
$ npx skills add TheAceTeam/AceHarness --skill aceharness-spec-coding -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheAceTeam/AceHarness aceharness-spec-coding --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/TheAceTeam/AceHarness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/aceharness-spec-coding .claude/skills/aceharness-spec-coding && 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 "aceharness-spec-coding" agent skill from https://github.com/TheAceTeam/AceHarness/tree/main/skills/aceharness-spec-coding into .claude/skills/aceharness-spec-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aceharness-spec-coding", 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/TheAceTeam/AceHarness/tree/main/skills/aceharness-spec-codingType 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 TheAceTeam/AceHarness --skill aceharness-spec-coding -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheAceTeam/AceHarness aceharness-spec-coding --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheAceTeam/AceHarness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/aceharness-spec-coding .agents/skills/aceharness-spec-coding && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aceharness-spec-coding" agent skill from https://github.com/TheAceTeam/AceHarness/tree/main/skills/aceharness-spec-coding into .agents/skills/aceharness-spec-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aceharness-spec-coding", 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 TheAceTeam/AceHarness --skill aceharness-spec-coding -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheAceTeam/AceHarness aceharness-spec-coding --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheAceTeam/AceHarness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/aceharness-spec-coding .cursor/skills/aceharness-spec-coding && 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 "aceharness-spec-coding" agent skill from https://github.com/TheAceTeam/AceHarness/tree/main/skills/aceharness-spec-coding into .cursor/skills/aceharness-spec-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aceharness-spec-coding", 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/TheAceTeam/AceHarness.git --path skills/aceharness-spec-coding--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 TheAceTeam/AceHarness --skill aceharness-spec-coding -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheAceTeam/AceHarness aceharness-spec-coding --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheAceTeam/AceHarness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/aceharness-spec-coding .gemini/skills/aceharness-spec-coding && 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 "aceharness-spec-coding" agent skill from https://github.com/TheAceTeam/AceHarness/tree/main/skills/aceharness-spec-coding into .gemini/skills/aceharness-spec-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aceharness-spec-coding", 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 TheAceTeam/AceHarness aceharness-spec-codingInstalls 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 TheAceTeam/AceHarness --skill aceharness-spec-coding -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheAceTeam/AceHarness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/aceharness-spec-coding .github/skills/aceharness-spec-coding && 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 "aceharness-spec-coding" agent skill from https://github.com/TheAceTeam/AceHarness/tree/main/skills/aceharness-spec-coding into .github/skills/aceharness-spec-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aceharness-spec-coding", 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 TheAceTeam/AceHarness --skill aceharness-spec-coding -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheAceTeam/AceHarness aceharness-spec-coding --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheAceTeam/AceHarness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/aceharness-spec-coding .opencode/skills/aceharness-spec-coding && 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 "aceharness-spec-coding" agent skill from https://github.com/TheAceTeam/AceHarness/tree/main/skills/aceharness-spec-coding into .opencode/skills/aceharness-spec-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aceharness-spec-coding", 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.
aceharness-spec-codingACEHarness Spec Coding skill for generating, reviewing, revising, and executing spec-first requirements/design/tasks artifacts tied to workflow steps.
Aceharness Spec Coding is an agent skill from TheAceTeam/AceHarness. ACEHarness Spec Coding skill for generating, reviewing, revising, and executing spec-first requirements/design/tasks artifacts tied to workflow steps. Use when turning rough workflow requirements into actionable requirements.md, design.md, tasks.md, when revising AI-generated specs, or when keeping SpecCoding artifacts aligned with workflow execution.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `PROMPT.md`, `examples/executable-spec.md` and `templates/checklist.md`).
It sits in Development, covering Design tokens and Spec-driven development.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 7122bf6. 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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From 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.
Aceharness Spec Coding loads about 2.7k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 1,206 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,206 words (~2,704 tokens).
“Turn rough workflow intent into three executable planning artifacts:”
SKILL.md and 6 other files in skills/aceharness-spec-coding of TheAceTeam/AceHarness.
Open the folder on GitHubat commit 7122bf6
Aceharness Spec Coding 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 |
|---|---|---|---|---|---|---|
| Aceharness Spec Coding this skillTheAceTeam/AceHarness | 105 | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| Spec Driven DevelopmentFredAntB/Spec-Driven-Development | 153 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Oft Spec Driven Developmentitsallcode/openfasttrace | 197 | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Design TrackerDeL-TaiseiOzaki/claude-code-orchestra | 199 | — | ~2k | Automated safety check: Pass | MIT | |
| Verifying Modulestelagod/code-abyss | 243 | — | ~431 | Automated safety check: Notes | MIT | |
| Yoga Go Desktop UIchapar-rest/chapar | 715 | — | ~2.8k | Automated safety check: Pass | BSD-3-Clause |
FredAntB/Spec-Driven-Development
A skill your agent uses to scaffold Spec Driven Development: requirements.md, design.md, tasks.md, and cross-compatible AI config files (CLAUDE.md, .cursorrules, .windsurfrules…
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…
DeL-TaiseiOzaki/claude-code-orchestra
Record a project design decision into .claude/docs/DESIGN.md through the shared typed writer.
telagod/code-abyss
Scans directory structure, detects missing documentation, and verifies code-doc synchronization.
chapar-rest/chapar
Guides building desktop interfaces with the Yoga Go framework: Body views, layout nodes, widgets, dialogs and headless builds.
NVIDIA/Personal-AI-Router
Kaizen UI (KUI) component library and design-pattern advisor for NVIDIA applications.
TheAceTeam/AceHarness
A skill your agent uses when the user wants AI to play Chinese-style Werewolf, host a Werewolf table, simulate roles such as seer/werewolf/witch/hunter/guard/villager, or produce structured…
TheAceTeam/AceHarness
用 rulesregistry 辅助 PR/代码评审:准备 diff(git/PR/编码 agent 上下文)→ L0 扫描 → selectrules 路由 → 四步判定 → rule-issue-reports 上报。
TheAceTeam/AceHarness
使用 ACEHarness 运行时提供的 workspace SQLite 能力创建和维护 Skill 数据库. An agent skill from TheAceTeam/AceHarness.
TheAceTeam/AceHarness
ACEHarness workflow creation skill. An agent skill from TheAceTeam/AceHarness.
TheAceTeam/AceHarness
通用可视化卡片渲染技能。
TheAceTeam/AceHarness
使用 ACEHarness 内置 RAG/LanceDB 知识库进行只读检索。
Categories
ACEHarness Spec Coding skill for generating, reviewing, revising, and executing spec-first requirements/design/tasks artifacts tied to workflow steps. Aceharness Spec Coding is an agent skill from TheAceTeam/AceHarness. ACEHarness Spec Coding skill for generating, reviewing, revising, and executing spec-first requirements/design/tasks artifacts tied to workflow steps.
Aceharness Spec Coding fits situations like: turning rough workflow requirements into actionable requirements.md; revising AI-generated specs; keeping SpecCoding artifacts aligned with workflow execution.
Run `npx skills add TheAceTeam/AceHarness --skill aceharness-spec-coding -a claude-code`. Or copy the skill folder (skills/aceharness-spec-coding in TheAceTeam/AceHarness) into .claude/skills/aceharness-spec-coding in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheAceTeam/AceHarness --skill aceharness-spec-coding -a codex`. Or copy the skill folder (skills/aceharness-spec-coding in TheAceTeam/AceHarness) into .agents/skills/aceharness-spec-coding 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 TheAceTeam/AceHarness --skill aceharness-spec-coding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aceharness-spec-coding, .gemini/skills/aceharness-spec-coding, .github/skills/aceharness-spec-coding and .opencode/skills/aceharness-spec-coding in your project.
SKILL.md names no scripts, command-line tools or credentials: Aceharness Spec Coding is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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.
Aceharness Spec Coding has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 2.7k tokens (SKILL.md is roughly 11k 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 Aceharness Spec Coding: Spec Driven Development (FredAntB/Spec-Driven-Development, 153 stars), Oft Spec Driven Development (itsallcode/openfasttrace, 197 stars), Design Tracker (DeL-TaiseiOzaki/claude-code-orchestra, 199 stars) and Verifying Modules (telagod/code-abyss, 243 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
TheAceTeam (a GitHub organization) maintains it in TheAceTeam/AceHarness, which has 105 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 3, 2026.
Source: TheAceTeam/AceHarness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.