seabbs

Check Requirements — Development skill for Claude Code

Development community

Verify completed work against original requirements: $ARGUMENTS.

How to install Check Requirements

Installs to ~/.claude/skills/seabbs-claude-check-requirements/SKILL.md

Terminal
mkdir -p ~/.claude/skills/seabbs-claude-check-requirements && curl -fsSL https://raw.githubusercontent.com/seabbs/claude/HEAD/commands/check-requirements.md -o ~/.claude/skills/seabbs-claude-check-requirements/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Check Requirements does


argument-hint: [issue-or-spec]

Verify completed work against original requirements: $ARGUMENTS

  1. Extract all requirements from the source (issue, spec, user request)
  2. Break down into atomic, verifiable components
  3. Examine the implementation (code, docs, tests)
  4. Map each change to specific requirements
  5. Perform gap analysis with status for each requirement:
    • Fully Satisfied / Partially Satisfied / Not Satisfied / Modified / Extra
  6. Check for regressions, side effects, and s

Alternatives in Development

  • Om Tidy — Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits ove 4.6k ★
  • Compass Planner — Use the @compass-planner agent to help the user create a work plan for the following: $ARGUMENTS 523 ★
  • Overnight PRs — Autonomous overnight loop — verify issues against the codebase, close stale ones, ship PRs through /ship (bug 324 ★

Full documentation available on GitHub

View Source Repository