Problem
What problem this solves
Multi-platform products drift easily: a feature may exist on one OS, be partially native on another, and still be described as fully supported everywhere.
Menu Open navigation menu Close navigation menu
Audit & Improve
Skill Detail
sg-platform-parity
Keep product expectations and technical implementation aligned across every supported platform.
Audits platform parity, separates legitimate platform adaptations from implementation debt, and routes missing work to the right ShipGlows skill.
Outcome
What changes when it works
You get a platform parity matrix, clear adaptation decisions, proof gaps, and owner routes for implementation, QA, verification, or documentation correction.
Why It Matters
What this changes for a solo founder
This skill protects trust. It keeps users from being surprised by platform differences unless the adapted experience is better or genuinely required by the platform.
When to use it
- Before claiming support for a new platform
- When porting a feature from one OS to another
- Before a release where platform coverage matters
- When docs, store copy, or roadmap language may overpromise parity
What you give it
- A project, feature, workflow, or spec path
- Optional target platforms such as web, Android, iOS, Windows, macOS, or Linux
- Any explicit product decision about acceptable platform adaptation
What you get back
- A parity verdict by capability and platform
- A distinction between better adaptation, required adaptation, accepted degradation, and implementation debt
- Evidence pointers for code, docs, specs, tests, CI, or manual QA
- Routes to sg-spec, sg-build, sg-test, sg-verify, sg-docs, or sg-ship
Typical examples
- /sg-platform-parity overlay and hotkeys across desktop
- /sg-platform-parity WinFlowz platforms=android,ios,windows,macos,linux,web
- /sg-platform-parity check the platform claims before ship
Limits
- It does not implement platform ports directly
- It does not treat scaffolds, permission strings, shared code, or roadmap language as proof of support
- It does not accept a different experience unless it is better, required, or explicitly accepted as degraded
Arguments
Some arguments change the workflow, not just the wording.
These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.
<project | feature | spec path>
Audits parity for the requested scope.
Consequence
Produces a concise verdict by default and durable artifacts when the scope needs follow-up.
platforms=<list>
Constrains the comparison to the named platforms.
Consequence
Useful when the project supports more platforms than the current chantier targets.
report=agent / handoff / verbose / full-report
Includes detailed matrix evidence and routing notes.
Consequence
Useful when another skill or agent will execute the follow-up.
Related Skills
See the rest of the loop around this move.
Audit & Improve
sg-audit
Run a broad project audit when you need a high-level map of what is weak before you decide what to fix.
The top-level audit skill scans across multiple quality domains so you can see where the real risk or drift sits.
Open skill page Plan & Decide
sg-spec
Turn a fuzzy request into an implementation-ready contract before code starts mutating the repo.
The spec-writing skill for shaping non-trivial work into a clear user story, behavior contract, executable task list, and chantier history.
Open skill page Build & Fix
sg-build
Run non-trivial work from story to spec, build, verification, closeout, and ship without making the user drive every gate.
The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
Open skill page Build & Fix
sg-test
Guide the human through the real user flow, then turn the result into test evidence and actionable bugs.
A manual QA skill for creating guided test campaigns, capturing structured outcomes, and preserving bug history after implementation.
Open skill page Audit & Improve
sg-verify
Check whether the work really satisfies the user story, not just whether the code compiles.
A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.
Open skill page Operate & Ship
sg-docs
Create or repair documentation so the repo stays navigable for both humans and agents.
A documentation skill for maintaining docs, metadata, and governance-layout compliance across project surfaces.
Open skill page Operate & Ship
sg-ship
Commit and push quickly when the work is actually ready, instead of stretching closure into another vague step.
A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
Open skill pageGo Deeper
This public page explains the move. The repository explains the execution contract.
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.