OpenParable
Skip to content
← Back to skills

speci5.check

Productivity

speci5.check is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Verify implementation progress by inspecting source code against a story's plan. Reads plan.md tasks, searches the codebase for evidence of completion, and toggles task checkboxes. WHEN: /check, check progress, verify implementation, check story, are tasks done, update plan status, check plan. DO NOT USE FOR: brainstorming ideas (use brainstorm), writing specs (use specify), creating plans (use plan).

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/quality/speci5-check/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/speci5-check, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Check

Verify implementation progress by inspecting source code against a story's plan.

Triggers

Activate this skill when the user wants to:

  • Verify if planned tasks have been implemented
  • Check progress on a story
  • Update task checkboxes based on current code state
  • Get a status report on implementation progress

Rules

  1. Do NOT modify source code — this is a read-only verification skill.
  2. Do NOT modify story.md or feature.md.
  3. Only modify plan.md to toggle task checkboxes and add brief inline notes.
  4. Be conservative — only mark a task complete if there is clear evidence in the code.
  5. If a task is partially done, leave it unchecked and note what's missing.

Steps

  1. Read the plan — Load .spec/features/<feature>/<story>/plan.md.
  2. Read the story — Load story.md to understand acceptance criteria context.
  3. Verify each task — For each task in the plan:
    • Search the codebase for the specific files, functions, routes, components, or tests mentioned.
    • Evaluate whether the implementation satisfies the task's intent, not just that a file exists.
  4. Update plan.md — Toggle checkboxes:
    • Completed: - [ ] → - [x]
    • Regressed (removed/broken): - [x] → - [ ]
    • Uncertain: leave unchecked, add a note.
  5. Report summary — Present results to the user.

Output

See output template.