check

Compare actual work against a predefined plan to identify discrepancies.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/whilp/working --skill check-whilp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/whilp/working/tree/main/skills/check
Command: npx skills add https://github.com/whilp/working --skill check-whilp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain the integrity of work by comparing actual work against a predefined plan, identifying discrepancies, and ensuring adherence to quality standards.

Core Features & Use Cases

  • Plan Review: Compare the actual work with the predefined plan.
  • Issue Detection: Identify issues, such as missing features or changes not in line with the plan.
  • Automated Validation: Validate changes through automated builds and tests.
  • Use Case: After a developer merges code, use the 'check' skill to ensure the new code adheres to the project plan, passes automated tests, and does not introduce any out-of-scope changes.

Quick Start

Execute the 'check' skill by providing the work item JSON and verify the results.

Frequently Asked Questions about check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate code changes against a predefined project plan?

Plan review compares actual work execution against a predefined plan to identify discrepancies. Use this process after merging code to ensure changes adhere to the project plan, pass automated tests, and avoid out-of-scope modifications.

How do I detect out-of-scope changes during a pull request review?

Issue detection identifies missing features or changes not in line with the plan during code reviews. By analyzing the work item JSON, it flags discrepancies between actual execution and the predefined project scope.

Do I need Git and make to run automated build validation for PRs?

Yes, Git and make are required to run automated build validation for pull requests. The validation process relies on these tools to execute custom scripts, verify automated tests, and ensure work execution aligns with the plan.

What is the best way to ensure work execution aligns with the plan?

Ensuring work execution aligns with the plan is best achieved through automated validation and issue detection. By comparing actual work with the predefined plan, you can identify discrepancies and verify that changes pass automated builds and tests.

Can I use custom scripts for plan adherence and issue detection?

Yes, you can use custom scripts for plan adherence and issue detection. The validation process applies specific scripts to verify work execution, identify discrepancies, and ensure changes adhere to the predefined project plan.

When should I not use automated validation for code review?

Automated validation for code review should not be used when you cannot provide a work item JSON or predefined plan. Without these inputs, the process cannot compare actual work execution or identify discrepancies and out-of-scope changes.