Convert feature intent into testable user stories with EARS-style acceptance criteria.
npx skills add https://github.com/provenimpact/proven-needs --skill needs-stories
Please help me install this Agent Skill. Skill: needs-stories Source: https://github.com/provenimpact/proven-needs/tree/main/skills/needs-stories Command: npx skills add https://github.com/provenimpact/proven-needs --skill needs-stories
Stories are often missing or misaligned with user needs, causing scope creep and poor validation. This skill helps teams create and update user stories with precise acceptance criteria from a user's perspective, ensuring alignment with feature intent.
Describe the feature briefly and generate a first set of US-001 style stories.
High-intent search queries and answers about installing and using this skill.
User stories are generated by converting feature intent into US-001 style stories with EARS-style acceptance criteria, ensuring alignment with user needs and feature scope to prevent scope creep and poor validation.
EARS-style acceptance criteria are structured conditions used to validate user stories from a user's perspective, ensuring that stories are testable, precise, and aligned with the intended feature state and constraints.
Existing user stories are updated by reading docs/features/<slug>/user-stories.adoc to refine the story set, enforcing constraint checks and versioning throughout the Execute phase to reflect changes in scope or constraints.
Feature packages at docs/features/<slug>/ support user story versioning and constraint checks, as the skill operates within this context to align stories with the current feature state throughout execution.
Misaligned user stories cause scope creep because they lack precise acceptance criteria, leading to poor validation and uncontrolled feature expansion during development.
Validating user stories against current feature state is best done by enforcing constraint checks and versioning within a single feature package, ensuring stories remain aligned with feature intent throughout the Execute phase.
provenimpactConvert feature stories into black-box EARS specifications with unique IDs.
lamb92009Coordinate structured feature discovery and EARS-based specification drafting.
amitmishra-bylddExecute story implementation from context-filled spec files with status transitions.
ProjAnvilPlan product development from ideation to release with PRDs and roadmaps.
