Agent skill · Security

analyze-spec

Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill analyze-spec-sequenzia-agent-alchemy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 13 KB
Bundled scripts: none
Allowed tools: AskUserQuestionTaskReadGlobTaskCreateTaskUpdateTaskList
Path: skills/analysis/analyze-spec-sequenzia-agent-alchemy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Spec Analysis Skill You are initiating the spec analysis workflow. This process will analyze an existing spec for quality issues, optionally guide the user through resolving them interactively, and optionally create fix tasks from approved findings. ## Load Reference Skills For task creation from findings (Step 8), load the Tasks reference: ``` Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-tasks/SKILL.md ``` ## Workflow ### Step 1: Validate File Verify the spec file exists at the provided path. If not found: - Check if user provided relative path and try common locations - Use Glob to search for similar filenames - Ask user for correct path if needed ### Step 2: Read Spec Content Read the entire spec file using the Read tool. ### Step 3: Detect Depth Level Analyze the spec content to detect its depth level: **Full-Tech Indicators** (check first): - Contains `API Specifications` section OR `### 7.4 API` or similar - Contains API endpoint definitions (`POST /api/`, `GET /api/`, etc.) - Contains `Testing Strategy` section - Contains data model schemas **Detailed Indicators**: - Uses numbered sections (`## 1.`, `### 2.1`) - Contains `Technical Architecture` section -

What's inside
Steps it walks through
  1. Load Reference Skills
  2. Workflow
  3. Step 1: Validate File
  4. Step 2: Read Spec Content
  5. Step 3: Detect Depth Level
  6. Step 4: Check Settings
  7. Step 5: Determine Report Paths
  8. Step 6: Launch Analyzer Agent
  9. Step 7: Handoff Complete
  10. Step 8: Create Fix Tasks (Optional)
  11. Example Usage
  12. Notes
  13. Analysis Philosophy
  14. Depth-Aware Analysis
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the analyze-spec skill do?

Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill analyze-spec-sequenzia-agent-alchemy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going