本文へ移動
cccskills
無料GitHub で公開

spec-audit

Audit and migrate specs to the Guarantees + Constraints format. Use when asked to review spec quality, find non-conforming specs, or batch-migrate specs from the old Behaviors/Interfaces format.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md2.5 KB
  • references/format-checklist.md1.6 KB
  • references/migration-patterns.md3.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Spec Audit

Overview

Systematically audit specs in the Mighty graph for format compliance, then migrate non-conforming specs to the canonical Guarantees + Constraints structure.

When to use

  • After adopting the new spec format and needing to migrate existing specs.
  • Periodic hygiene: find specs with missing sections, stale prose, or structural issues.
  • Before a major planning push: ensure the spec tree is clean and navigable.

Audit workflow

1) Scan the tree

mt tree --all

Walk each root and its children. For every spec, run mt show <id> and check against the format checklist (references/format-checklist.md).

2) Identify non-conforming specs

Flag specs that have any of:

  • ## Behaviors or ## Interfaces sections (old format)
  • Missing ## Guarantees section
  • Missing ## Constraints section (acceptable only if truly no constraints exist — annotate why)
  • Unstructured prose instead of bullet lists
  • Nesting deeper than 3 levels in the spec tree
  • Orphan specs (no parent, not a root)

3) Migrate specs

Use mt show --json <id> | jq -r '.description' to get the current description, then transform it following the migration patterns (references/migration-patterns.md).

Apply with:

cat <<'EOF' | mt update <id> --description-file -
<new description>
EOF

4) Validate tree structure

After migration, verify:

  • Max 3 levels deep (root → mid → leaf)
  • Every non-root spec has a parent via child_of edge
  • Root specs are area/capability buckets, not implementation details
  • Parent summaries still accurately describe their children

5) Batch workflow

Process in tree order — roots first, then children:

  1. Migrate root/parent specs first (they set the framing for children)
  2. Migrate children, checking consistency with parent
  3. After migrating children, re-read parent to update its summary if children changed scope
  4. Leave a comment on each migrated spec: mt comment --on <id> --content "Migrated to Guarantees + Constraints format"

Reference files

  • Format compliance checklist: references/format-checklist.md
  • Old → new migration patterns: references/migration-patterns.md
  • Canonical spec template: see .codex/skills/plan/references/spec-template.md
  • Spec examples by domain: see .codex/skills/plan/references/examples.md

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Optimize a pydantic-ai agent's instructions, tool descriptions, output type, and signature inputs using the gepa CLI. Trigger when the user asks to "optimize this agent", "improve tool descriptions", iterate on prompts driven by eval failures, or otherwise improve a pydantic-ai agent against a dataset. Operates in the user's repo with full filesystem access — YOU are the reflection model; the gepa CLI handles minibatches, evaluation, and Pareto bookkeeping.

日本語の概要は準備中です。原文の説明を表示しています。

indexedlabs/pydantic-ai-gepa362026年10月7日 更新

mighty

無料

Use the `mt` tool to work with this repo’s Mighty graph: run `mt prime` at session start; prefer `mt search`/`mt tree`/`mt show` before reading code; create specs/decisions/tasks and link evidence; triage `mt inbox`; and close out with `mt closeout` then `mt commit`. For full workflow + templates, run `mt prime`.

日本語の概要は準備中です。原文の説明を表示しています。

indexedlabs/pydantic-ai-gepa362026年10月7日 更新

Resolve `.mighty/loro/*.loro` merge conflicts safely using `mt merge`, then verify store health and sync.

日本語の概要は準備中です。原文の説明を表示しています。

indexedlabs/pydantic-ai-gepa362026年10月7日 更新

plan

無料

Plan work using Mighty (mt) by creating/updating specs and recording decisions, then spawning/structuring implementation tasks. Use when asked to plan/outline/break down a change, draft a spec (feature/rule/invariant/bug), record an ADR-style decision, or turn a fuzzy request into a structured Mighty spec tree with linked tasks.

日本語の概要は準備中です。原文の説明を表示しています。

indexedlabs/pydantic-ai-gepa362026年10月7日 更新

Convert roman numerals to integers.

日本語の概要は準備中です。原文の説明を表示しています。

indexedlabs/pydantic-ai-gepa362026年10月7日 更新

tasks

無料

Track and execute implementation work using Mighty (mt) tasks, with progress comments, linked evidence, recorded decisions, and clean closeout. Use when asked to fix a bug, implement a feature/refactor, or “work through” changes in code while keeping Mighty tasks/specs/decisions updated.

日本語の概要は準備中です。原文の説明を表示しています。

indexedlabs/pydantic-ai-gepa362026年10月7日 更新

indexedlabs のスキルをすべて見る

このスキルの問題を報告する