majestic-engineer

Get a config value from .agents.yml (with local overrides)

Explain a concept using real examples from YOUR project, not abstract theory

Generate complete favicon set from source image and update project HTML

Create engaging changelogs from recent merges to default branch

Generate documentary-style narrative of repository development history

Create a git commit with conventional commit format

Create a pull request for the current feature branch

Start a Linked Decision Record — creates numbered branch, prompt, and blueprint files

Review and address Pull Request comments from GitHub

Triage all open PRs with parallel review agents, label, group, and walk through one-by-one for merge/comment/close decisions

Clean up merged and stale git worktrees

Parse blueprint markdown into epic.yml for fresh-context execution

Show playlist progress across all epics

Output terminal command to execute playlist

Show current epic progress and task status

Execute epic tasks with fresh-context Claude instances and quality gate verification

Create a detailed handoff plan for continuing work in a new session

Clear the session ledger file to start fresh

Resume work from a previous handoff session stored in .agents/handoffs

Analyze conversation and generate optimized /compact command

Manage backlog items across files, GitHub Issues, Linear, or Beads

Transform feature descriptions into well-structured project plans

Autonomous task implementation - research, plan, build, review, fix, ship

Generic code review that auto-detects tech stack and delegates to appropriate framework-specific orchestrator

Debug errors, test failures, or unexpected behavior. Auto-detects project type.

Initialize AGENTS.md with hierarchical structure and .agents.yml config

Create a Product Requirements Document (PRD) for a new product or feature

Run quality gate checks on code changes with tech stack-aware reviewers

Answer questions about the project structure, documentation, or external topics without coding

Refactor existing AGENTS.md to follow progressive disclosure principles

Execute all tasks in a blueprint using build-task workflow

Complete checkout workflow - runs linting, creates commit, and opens PR

Create junior-dev-ready design systems through guided discovery before implementation

Use proactively for UI/UX design work. Specialist for iterative refinement through screenshots, visual analysis, and progressive improvements.

Resolve CI failures and PR review comments from GitHub. Routes to specialized resolvers.

Design non-trivial features with architectural planning. Transforms requirements into implementation approaches and system designs.

Analyze code structure and create refactoring plans with risk assessment. Identifies improvement opportunities and produces step-by-step implementation plans.

Break implementation plans into small, actionable tasks (1-3 story points) with dependencies and parallelization matrix

Review code for security vulnerabilities, hardcoded secrets, OWASP Top 10 issues, and insecure practices.

Remove AI-generated code slop: over-commenting, defensive checks, type escapes, style inconsistencies.

Split blueprint into multiple epics by logical phase (foundation, core, integration, polish)

Generate playlist.yml from epics folder (non-interactive)

Aggregate learnings from relay epic, apply frequency thresholds, write to .agents/lessons/ or AGENTS.md

Use proactively after implementing features or fixes to verify they actually work. Enforces systematic verification before declaring completion.

Orchestrates build execution workflow - build, verify, quality, fix loop, and ship.

Wrap agent invocations with output budget enforcement. Executes inner agent, compacts results exceeding specified character limit.

Discover and rank relevant lessons with semantic scoring. Returns links (not content) to minimize token overhead.

Orchestrate parallel code review based on tech stack configuration. Aggregates findings from multiple specialized reviewers and returns unified quality verdict.

Reference for Step 10 of build-task-workflow-manager. Defines what to capture and how to format it for AGENTS.md.

Complete checkout workflow - runs linting, creates commit, opens PR, creates handoff. Ships code on "ready to ship" or "finish up".

Fetch task details from configured task management system. Supports GitHub Issues, Beads, Linear, and file-based backends. Returns normalized task data.

Update task status in configured task management system. Handles claim (in_progress) and ship (ready-for-review with CI check) actions across GitHub, Beads, Linear, and file backends.

Discover and resolve tech-stack toolbox manifests from installed plugins. Returns merged configuration for build-task and quality-gate orchestrators.

Create development workspace (branch or worktree) based on project configuration. Handles branch naming patterns and git workflow preferences.

Manage backlog items across multiple backends (GitHub Issues, Linear, Beads). Configure task_management in .agents.yml.

Discovery phase for blueprint workflow - interview triggers, acceptance criteria, and feature classification

Execution phase for blueprint workflow - present options and delegate to appropriate commands

Research phase for blueprint workflow - toolbox resolution, lessons discovery, and parallel research agents

This skill monitors PR CI checks by polling GitHub status until completion or timeout. Use when the user requests to check CI status, wait for CI to pass, monitor PR checks, or verify build status. Applicable for queries like "check my CI", "wait for CI to pass", "is my PR green", or "monitor CI checks".

Build edge-first TypeScript applications on Cloudflare Workers. Covers Workers API, Hono framework, KV/D1/R2 storage, Durable Objects, Queues, and testing patterns. Use when creating serverless workers, edge functions, or Cloudflare-deployed services.

Narrative templates for git history documentation. Used by /git:code-story command.

Read project config from .agents.yml and .agents.local.yml with local overrides. Supports dot notation for nested fields. Invoke with args "<field> <default>".

Create Architecture Decision Records (ADRs) to document significant technical decisions, their context, alternatives considered, and consequences. Use when making architectural choices, selecting libraries/frameworks, or designing system components.

Help choose the right design tool based on your current task. Use when unsure whether to use frontend-design, ui-ux-designer, visual-validator, or ui-code-auditor.

