What problem does it solve? Multisig proposal changes in the Guardian repository span two SDK stacks (Rust and TypeScript) plus multiple example harnesses, so editing one stage in isolation risks breaking lifecycle invariants like threshold counting, offline signing, and export/import stability. ## Core Features & Use Cases - Cross-stack lifecycle guidance: Classifies work by proposal stage (creation, parsing, signing, readiness, execution, export/import, sync) and points to the exact Rust and TypeScript files for each stage. - Invariant guardrails: Enforces rules such as stable proposal identifiers across export/import, explicit online-to-offline fallback, fail-fast handling of malformed signatures, and special treatment of SwitchGuardian flows. - Validation workflow: Provides targeted test commands (cargo test, npm test, smoke harnesses) and a workflow matrix reference for deciding what else must be checked when one stage changes. - Use Case: When adding a new signature scheme to the multisig SDK, use this Skill to update both the Rust and TypeScript signing paths, verify threshold logic, and run the demo and smoke-web example surfaces. ## Quick Start Use the guardian-multisig-proposal-lifecycle skill to update proposal signing logic in both the Rust and TypeScript multisig SDKs and validate the change with the demo and smoke-web examples.