sparq:sync

Sync test suites with changed requirements via diff analysis and approval workflows.

27|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq:sync
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-sync
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps test suites in sync with changing requirements by detecting diffs, proposing updates, and guiding automated or manual test adjustments.

Core Features & Use Cases

  • Diff analysis: compare current tests against updated requirements to classify NEW, CHANGED, REMOVED, and UNCHANGED.
  • Update generation: create and apply test changes, generate proposals for E2E specs, page objects, and test data with review checkpoints.
  • Telemetry & registry updates: record lastRefreshedAt, requirementsHash, and linked test IDs for traceability.

Quick Start

Install and run the sparq-sync skill to begin aligning tests with updated requirements.

Frequently Asked Questions about sparq:sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync test suites with updated requirements?

To sync test suites with updated requirements, perform a diff against a primary requirements source and the test registry to classify NEW, CHANGED, REMOVED, and UNCHANGED items, then orchestrate test updates with review checkpoints.

How does diff analysis classify changed requirements for test updates?

Diff analysis classifies changed requirements by comparing updated requirements against the test registry. It identifies NEW, CHANGED, REMOVED, and UNCHANGED requirements to generate targeted update proposals for E2E specs and page objects.

Can I automate E2E spec and page object updates from requirement changes?

Yes, you can automate E2E spec and page object updates from requirement changes. The Skill orchestrates both automation-based and manual test updates while enforcing approval workflows before applying changes.

How is traceability preserved across releases when syncing tests?

Traceability is preserved by recording metadata in the test registry. It tracks lastRefreshedAt, requirementsHash, and linked test IDs to maintain a clear audit trail across test updates and releases.

What's the best way to handle removed requirements in an automated test suite?

Handling removed requirements involves diff analysis to classify them. Update proposals are generated to guide manual or automated test adjustments, and changes are only applied after passing enforced approval workflows and review checkpoints.