Convert vague requirements into delta specs and design artifacts under .superspec.
npx skills add https://github.com/Serien3/SuperSpec --skill definition-serien3
Please help me install this Agent Skill. Skill: definition Source: https://github.com/Serien3/SuperSpec/tree/main/src/superspec/skills/definition Command: npx skills add https://github.com/Serien3/SuperSpec --skill definition-serien3
Helps teams convert vague user needs into precise specifications and design artifacts before coding.
Review the current project state and begin drafting delta specs for the upcoming feature.
High-intent search queries and answers about installing and using this skill.
Delta specs define exactly WHAT a system should do by structuring changes into ADDED, MODIFIED, REMOVED, and RENAMED operations. They are needed for brownfield projects and ongoing feature work to maintain traceability from proposal to implementation.
To create delta specs for ongoing feature work, you assess the current project state and apply delta operations like ADDED, MODIFIED, REMOVED, and RENAMED. The resulting specs are then stored under the .superspec directory for team traceability.
Yes, using delta specs for brownfield project state assessment requires a valid SKILL.md frontmatter containing name and description. This frontmatter enforces the template-driven workflow needed to orchestrate spec creation effectively.
You should avoid using delta specs for project proposals when dealing with greenfield projects lacking an existing state to assess. Delta operations like MODIFIED and REMOVED are designed for brownfield feature work rather than entirely new system architectures.
l-linGenerate a Claude Code skill directory with SKILL.md and YAML frontmatter.
tonysyuValidate code changes against openspec delta specs and task lists.
cvillamarp-lgtmDefine design engineering roles and handoff workflows between design and engineering teams.
memorysaverMerge delta specs under openspec/changes into main specs.
