Generates executable tests from spec.adoc verification descriptions within a feature package.
npx skills add https://github.com/provenimpact/proven-needs --skill needs-tests
Please help me install this Agent Skill. Skill: needs-tests Source: https://github.com/provenimpact/proven-needs/tree/main/skills/needs-tests Command: npx skills add https://github.com/provenimpact/proven-needs --skill needs-tests
Derive and generate executable tests from feature specifications to guarantee test coverage before implementation.
Run the test-generation workflow for the current feature package using the orchestrator.
High-intent search queries and answers about installing and using this skill.
To generate tests from feature specifications, this Skill translates verification descriptions in spec.adoc files into concrete test cases using the project's existing test framework. It scopes generation to a single feature package at docs/features/<slug>/ to ensure 100% spec coverage before implementation begins.
Ensuring 100% test coverage before implementation involves deriving executable test cases from feature spec descriptions. This approach translates spec.adoc verification criteria into tests, proactively reporting any coverage gaps to the orchestrator for remediation so gaps are caught early.
Yes, you can use your existing test framework. The generation process detects and adapts to the project's current testing setup, translating the spec.adoc verification descriptions into concrete test cases that fit natively within your established quality-assurance environment.
To report and fix spec coverage gaps, the test generation process analyzes the spec.adoc files and identifies missing verification descriptions. It then reports these gaps back to the proven-needs orchestrator for remediation, guiding incremental test generation as the feature specifications evolve.
Yes, this approach works by operating exclusively within a single feature package located at docs/features/<slug>/. This scoping ensures that test generation is strictly isolated to the relevant feature, translating only that specific spec.adoc into executable tests without affecting unrelated project areas.
You should not use automated test generation from feature specs if your project lacks structured spec.adoc files or a defined feature package directory. The process relies entirely on translating existing verification descriptions within docs/features/<slug>/ into concrete tests.
provenimpactConvert feature stories into black-box EARS specifications with unique IDs.
shawn-sandyReview existing tests for quality, coverage gaps, and alignment with code behavior.
shaman007Compare codebase against spec.md, plan.md, and tasks.md to identify implementation gaps.
joelabrahamssonGuide users through creating BDD specifications and generating executable test files.
