Spec Verify logo

Spec Verify

Community
jh941213
spec-verify

SPEC.md 명세서 대비 구현 완료도를 검증합니다. Triggers on: 스펙 검증, spec-verify, 명세서 검증, 구현 검증. NOT for: 코드 리뷰, 단위 테스트, 빌드 검증.

Overview

Publisherjh941213
Repositorymy-cc-harness
Skill namespec-verify
Stars
125
Forks
35
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by jh941213 on GitHub. Read the source before you install it.

Installation

Install the Spec Verify AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jh941213/my-cc-harness.git /tmp/my-cc-harness
mkdir -p .claude/skills
cp -r /tmp/my-cc-harness/skills/spec-verify .claude/skills/spec-verify
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Spec Verify in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Spec Verify on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Spec Verify is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

SPEC 검증

명세서 기반 작업 완료 후 검증하는 스킬입니다.

트리거

  • "스펙 검증", "spec-verify", "명세서 검증", "구현 검증"

워크플로우

1단계: 서브에이전트 생성

Task 도구를 사용하여 검증 에이전트를 생성합니다:

subagent_type: "Explore"
prompt: |
  SPEC.md 파일을 읽고 다음을 검증하세요:

  1. 명세서의 모든 요구사항이 구현되었는지 확인
  2. 각 항목별 체크:
     - [ ] 기능적 요구사항
     - [ ] 비기능적 요구사항
     - [ ] UI/UX 명세
     - [ ] API 설계 (해당 시)
     - [ ] 보안 고려사항

  3. 누락된 항목이 있으면 구체적으로 명시
  4. 개선 제안 사항 포함

  결과를 텍스트로 반환하세요. (Explore 서브에이전트는 읽기 전용 — 파일 작성 금지)

서브에이전트는 결과를 텍스트로 반환하고, 반환된 결과를 SPEC-REVIEW.md 파일로 작성하는 것은 본 스킬(부모)이 수행합니다.

2단계: 피드백 반영

검증 결과에 누락 사항이 있으면:

  1. SPEC-REVIEW.md 내용을 사용자에게 보여줌
  2. 수정 여부 확인 (AskUserQuestion 사용)
  3. 승인 시 누락 사항 구현

3단계: 완료 보고

모든 항목이 완료되면:

markdown
## 검증 완료

### 구현 상태
- [x] 기능적 요구사항: 100%
- [x] 비기능적 요구사항: 100%
- [x] UI/UX: 100%
- [x] 테스트: 100%

### 주의사항
- ...

### 다음 단계 제안
- ...

검증 체크리스트

markdown
## SPEC 검증 체크리스트

### 기능 완성도
- [ ] 모든 기능적 요구사항 구현됨
- [ ] 모든 엣지 케이스 처리됨
- [ ] 에러 핸들링 적절함

### 코드 품질
- [ ] 타입 안전성 확보
- [ ] 린트 규칙 준수
- [ ] 테스트 커버리지 충분

### 문서화
- [ ] 코드 주석 적절
- [ ] API 문서 (해당 시)
- [ ] README 업데이트

### 보안
- [ ] 입력 검증
- [ ] 인증/권한 확인
- [ ] 민감 정보 보호

핵심 원칙

  1. 객관적 검증: 명세서 대비 실제 구현 비교
  2. 구체적 피드백: "안 됨" 대신 "X 기능의 Y 부분 누락"
  3. 반복 가능: 피드백 → 수정 → 재검증 사이클

Frequently asked questions

What does the Spec Verify AI skill do?

SPEC.md 명세서 대비 구현 완료도를 검증합니다. Triggers on: 스펙 검증, spec-verify, 명세서 검증, 구현 검증. NOT for: 코드 리뷰, 단위 테스트, 빌드 검증.

Why use Spec Verify on TypingMind?

Because you install it once and use it with any model. Spec Verify is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Spec Verify in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jh941213/my-cc-harness/tree/main/skills/spec-verify. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Spec Verify?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Spec Verify?

As many as you like. As long as a model supports skills, you can use Spec Verify with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Spec Verify AI skill free?

It is published on GitHub by jh941213. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