feature-delivery

To automate feature delivery validation, you can trigger this skill to verify code completeness, tests, changelogs, and API documentation. It enforces a rigorous handoff by checking a deliverable checklist, static analysis results, and performance considerations.

A release checklist for production-ready features should include passing tests, updated README and CHANGELOG files, API documentation, static analysis results, and known limitations. This skill automates verifying these artifacts to reduce release risk and rework.

You generate release notes and handoff documentation by running this skill after a feature is complete. It prepares release artifacts, usage examples, and handoff notes to ensure smooth onboarding for product and software teams.

Yes, you can use this feature delivery skill for quality assurance. It applies quality gates by verifying static analysis results, security reviews, and performance considerations before allowing a feature to be released.

You need to run a final delivery checklist when a feature is complete and ready for release. This ensures all necessary artifacts, tests, and documentation are verified, reducing the risk of post-release rework.

Feature delivery validation works without external dependencies. This skill operates standalone to verify artifacts, tests, and documentation, applying its own rigorous checks for code completeness and handoff readiness.