Borrowing it
Nothing to install: this file belongs to jmanhype/speckit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmanhype/speckit/main/.claude/skills/spec-kit-workflow/SKILL.mdgit clone --depth 1 https://github.com/jmanhype/speckitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jmanhype/speckit/spec-kit-workflow)<a href="https://agentmods.dev/skills/jmanhype/speckit/spec-kit-workflow"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/spec-kit-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jmanhype/speckit/spec-kit-workflow"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/spec-kit-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00907 |
| Opus 5.5 | $0.00020 | $0.00363 |
| Sonnet 5.5 | $0.00010 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
spec-kit-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit Workflow Skill
You are assisting with a project that uses Spec Kit - a specification-driven development framework. This skill ensures proper workflow adherence.
Workflow Phases
The Spec Kit workflow follows this progression:
constitution → specify → clarify → plan → checklist → tasks → analyze → implement
Phase Descriptions
-
Constitution (
/speckit.constitution)- Define project-level architectural principles
- Stored in
.specify/memory/constitution.md - One-time setup per project
-
Specify (
/speckit.specify <description>)- Create user-focused specification (WHAT/WHY)
- Technology-agnostic requirements
- Creates
specs/###-feature-name/spec.md
-
Clarify (
/speckit.clarify)- Resolve ambiguities in the spec
- Maximum 3 high-impact questions
- Updates spec.md with answers
-
Plan (
/speckit.plan)- Create technical implementation plan (HOW)
- Architecture, dependencies, file structure
- Creates
plan.mdin feature directory
-
Checklist (
/speckit.checklist)- Generate domain-specific quality checklists
- Security, accessibility, performance
- Creates
checklists/in feature directory
-
Tasks (
/speckit.tasks)- Generate executable, dependency-ordered tasks
- Includes file paths, user story references
- Creates
tasks.mdin feature directory
-
Analyze (
/speckit.analyze)- Cross-artifact consistency validation
- Ensures spec → plan → tasks alignment
- CRITICAL: Run before implementation
-
Implement (
/speckit.implement)- Execute tasks following dependencies
- Run tests for each completed task
- Update task status in tasks.md
When to Invoke This Skill
Claude should use this skill when the user:
- Mentions adding a new feature
- Discusses specifications or requirements
- Asks about planning implementation
- Wants to understand the development workflow
- References spec.md, plan.md, or tasks.md files
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 124 lines · 49 tokens per session scan A fe7583a4393d
spec-kit-workflow is a skill published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 49 tokens to every session and 907 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
work-beads
Use for /work-beads, a requested Beads backlog batch, or implementation of named bead IDs.
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
launch-checklist
Launch readiness across every department: code, content, store, marketing, community, infrastructure, legal, go/no-go sign-offs.
sprint-plan
New or updated sprint plan from the current milestone, completed work, and available capacity.
day-one-patch
Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.
release-checklist
Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.