Organize feature design documentation into structured design.adoc files.
npx skills add https://github.com/provenimpact/proven-needs --skill needs-design
Please help me install this Agent Skill. Skill: needs-design Source: https://github.com/provenimpact/proven-needs/tree/main/skills/needs-design Command: npx skills add https://github.com/provenimpact/proven-needs --skill needs-design
This skill helps product teams and engineers create a coherent, living design document that maps user stories and specs to a concrete implementation plan, ensuring ADRs and constraints are considered and traceable throughout a feature's lifecycle.
Create a new design for a feature by running the Proven Needs orchestration and populate docs/features/<slug>/design.adoc with system, data, interfaces, and story resolution.
High-intent search queries and answers about installing and using this skill.
A living feature design document maps user stories and specs to a concrete implementation plan, ensuring ADRs and constraints are traceable throughout a feature's lifecycle. You need one when starting a new feature to capture decisions and structure the implementation plan.
To create a design.adoc, run the Proven Needs orchestration to populate docs/features/<slug>/design.adoc with system architecture, data models, interfaces, and story resolution. This organizes end-to-end feature design documentation across research and design phases.
Use sync and maintenance workflows to keep system design documentation aligned with evolving stories, specs, and ADR updates. This ensures your design.adoc remains a living document that preserves traceability from requirements to implementation as the feature changes.
Apply Phase 0 research guidance to identify technology choices, unknowns, dependencies, and ADR integration, then use Phase 1 design guidance for system architecture and story mapping. This maps architecture decisions directly to a structured implementation plan in design.adoc.
The feature design process references ADRs to ensure constraints and technology choices are considered traceable. While it guides identifying unknowns and dependencies during research, having established ADRs provides the foundational decisions needed for a coherent implementation plan.
Clos01Create structured product requirement documents with goals, metrics, and delivery plans.
dmayerdesignPlan implementation from a behavioral spec into a testable design plan.
flight505Evaluate technology options and document decisions with Architecture Decision Records.
WellApp-aiGenerate numbered Gherkin scenarios and acceptance criteria for QA contracts.
