// Analyzes an existing Galactic feature or workflow to find the highest-value product gaps. Use when you need a structured gap analysis grounded in real users, current implementation, and clear in-scope versus out-of-scope pain.
Applies Galactic engineering rules for work in the galactic-ide repository. Use when implementing, reviewing, or refactoring repo code and you need the canonical standards for testing, versioning, React/Tailwind conventions, toasts, storage, OS-aware logic, and git-service boundaries.
Applies the client-side subset of Galactic engineering rules. Use when writing, reviewing, or modifying React/TypeScript renderer code and you want the UI conventions without loading the broader repo framing.
Packages an approved Galactic UX/UI design into a design-ready handoff for future engineering skills. Use when solution framing, design, and validation are complete and you need one final artifact with behavior, states, acceptance criteria, instrumentation, and open risks.
Critiques a Galactic UX/UI spec before engineering handoff. Use when you need a structured validation pass focused on clarity, trust, compatibility risk, edge cases, and whether the design actually serves Galactic's target users.
Turns a Galactic gap analysis into a scoped product brief. Use when you need a decision-oriented solution framing artifact with scope, constraints, success metrics, and design questions before UX/UI work starts.
Creates a Galactic-specific user insight brief for a feature, workflow, or product area. Use when you need to identify the target user, JTBD, current workaround, trust requirements, and adoption blockers before gap analysis or design.
| name | galactic-feature-gap-analysis |
| description | Analyzes an existing Galactic feature or workflow to find the highest-value product gaps. Use when you need a structured gap analysis grounded in real users, current implementation, and clear in-scope versus out-of-scope pain. |
| allowed-tools | Read, Grep, Glob |
Use this skill to diagnose where an existing Galactic experience falls short for real users.
Read these first:
../references/galactic-product-foundation.mdREADME.mdUser Insight Brief when availableUXgaps.md, screenshots, or notesInspect the current experience in code and tests before naming a gap. For product surfaces, search the relevant paths in src/, electron/, and tests/.
../references/galactic-product-foundation.md.Return exactly this Markdown structure:
# Gap Analysis
## Scope
- Feature or workflow:
- Current surface inspected:
- Primary archetype:
- Dominant pain:
## Current Experience
- What the user sees today:
- What the product is trying to achieve:
- Where the experience currently works:
## Observed Gaps
| Gap | Why It Matters | Severity | Frequency | Confidence |
| --- | --- | --- | --- | --- |
| | | High / Medium / Low | High / Medium / Low | High / Medium / Low |
## Who Feels This Most
- Primary affected user:
- Secondary affected user:
## Non-Gaps
- What should not be changed:
## Adjacent But Out Of Scope
- Adjacent pain:
- Why it is not the primary gap:
## Recommended Primary Gap
- Primary gap to solve next:
- Why this is the right wedge for Galactic:
- Next skill:
Hand off to $galactic-solution-framing.