Validate a specification document against spec-rules.md
Validates specification documents against required structure and quality standards. Use this when you need to verify a SPEC.md file has all necessary sections (Task, Background, Current State, Requirements, Success Criteria) before creating implementation plans.
/plugin marketplace add edspencer/claude-agents/plugin install product-team@edspencer-agentsspec-fileYour task is to validate a SPEC.md file ($1) against the requirements in spec-rules.md and provide structured feedback.
Read the specification document and validate it against Check .claude/docs/processes/spec-rules.md (project) OR ~/.claude/plugins/marketplaces/edspencer-agents/plugins/product-team/docs/processes/spec-rules.md (plugin). This is a read-only validation task - do not modify the spec file.
Check the following aspects:
File Location and Naming:
./tasks/[task-name]/SPEC.md formatRequired Structure:
Content Quality:
Completeness:
Provide a structured feedback report with two parts:
Create a file called SPEC-STATUS.md containing a 2-paragraph content overview that someone can read to understand what the specification covers. This should answer: "What requirements does this specification define? What is the scope and key goals?"
Format:
Example:
This specification outlines requirements for implementing user account deletion functionality. The feature must allow users to permanently delete their accounts and associated data while maintaining system integrity and compliance with data protection regulations.
Key requirements include: database cleanup of all user records, notification of deletion to third-party services, verification steps to prevent accidental deletion, and audit logging of all deletions. The implementation must support gradual data removal to avoid performance impact on the production system.
- Permanent and irreversible account deletion with full data cleanup
- Compliance with GDPR and data protection requirements
- Deletion verification workflow to prevent accidents
- Audit trail for compliance and security
List any missing required sections or major problems that must be fixed.
List improvements that would enhance the spec quality.
Note what the spec does well.
After generating SPEC-STATUS.md and your validation feedback, sync the status to the GitHub issue:
tasks/{issue-number}-{task-name}/)github-task-sync/push-file.sh script to update the SPEC comment with status summary
~/.claude/plugins/marketplaces/edspencer-agents/plugins/product-team/skills/github-task-sync/push-file.sh <issue-number> SPEC SPEC-STATUS.md SPEC.md
This keeps the GitHub issue updated with the current spec validation status. The SPEC-STATUS.md file provides the 2-paragraph summary that appears at the top of the collapsible SPEC comment on GitHub.
If there are critical issues, recommend revisions before proceeding to plan creation. If the spec passes validation, confirm it's ready for the plan-writer agent.