speckit-analyze SKILL.md skillA

speckit-analyze from pisberg/vibetags is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add pisberg/vibetags/speckit-analyze@git:20260920.e596793

Pins git:20260920.e596793 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

pisberg/vibetags

Path

.claude/skills/speckit-analyze/SKILL.md

Versions recorded

1

Latest version

git:20260920.e596793, committed Sep 20, 2026

Size

10,970 bytes

Repository stars

25

License

MIT

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

## User Input

```text
$ARGUMENTS
```

You **MUST** consider the user input before proceeding (if not empty).

## Pre-Execution Checks

**Check for extension hooks (before analysis)**:
- Check if `.specify/extensions.yml` exists in the project root.
- If it exists, read it and look for entries under the `hooks.before_analyze` key
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
- For each executable hook, output the following based on its `optional` flag:
  - **Optional hook** (`optional: true`):
    ```
    ## Extension Hooks
…

Read the whole file at its exact version.

How to install

mdr add pisberg/vibetags/speckit-analyze@sha256:adb9c4baed1d0e27

[![mdr](https://markdownregistry.com/badge/art_cmkxw6h2q3zb3smh.svg)](https://markdownregistry.com/a/art_cmkxw6h2q3zb3smh)

Versions

The registry has recorded 1 version of this file, committed on Sep 20, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_cmkxw6h2q3zb3smh
GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/speckit-analyze
GET https://markdownregistry.com/api/v1/blob/adb9c4baed1d0e27cebd08e506a7247c1357ee721b6ea340201553d5792e6c8a

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from pisberg/vibetags

Every file in pisberg/vibetags

Other files named speckit-analyze

Browse by kind, by grade A, or by owner.