deliverable-review

You can validate deliverables against current framework documentation by using Context7 MCP to compare SKILL.md frontmatter and project docs against the latest framework standards, identifying outdated patterns and gaps in skills, stack templates, and documentation.

A deliverable review is needed during monthly quality review cycles, before pre-release validation, and when updating to major framework versions to ensure skills, stack templates, and documentation maintain alignment with current standards.

To check alignment, run the review workflow against directories like .github/skills/ and templates/stacks/ to read SKILL.md frontmatter and project docs, comparing them against Context7 MCP results to generate actionable findings and change recommendations.

Yes, you need Context7 MCP configured in your environment, such as Claude Desktop or Cursor, because the validation process relies on it to fetch and compare current framework documentation against your local project deliverables.

The best way to automate pre-release validation is running a workflow that reads local project docs and SKILL.md frontmatter, using Context7 MCP to cross-reference current framework standards and output actionable change recommendations for maintainers.

A deliverable review workflow fails to read stack templates if the required directories templates/stacks/ and .github/skills/ are not accessible, or if Context7 MCP is not properly configured in your Claude Desktop or Cursor environment.