Validate implemented features against specification and Definition of Done.
npx skills add https://github.com/rudometkin/GenAI-intensive --skill test-rudometkin
Please help me install this Agent Skill. Skill: test Source: https://github.com/rudometkin/GenAI-intensive/tree/main/projects/DemyanovaDarya/bonus/test Command: npx skills add https://github.com/rudometkin/GenAI-intensive --skill test-rudometkin
Streamlines validation by comparing implemented features against the product spec and DoD, catching gaps before release.
Run the DoD-driven checks against the implemented feature to confirm it meets the specified criteria.
High-intent search queries and answers about installing and using this skill.
To verify implemented features against a product specification, you can run DoD-driven validation that reads requirements from spec.md and executes static analysis, linting, unit tests, and integration tests. This automatically identifies gaps between the implementation and the expected behavior.
DoD-driven verification is a validation mechanism that reads the Definition of Done from spec.md to confirm feature completeness. It automatically runs static analysis, linting, unit tests, and integration tests to ensure the implementation matches the expected behavior specified in the document.
You can run API checks and UI scenario validation by executing standard tooling against the implemented feature. This validates manual API scenarios and UI behavior to confirm the implementation satisfies the expected criteria outlined in the specification.
Yes, the verification process explicitly supports TypeScript type checking and linting. It applies standard tooling to perform static analysis on your codebase, ensuring the implemented features meet the required type safety and code quality standards before release.
The best way to catch regressions early is to run DoD-driven checks that compare your implementation directly against the product spec. By executing static analysis, unit tests, integration tests, and API checks together, you identify behavioral gaps and regressions before release.
You need to validate features against the Definition of Done after implementing a feature and before release. This ensures the code aligns with the expected behavior specified in spec.md by running comprehensive checks like static analysis, tests, and API validations.
shouqitaoGenerate structured Markdown requirements documents from natural language input.
SjdjdiejdrirhdkjejPromote validated staging builds to production with semantic versioning and health checks.
kevinnftAutomate CI/CD quality gates for lint, type checks, tests, and security audits.
rhussGenerate implementation plans and TDD cycles from validated specifications.
