task-compliance

Verify codebase changes against task file requirements and classify compliance.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Codagent-AI/agent-skills --skill task-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-compliance
Source: https://github.com/Codagent-AI/agent-skills/tree/main/skills/task-compliance
Command: npx skills add https://github.com/Codagent-AI/agent-skills --skill task-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementations often miss subtle requirements from task files, leading to incomplete features that fail to meet stakeholder expectations and require costly rework after shipping.

Core Features & Use Cases

  • Full Requirement Extraction: Pulls every spec scenario (WHEN/THEN), Done When criterion, and explicit background instruction from task files to build a complete compliance checklist.
  • Implementation Cross-Check: Verifies each checklist item against the actual codebase, classifying items as addressed, missed, or partially addressed, with mandatory code verification before marking items as missed.
  • Use Case: After completing a new payment processing feature per a task file, use this skill to confirm all required error handling, transaction logging, and success scenario implementations are present before opening a pull request.

Quick Start

Use the task-compliance skill to review the current feature implementation against its associated task file and report any missing or incomplete requirements.

Frequently Asked Questions about task-compliance

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

FAQPage Schema
How do I verify code changes meet all task file requirements before shipping?

To verify task compliance before shipping, extract all spec scenarios, Done When criteria, and background instructions from task files, then cross-reference each item against actual codebase changes to classify them as addressed, missed, or partially addressed.

What is requirement verification for pre-shipment code validation?

Requirement verification for pre-shipment validation is the process of checking software implementations against defined task files to ensure every spec scenario and Done When criterion is fully addressed before opening a pull request.

How do I check spec adherence and catch missed requirements in my codebase?

Check spec adherence by building a compliance checklist from task file requirements, then verifying each item against the actual codebase to identify and address missed or partially implemented scenarios before they reach production.

Can I use gap analysis to validate bug fixes and feature implementations against task specifications?

Yes, gap analysis validates both bug fixes and feature implementations by cross-referencing task file requirements against codebase changes, classifying each requirement as addressed, missed, or partially addressed to ensure full compliance.

What's the best way to perform implementation checks on a new payment processing feature?

Perform implementation checks by extracting all required error handling, transaction logging, and success scenarios from the associated task file, then verifying each requirement exists in the codebase before opening a pull request.

Does the requirement verification process require code verification before marking a requirement as missed?

Yes, mandatory code verification is required before marking any requirement as missed, ensuring the cross-check accurately classifies spec scenarios and Done When criteria as addressed, partially addressed, or genuinely missed.