Convert feature stories into black-box EARS specifications with unique IDs.
npx skills add https://github.com/provenimpact/proven-needs --skill needs-spec
Please help me install this Agent Skill. Skill: needs-spec Source: https://github.com/provenimpact/proven-needs/tree/main/skills/needs-spec Command: npx skills add https://github.com/provenimpact/proven-needs --skill needs-spec
Create and maintain feature specifications with EARS requirements derived from user stories. Use when the proven-needs orchestrator determines that a feature needs specifications created or synced. Operates within a single feature package at docs/features/<slug>/; Specs define WHAT must be true — black-box testable requirements for externally observable behavior.
Run this skill to generate or synchronize a feature specification from the current feature stories.
High-intent search queries and answers about installing and using this skill.
To convert user stories into formal specifications, this Skill reads feature stories and derives black-box EARS requirements, assigning unique IDs and outputting a formatted spec.adoc file with proper traceability.
EARS is a syntax for writing unambiguous, testable software requirements. This Skill enforces EARS formatting to translate feature stories into precise, black-box specifications for externally observable behavior.
You maintain versioning and traceability by syncing existing specifications with updated user stories. The Skill evaluates story versions, checks for constraints overlap, and generates a change-report workflow with proper meta headers.
Yes, you can generate specifications automatically from existing documentation. The Skill reads user-stories.adoc, derives the requirements, and creates or updates the spec.adoc file within the specific feature package directory.
Yes, this specification tool handles constraints overlap by evaluating existing specs and identifying constraints during the generation process. It actively checks for duplication to maintain precise, non-redundant requirements.
You need to create a new spec when a feature package lacks one, or sync an existing spec when user stories are updated. The Skill decides the correct action based on evaluating story versions and content.
provenimpactConvert feature intent into testable user stories with EARS-style acceptance criteria.
blesstosamFormalize Layer-3 EARS requirements with WHEN-THE-SHALL-WITHIN syntax and traceability.
provenimpactGenerates executable tests from spec.adoc verification descriptions within a feature package.
etrSynchronize product specifications with session decisions while preserving EARS formatting and versioning.
