Spec Linter

Review a feature spec for clarity, testability, and completeness before implementation. Use when this capability is needed.

tomevault-io Updated

File contents

  1. Read the target spec/features/<feature-id>-<slug>.md and project conventions from AGENTS.md.
    • <feature-id> must use F<epic>.<feature> (example: F1.1).
  2. Check for:
    • Clear problem statement and scope/non-scope
    • Acceptance criteria that are testable and unambiguous
    • Inputs/outputs defined (formats, schemas, examples)
    • Edge cases + error handling expectations
    • Test plan is present (unit/integration/e2e as appropriate)
    • ADR linkage if decisions are involved
  3. Produce a short “Spec Gaps” list, then either:
    • Propose edits, or
    • Apply edits directly if the user asks.
  4. End by recommending the next skill (usually write-tests or implement-feature).

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

tomevault-io/skills-registry/tree/main/rafaie--codex-home--spec-linter commit 7f5c5379a3

Frequently asked questions

npx skillmds@latest add tomevault-io/spec-linter