Create delta specs with ADDED, MODIFIED, REMOVED, and RENAMED sections.
npx skills add https://github.com/Serien3/SuperSpec --skill writing-specs-serien3
Please help me install this Agent Skill. Skill: writing-specs Source: https://github.com/Serien3/SuperSpec/tree/main/src/superspec/skills/writing-specs Command: npx skills add https://github.com/Serien3/SuperSpec --skill writing-specs-serien3
Delta specs describe what's changing relative to the current specs, enabling focused, incremental software decisions without restating the entire system behavior.
Fill in the template for a given capability and save the resulting spec to the designated path.
High-intent search queries and answers about installing and using this skill.
A delta spec describes what a system should do relative to current specs, enabling focused incremental decisions without restating entire system behavior. You need delta specs when proposing capability changes that require structured, machine-parsable artifacts for automated reviews.
To write a delta spec with testable scenarios, apply the provided template to each capability listed in your proposal. Enforce a structured format with ADDED, MODIFIED, REMOVED, and RENAMED sections, ensuring every requirement includes specific testable scenarios for validation.
To keep requirements scope clear and traceable, generate one delta spec per capability listed in the proposal. Save the resulting versioned artifacts to standardized designated paths, ensuring each spec maintains a consistent, machine-parsable format for traceability and automated reviews.
Writing delta specs does not require restating entire system behavior. Delta specs specifically describe only what is changing relative to current specs, using ADDED, MODIFIED, REMOVED, and RENAMED sections to enable focused, incremental software decisions without duplicating existing documentation.
You must follow the provided template to ensure consistent, machine-parsable spec artifacts. The template enforces a structured format with ADDED, MODIFIED, REMOVED, and RENAMED sections, and requires testable scenarios for each requirement to maintain spec quality and automated review compatibility.
The best way to define removed and renamed capabilities is using a delta spec template with dedicated REMOVED and RENAMED sections. This structured approach describes changes relative to current specs, keeping scope clear and generating versioned artifacts for traceability and automated reviews.
crozzbiteMerge delta specs into main specs using the openspec CLI.
sachinnair90Verify implementation against change artifacts and generate a prioritized gap report.
alexei-lexxMerge delta specifications into canonical main spec files.
adacosdevGenerate delta specifications for added, modified, or removed system behavior.
