Agent skill · Documentation

analyze

Analyze consistency across spec, plan, tasks, and checklist. Use before implementation. Triggers on: analyze consistency, check artifacts, validate feature.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill analyze-arvorco-relentless --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/analysis/analyze-arvorco-relentless/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

# Cross-Artifact Consistency Analyzer Validate consistency across feature artifacts before implementation. --- ## SpecKit Workflow This skill is **Step 5 of 6** in the Relentless workflow: specify → plan → tasks → convert → **analyze** → implement Prerequisites (ALL must exist): - `spec.md` - Feature specification - `plan.md` - Technical implementation plan - `tasks.md` - User stories and tasks - `prd.json` - Converted PRD with routing metadata (run convert first) - `checklist.md` - Quality validation checklist (recommended) Purpose: - Validate consistency across ALL artifacts - Catch gaps before implementation begins - **Ensure TDD and routing compliance** - **Verify quality gates are defined** --- ## The Job 1. Read all feature artifacts 2. Check for consistency issues 3. **Validate TDD compliance** 4. **Validate routing metadata** 5. **Validate quality gates** 6. Validate against constitution 7. Generate analysis report --- ## Files to Analyze Required: - `relentless/constitution.md` - `relentless/features/NNN-feature/spec.md` - `relentless/features/NNN-feature/plan.md` - `relentless/features/NNN-feature/tasks.md` - `relentless/features/NNN-feature/prd.json` - `relentless/featur

What's inside
Steps it walks through
  1. SpecKit Workflow
  2. The Job
  3. Files to Analyze
  4. Validation Checks
  5. 1. Completeness
  6. 2. TDD Compliance Validation (MANDATORY)
  7. 3. Routing Metadata Validation (MANDATORY)
  8. 4. Quality Gates Validation (MANDATORY)
  9. 5. Constitution Compliance
  10. 6. Dependency Consistency
  11. 7. Scope Consistency
  12. 8. Data Model Consistency
  13. 9. API Consistency
  14. 10. Testing Coverage
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the analyze skill do?

Analyze consistency across spec, plan, tasks, and checklist. Use before implementation. Triggers on: analyze consistency, check artifacts, validate feature.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill analyze-arvorco-relentless --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
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.