Fetch and summarize API documentation from official sources before implementation. Covers Rails, Tailwind, external libraries, and gem source exploration. Triggers on fetch docs, API reference, library documentation, check docs, read documentation.

Post-documentation decision menu for fix-reporter. Routes to critical patterns, skill updates, cross-references, or discovery enablement.

Capture solved problems as categorized documentation with YAML frontmatter for fast lookup

Framework-agnostic CSS patterns for typography, color, motion, and spatial composition.

Design thinking principles for distinctive interfaces. Covers aesthetic direction, anti-patterns, and avoiding generic AI-generated aesthetics.

Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, or applications. Includes framework-specific guidance for Tailwind, React, Vue, and Rails/Hotwire ecosystems.

Analyze git history to trace code evolution, identify contributors, and understand commit patterns. Use for archaeological analysis of repositories. Triggers on git history, blame analysis, code evolution, contributor mapping, commit patterns.

Manage git worktrees for parallel development. Use when the user wants to work on multiple branches simultaneously, create isolated environments for features/fixes, or clean up completed worktrees.

Repository structure methodology for maximum AI agent effectiveness. Three pillars — context engineering (repo as knowledge product), architectural constraints (deterministic enforcement), garbage collection (active entropy fighting). Use when setting up repos for AI development, diagnosing repeated agent failures, writing AGENTS.md, or designing CI gates and structural tests.

Generate hierarchical AGENTS.md structure for codebases to optimize AI agent token usage. Use when creating AGENTS.md files, documenting codebase structure, setting up agent guidance, organizing project documentation for AI tools, implementing JIT indexing, or working with monorepos that need lightweight root guidance with detailed sub-folder documentation. Covers repository analysis, root AGENTS.md generation, sub-folder AGENTS.md creation, and token-efficient documentation patterns.

Generate .agents.yml config from user answers. Provides tech stack templates for Rails, Python, Node, and Generic projects.

Expert guidance for creating syntactically correct Mermaid diagrams. Use when creating flowcharts, sequence diagrams, class diagrams, state diagrams, Gantt charts, ER diagrams, or data lineage visualizations.

Write implementation plans with appropriate templates based on complexity. Use when planning features or changes. Provides minimal, standard, and full templates for different scope levels.

Use when reviewing a plan before implementation begins. Not for autonomous plan analysis — use plan-review agent instead. Challenges scope, walks through architecture/quality/tests/performance interactively with mandatory user checkpoints and opinionated recommendations.

Review development plans for issues, missing considerations, architectural violations, and alternatives. Includes SOLID compliance, circular dependency detection, and coupling analysis.

Address PR review comments by implementing reviewer feedback and suggestions.

Capture and document UI changes with before/after screenshots for pull requests. Use when creating PRs that include visual changes to ensure reviewers can assess design modifications.

Production-grade README.md patterns for any project type. Use when creating project documentation, writing README files, or improving existing docs. Covers hero sections, quick start examples, comparison tables, troubleshooting guides, and limitation transparency. Triggers on README, documentation, project setup, open source.

Automatically check and update folder-specific AGENTS.md during research. Before investigating a domain, read nearest AGENTS.md for existing context. After discovering valuable patterns, append learnings to that file.

Code review using RepoPrompt MCP (chat_send mode=review). Returns structured verdict for relay workflow.

Save session state to ledger file for continuity across crashes, context switches, or /clear + reload cycles.

Analyze specifications, plans, or feature descriptions for user flows, gaps, and missing requirements. Use before implementation begins.

Production logging patterns for observability and incident debugging. Structured JSON logging, correlation IDs, context propagation, log levels, and performance. Use when implementing logging, adding observability, or debugging production systems. Triggers on logging setup, logger configuration, observability, distributed tracing, or incident response workflows.

Use when orchestrating multi-step workflows with Claude Code's native Task system (TaskCreate, TaskUpdate, TaskGet, TaskList) - lifecycle management, parallel execution, crash recovery, and progress visibility. Not for simple single-step tasks.

Test-driven development execution workflow with red-green-refactor cycle, increment decomposition, and pause/continue rules. Use when building features or fixing bugs using TDD. Framework-agnostic with language-specific configs for Python, TypeScript, Go, and Ruby delegation.

Write technical tutorials, blog posts, and educational content with pedagogical structure. Covers concept explanations, how-to guides, deep dives, and developer education. Triggers on tutorial, technical article, blog post, explain concept, teach, educational content, developer guide.

Review test quality, coverage, and completeness. Analyzes for missing edge cases, assertion quality, and coverage gaps.

Run test suite and return structured pass/fail results. Supports scoped runs by directory, file, or test name pattern. Triggers on run tests, execute tests, test results, check tests, verify tests pass.

Review source code for UI quality, accessibility violations, and performance anti-patterns. Static code analysis (NOT screenshot-based). Provides file:line references with severity, WCAG refs, and fix suggestions.

Design system templates and patterns for UI/UX briefs. Used by /majestic:ux-brief command.

Use proactively after UI changes to verify they achieved their intended goals. Skeptical visual QA through screenshot analysis, accessibility verification, and design system compliance checking.

Research technical problems across GitHub issues, Stack Overflow, Reddit, and documentation. Gathers solutions from multiple community sources with structured findings. Triggers on search for solutions, find examples, research problem, community solutions, debug research.

Knowledge about attempt tracking and gating patterns for task execution