From majestic-engineer
Analyzes specifications, plans, or feature descriptions for user flows, gaps, and missing requirements before implementation begins.
How this skill is triggered — by the user, by Claude, or both
Slash command
/majestic-engineer:spec-reviewerThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Audience:** Teams with specifications, plans, or feature descriptions ready for pre-implementation review.
Audience: Teams with specifications, plans, or feature descriptions ready for pre-implementation review.
Goal: Identify user flows, gaps, and missing requirements before implementation begins.
For each feature, identify:
Consider variations:
Look for missing:
For each gap:
## User Flows
[Numbered list of distinct user journeys]
## Flow Variations
| Flow | Guest | User | Admin |
|------|-------|------|-------|
| [flow name] | [behavior] | [behavior] | [behavior] |
## Gaps Found
### Critical (blocks implementation)
- [gap]: [why it matters]
### Important (affects UX)
- [gap]: [why it matters]
## Questions
1. [Specific question]
- Why: [impact]
- Default assumption: [what you'd assume]
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineerIdentifies gaps in product specifications like spec.md and generates clarifying questions with concrete stakeholder options. Useful before implementation or for requirement validation.
Reviews PRDs and specs for completeness, ambiguities, edge cases, acceptance criteria quality. Structures findings by severity and offers direct fixes.
Writes a detailed specification for a single feature including user flows, edge cases, API definitions, and acceptance criteria. Useful when asked for a feature spec or functional requirements.