spec-manager

Spec file management automation organizes specification files in a consistent structure across feat, fix, docs, refactor, and chore scopes. This Skill creates, updates, deletes, and lists specs under specs/{scope}/{work-name}.md, enforcing XML tag templates and preventing duplicates to standardize your spec-driven workflow.

Enforcing XML tag structure in specs involves applying scope-specific templates that validate tag format and organization. This Skill implements template-driven validation per scope, ensuring every spec conforms to the same XML structure and reducing manual review overhead.

Duplicate prevention and conflict resolution work by checking for existing spec files before creation and surfacing conflicts for user review. This Skill detects collisions, generates filenames automatically, and prompts you to resolve conflicts, keeping one spec per task except when frontend and backend collaborate.

Organizing specs across scopes means grouping specification files by work type—feat, fix, docs, refactor, chore—each under specs/{scope}/ directories with scope-specific templates. This Skill manages this structure automatically, applying the correct template rules for each scope and maintaining alignment with your workflow.

Spec file management supports create, update, delete, and list operations to give you full control over your specifications. Beyond initial creation, this Skill lets you modify existing specs, remove outdated ones, and enumerate all specs across scopes with a single workflow.

Manual validation is unnecessary because this Skill enforces validation steps automatically, checking XML structure, filename generation, and template compliance. Validation prevents misaligned specs and reduces errors before they affect your development workflow.