How do I install the Spectra Spec skill?

Run npx skillmds@latest add ahmedhamadto/spectra-spec in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Spectra Spec skill do?

Run a deep Alignment analysis — compare your original spec against what was actually built. It is listed under Coding & Dev Tools on SkillMD.

Is Spectra Spec safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spectra Spec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spectra Spec free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spectra Spec?

ahmedhamadto (@ahmedhamadto) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spectra Spec by ahmedhamadto — Agent Skill

Name: Spectra Spec
Author: ahmedhamadto

File contents

Run a deep Alignment analysis — compare your original spec against what was actually built.

Target

Spec alignment for: $ARGUMENTS

If no path is specified, analyse the current working directory.

Spec Input

The user MUST provide their original spec or prompt. If they haven't, ask for it before proceeding. The spec can be:

Pasted after running the command
Provided inline: /spectra-spec ./src I asked for a task API with auth and email notifications
A file path to a spec document

Scope

Skip: node_modules, dist, build, .git, pycache, vendor, lock files, binary files, cosmetic config.
Include: runtime config that affects behaviour.
Read the full codebase to understand what was built.

Output Structure

# ⚡ Spectra Spec Alignment

**Spec Coverage:** X% of requirements fully implemented

Then a deep analysis in these sections:

Faithful Implementations

Line-by-line mapping of spec requirements to implementations. For each requirement: what was asked → where it's implemented → assessment (complete/partial/missing).

Silent Decisions

Every decision the AI made that wasn't in the spec. For EACH:

What was chosen: e.g., "Express over Fastify"
What alternatives existed: e.g., "Fastify, Hono, Koa"
Whether it's reasonable: e.g., "Reasonable — largest ecosystem, most middleware"
When it might be wrong: e.g., "If you need >50K req/sec, Fastify would be faster"

Be exhaustive. Check: database, ORM, auth strategy, framework, folder structure, error handling, API patterns, middleware, logging, config management, testing framework, validation library, deployment config.

Gaps

Every spec requirement that isn't fully implemented. Classify each as:

Missing entirely: no trace in the codebase
Partially implemented: some code exists but it's incomplete
Stubbed out: placeholder code, TODO comments, empty functions

Extras

Everything built that wasn't in the spec. Classify each as:

Useful addition: genuinely helpful, worth keeping
Premature optimisation: not needed at current scale
Unnecessary complexity: adds maintenance burden without current value

Misinterpretations

Things built that don't match the spec's intent. For each: what was asked → what was built → how they differ.

Spec Coverage Score

Calculate: (fully implemented requirements / total requirements) × 100% List each requirement as ✅ implemented, ⚠️ partial, or ❌ missing.

Rules

NEVER mention AI or AI-generated code in the output.
Be precise. "Email notifications: not implemented" is better than "some features may be missing."
Silent decisions are not criticisms. Frame neutrally.
If everything matches the spec, say so clearly.

---name: spectra-specdescription: Run a deep Alignment analysis — compare your original spec against what was actually built.---Run a deep Alignment analysis — compare your original spec against what was actually built.## TargetSpec alignment for: $ARGUMENTSIf no path is specified, analyse the current working directory.## Spec InputThe user MUST provide their original spec or prompt. If they haven't, ask for it before proceeding. The spec can be:- Pasted after running the command- Provided inline: `/spectra-spec ./src I asked for a task API with auth and email notifications`- A file path to a spec document## Scope- Skip: node_modules, dist, build, .git, __pycache__, vendor, lock files, binary files, cosmetic config.- Include: runtime config that affects behaviour.- Read the full codebase to understand what was built.## Output Structure```# ⚡ Spectra Spec Alignment**Spec Coverage:** X% of requirements fully implemented```Then a deep analysis in these sections:### Faithful ImplementationsLine-by-line mapping of spec requirements to implementations. For each requirement: what was asked → where it's implemented → assessment (complete/partial/missing).### Silent DecisionsEvery decision the AI made that wasn't in the spec. For EACH:- **What was chosen**: e.g., "Express over Fastify"- **What alternatives existed**: e.g., "Fastify, Hono, Koa"- **Whether it's reasonable**: e.g., "Reasonable — largest ecosystem, most middleware"- **When it might be wrong**: e.g., "If you need >50K req/sec, Fastify would be faster"Be exhaustive. Check: database, ORM, auth strategy, framework, folder structure, error handling, API patterns, middleware, logging, config management, testing framework, validation library, deployment config.### GapsEvery spec requirement that isn't fully implemented. Classify each as:- **Missing entirely**: no trace in the codebase- **Partially implemented**: some code exists but it's incomplete- **Stubbed out**: placeholder code, TODO comments, empty functions### ExtrasEverything built that wasn't in the spec. Classify each as:- **Useful addition**: genuinely helpful, worth keeping- **Premature optimisation**: not needed at current scale- **Unnecessary complexity**: adds maintenance burden without current value### MisinterpretationsThings built that don't match the spec's intent. For each: what was asked → what was built → how they differ.### Spec Coverage ScoreCalculate: (fully implemented requirements / total requirements) × 100%List each requirement as ✅ implemented, ⚠️ partial, or ❌ missing.## Rules- NEVER mention AI or AI-generated code in the output.- Be precise. "Email notifications: not implemented" is better than "some features may be missing."- Silent decisions are not criticisms. Frame neutrally.- If everything matches the spec, say so clearly.

Frequently asked questions

Spectra Spec