Generate ADDED/MODIFIED/REMOVED behavioral specs from proposals and SRS.
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill specs-minhquan2904
Please help me install this Agent Skill. Skill: specs Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/specs Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill specs-minhquan2904
Generate delta behavioral specifications for changes to requirements by converting proposals and SRS into ADDED/MODIFIED/REMOVED scenarios.
Create a change named example-change and run the specs generator to produce the delta specs in openspec/changes/example-change/spec.md
High-intent search queries and answers about installing and using this skill.
To generate delta behavioral specs from a proposal and SRS, the tool converts requirement changes into ADDED, MODIFIED, and REMOVED scenarios. It validates coverage to ensure every requirement has at least one scenario and maps outputs to the source artifacts.
A delta spec in software change management defines the exact behavioral differences introduced by a new proposal. It categorizes updates into ADDED, MODIFIED, and REMOVED scenarios based on the existing software requirements specification.
Validating scenario coverage for software requirements involves enforcing a check that ensures every requirement listed in the SRS has at least one corresponding scenario generated. This prevents gaps in the delta specification during change management.
Yes, you can map generated specification scenarios back to the original proposal and SRS. The generation process explicitly maps the output delta specs directly to their source artifacts to maintain traceability throughout the change management workflow.
To start generating change specifications for a new software feature, create a named change directory and run the spec generator. This produces the delta specs in a structured markdown file within your project's changes folder.
Yes, you need an existing SRS and a proposal to document software requirement changes effectively. The tool relies on loading these source artifacts to accurately generate the ADDED, MODIFIED, and REMOVED delta scenarios for change management.
devmuslimExtract business rules and requirements from BRD, SRS, and User Stories.
Charles5277Merge delta spec changes into main specs and output an update log.
Zouu-XMerge delta specification changes into main specification documents.
echowavesMerge delta requirement blocks into main specification files.
