ワンクリックでManusで任意のスキルを実行

speckit-analyze

スター5

フォーク4

更新日2026年5月14日 19:22

Audit consistency between spec.md, plan.md, tasks.md, and the actual code in the pickup-points-modal — flagging drift, missing tasks, or out-of-spec changes before PR review.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vtex

vtex/pickup-points-modal

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

speckit-analyze

Lightweight audit before opening the PR. Detects drift across the four artifacts: spec → plan → tasks → code.

When to use

After speckit-implement and before gh pr create.
When the spec author is different from the implementer.
Before requesting human review on a large feature.

Checks

Spec → Plan: does every acceptance criterion from the spec appear as an item in the plan?
Plan → Tasks: does every file listed under "Files to touch" have at least one task?
Tasks → Code: is every file modified in git diff covered by some task?
Constitution check: does the diff respect the 5 principles?

Output

A markdown report listing:

✅ Items in sync
⚠️ Drift (changed in code but not in the task/spec)
❌ Missing (acceptance criterion without implementation)

It does not fix anything — it only reports. The user decides whether to update spec/plan or revert the code.

Important

speckit-analyze is read-only. It never edits the spec, plan, tasks or code. If drift is found, it returns the report and stops.

このリポジトリの他の Skills

同じリポジトリ

implementing

vtex/pickup-points-modal

Implement an approved spec end-to-end in the pickup-points-modal repo — branch, code, tests, lint, typecheck, build, commit, and open a PR following Conventional Commits and the project constitution.

2026-05-145

specification

vtex/pickup-points-modal

Generate an SDD (Spec Driven Development) document for a new feature in the pickup-points-modal, covering Business Context, Architectural Decisions, and Technical Contract before any code is written.

2026-05-145

speckit-checklist

vtex/pickup-points-modal

Generate a per-feature validation checklist (pre-merge gates, manual QA steps, rollback plan) for a pickup-points-modal feature, tailored to the spec and constitution principles.

2026-05-145

speckit-clarify

vtex/pickup-points-modal

Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.

2026-05-145

speckit-constitution

vtex/pickup-points-modal

Create or amend the project constitution in .specify/memory/constitution.md, capturing binding principles, governance, and ratification metadata for the pickup-points-modal.

2026-05-145

speckit-git-commit

vtex/pickup-points-modal

Compose Conventional Commits messages and stage the right files for a pickup-points-modal change, respecting CHANGELOG and the constitution's backward-compat principle.

2026-05-145

name	speckit-analyze
description	Audit consistency between spec.md, plan.md, tasks.md, and the actual code in the pickup-points-modal — flagging drift, missing tasks, or out-of-spec changes before PR review.
type	skill

speckit-analyze

Lightweight audit before opening the PR. Detects drift across the four artifacts: spec → plan → tasks → code.

When to use

After speckit-implement and before gh pr create.
When the spec author is different from the implementer.
Before requesting human review on a large feature.

Checks

Spec → Plan: does every acceptance criterion from the spec appear as an item in the plan?
Plan → Tasks: does every file listed under "Files to touch" have at least one task?
Tasks → Code: is every file modified in git diff covered by some task?
Constitution check: does the diff respect the 5 principles?

Output

A markdown report listing:

✅ Items in sync
⚠️ Drift (changed in code but not in the task/spec)
❌ Missing (acceptance criterion without implementation)

It does not fix anything — it only reports. The user decides whether to update spec/plan or revert the code.

Important

speckit-analyze is read-only. It never edits the spec, plan, tasks or code. If drift is found, it returns the report and stops.