skills.rest
sgttomas
sgttomasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

decomposition-package-review

Validate DOMAIN decomposition packages for parity, snapshot completeness, and handoff-state readiness.

Updated Aug 23, 2026
Search Tags:#automation#decomposition#review#handoff#parity#scope-change
One-click install
npx skills add https://github.com/sgttomas/chirality-piping --skill decomposition-package-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decomposition-package-review
Source: https://github.com/sgttomas/chirality-piping/tree/main/skills/decomposition-package-review
Command: npx skills add https://github.com/sgttomas/chirality-piping --skill decomposition-package-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates a DOMAIN decomposition package as a closed system, ensuring parity between surfaces, completeness of the active snapshot, and handoff-state readiness for downstream work.

Core Features & Use Cases

  • Parity verification: compares decomposition-local truths, authoritative registers, and snapshot artifacts to identify drift or gaps.
  • Snapshot and handoff validation: ensures the active scope-change snapshot aligns with contract terms and actual package state.
  • Bounded repair and reporting: in repair mode, applies only explicitly authorized, mechanically derived changes and produces a formal review artifact for gating decisions.

Quick Start

Provide ScopePath and an explicit AllowedWriteTargets list, then run the review to generate a READY, READY_WITH_GAPS, or BLOCKED verdict and a formal report.

Frequently Asked Questions about decomposition-package-review

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

FAQPage Schema
How do I verify parity before a decomposition package handoff?▼

To verify parity before a decomposition package handoff, validate the active snapshot and handoff-state against authoritative registers to ensure consistency and produce a formal review artifact.

What is the best way to review scope changes for DOMAIN root remediation?▼

Reviewing scope changes for DOMAIN root remediation requires validating the decomposition package as a closed system to ensure snapshot completeness and handoff-state readiness for downstream work.

How do I run a bounded repair on a DOMAIN decomposition package?▼

To run a bounded repair on a DOMAIN decomposition package, provide an explicit AllowedWriteTargets list to apply mechanically derived changes and generate a formal report for gating decisions.

Can I automate snapshot completeness checks for decomposition packages?▼

Yes, you can automate snapshot completeness checks by validating that the active scope-change snapshot aligns with contract terms and actual package state during the review process.

What does a BLOCKED verdict mean during decomposition package validation?▼

A BLOCKED verdict during decomposition package validation indicates critical inconsistencies exist between duplicated package truth, active snapshots, and authoritative surfaces, preventing downstream handoff.

Do I need to specify AllowedWriteTargets to validate decomposition package parity?▼

Yes, providing an explicit AllowedWriteTargets list is required to run the validation safely, ensuring any bounded repairs are explicitly authorized and mechanically derived.

Related Skills

Explore More Software Engineering Skills→
wesleyegbertowesleyegberto
3

microservices-architect

Define service boundaries for distributed systems using domain-driven design.

Community
Advanced
mitchellfyimitchellfyi
3

dxreview

Automate full-scope code review waves for Dex ticket-to-PR changes.

Community
Advanced
yusifengyusifeng
192

formax-semantics-parity-workflow

Enforce canonical cross-surface semantics across TUI, app-server, and Web surfaces.

Community
Advanced
FRIKKernFRIKKern
6

doey-repair

Diagnose and repair Doey Dashboard window 0 panes with non-destructive commands.

Community
Intermediate