From majestic-engineer
Generates implementation plans using minimal, standard, or comprehensive templates matched to task complexity. Use for planning bugs, features, changes, or architectural work.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineerThis skill is limited to using the following tools:
Write implementation plans using the appropriate template based on complexity.
Creates detailed technical implementation plans via interactive research, iteration, user questions, and autonomy modes (Autopilot, Critical, Verbose). Activated by /create-plan or planning requests.
Generates detailed phased implementation plans with sprints and atomic tasks for bugs, features, or tasks. Activates when user says 'plan harder'. Saves as Markdown plan file.
Creates structured plans for multi-step tasks including software features, implementations, research, or projects. Deepens plans via interactive sub-agent reviews.
Share bugs, ideas, or general feedback.
Write implementation plans using the appropriate template based on complexity.
| Complexity | When to Use | Template |
|---|---|---|
| Minimal | Simple bugs, small improvements, clear single-file changes | references/minimal.md |
| Standard | Most features, complex bugs, team collaboration | references/standard.md |
| Comprehensive | Major features, architectural changes, multi-phase work | references/comprehensive.md |
Write plans to: docs/plans/[YYYYMMDDHHMMSS]_<title>.md
Include in every plan:
src/models/user.rb:42)Include "Design System Reference" section when feature involves:
Include "Infrastructure Context" section when feature involves:
| Don't | Do |
|---|---|
| Use comprehensive for simple bugs | Match template to actual complexity |
| Skip Acceptance Criteria | Always include testable criteria |
| Leave placeholder text | Fill all sections or remove them |
| Over-plan obvious changes | Minimal template exists for a reason |