signal-system-sweep

Detects drift and unifies decisions across four operating systems and their artefacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill signal-system-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-system-sweep
Source: https://github.com/Scripsteam/scrips-stack/tree/main/signal-system-sweep
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill signal-system-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-fires on any work touching the four Scrips operating systems — SIGNAL (Design), TOPIC (Product), KERNEL (Engineering), TEMPO (Operations) — plus Storybook, design tokens, ADRs (DS-NNN / BRD-NNN / ADR-NNN), or any constitutional doc per META-SPEC. Runs a system-wide consistency sweep — pulls latest across scrips-signal-ds, signal-portal, scrips-react, the vault (Obsidian), and ~/.claude config; detects drift between locked decisions, tokens, agent contracts, and consumer code; updates the canonical changelog; surfaces stale references for Samer / Andrew / Tariq / Mark Watson / future-agent. Use when the user mentions: signal-ds, signal portal, signal-portal, TOPIC, KERNEL, TEMPO, Storybook, design system, DS-NNN / BRD-NNN / ADR-NNN decision, token update, brand sweep, version-control sweep, meta-spec, sister-OS, "make sure everything is in sync".

Core Features & Use Cases

  • System-wide drift detection across SIGNAL, TOPIC, KERNEL, TEMPO and downstream artefacts (Storybook, tokens, ADRs, META-SPEC).
  • Cross-repo synchronization and canonical-reference updates (CHANGELOG, DESIGN-STATE pointers, tokens, design-map references).
  • Pre- and post-change validation to ensure alignment before deployment and after iteration.

Quick Start

Run this skill before making changes to ensure system-wide consistency.

Frequently Asked Questions about signal-system-sweep

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

FAQPage Schema
How do I detect design system drift across multiple repositories?

Design system drift is detected by running a system-wide consistency sweep that pulls latest changes from linked repos and compares locked decisions, tokens, and consumer code to surface actionable drift reports.

How do I keep design tokens and Storybook aligned with engineering code changes?

Token validation and Storybook alignment are maintained by automatically sweeping canonical documents and downstream artefacts whenever changes touch design tokens, ADRs, or consumer code to unify decisions across operating systems.

When do I need to run a consistency sweep for ADR and META-SPEC updates?

A consistency sweep is needed whenever changes touch constitutional docs per META-SPEC, ADRs (DS-NNN / BRD-NNN / ADR-NNN), or DESIGN-STATE.md to ensure system-wide alignment before deployment and after iteration.

Can I use this sweep to validate pre-deployment alignment across SIGNAL, TOPIC, KERNEL, and TEMPO?

Pre- and post-change validation ensures alignment across the four Scrips operating systems by detecting stale references, enforcing token validation, and surfacing drift reports before deployment and after iteration.

What's the best way to surface stale references in a multi-repo design system?

Stale references are surfaced by running an automated consistency sweep that pulls latest changes from linked repos, detects drift between locked decisions and consumer code, and generates actionable drift reports for teams and future-agents.