mlst

Plugin mlst from marketplace patricks-plugins in lexicalninja/my-little-scrum-team. Commands read from the repo's manifest — 1 month ago.

Skills (40)

• accessibility-checker

  Checks code for accessibility issues including missing alt text, poor color contrast, missing ARIA labels, keyboard navigation issues, screen reader compatibility, and focus management. Returns structured accessibility issue reports with WCAG compliance information.

• accessibility-design-checker

  Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.

• agent-capability-assessor

  Assesses agent capabilities by analyzing agent files and determining what tasks they can handle. Use when you need to evaluate if an existing agent can handle a task or if a new agent is needed. Reviews agent descriptions, skills, and workflows to determine capability match.

• agent-creator

  Creates new agent files with complete specifications, following the same format as existing agents. Use when a new agent is needed for tasks that existing agents cannot handle. Generates agent markdown files with name, description, core principles, workflow, and integration details.

• api-implementer

  Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.

• architecture-reviewer

  Reviews code architecture for design issues including poor separation of concerns, tight coupling, missing abstractions, design pattern violations, scalability concerns, and maintainability issues. Returns structured architecture review reports with improvement suggestions.

• best-practices-checker

  Checks code for best practice violations including DRY violations, SOLID principles, error handling patterns, testing practices, documentation standards, and version control practices. Returns structured best practice reports with improvement suggestions.

• bug-detector

  Detects bugs, logic errors, and edge case handling issues in code. Use when reviewing code for runtime errors, null/undefined handling, type errors, and edge cases. Returns structured bug reports with file paths, line numbers, and suggested fixes.

• changelog-generator

  Generate changelog entries from git commits, pull requests, or code changes. Use when creating release notes, updating CHANGELOG.md, or documenting what changed in a version.

• code-documentation

  Generate comprehensive code documentation including docstrings, comments, and API documentation. Use when code lacks documentation, needs better explanations, or requires API docs. Focuses on clarity, completeness, and following language-specific documentation standards.

• code-style-analyzer

  Analyzes code for style and formatting issues including inconsistent formatting, naming conventions, code organization, comment quality, unused code, and magic numbers. Returns structured style issue reports with suggestions for improvement.

• color-system-designer

  Creates color palettes and color systems for applications. Defines primary, secondary, neutral colors, and semantic colors (success, error, warning, info). Ensures accessibility compliance and provides usage guidelines.

• component-designer

  Designs reusable UI components including buttons, inputs, cards, modals, and other interface elements. Specifies states, variations, and usage guidelines. Considers accessibility and responsive behavior.

• component-implementer

  Implements UI components from design specifications. Use when implementing frontend components, pages, or UI elements. Follows design specs from ui-ux-designer, implements responsive design, and ensures accessibility.

• config-setup

  Sets up configuration files, environment variables, and project configuration. Use when setting up project configuration, environment setup, or configuration management. Creates config files, .env examples, and configuration documentation.

• conflict-resolver

  Resolves conflicts between agents or approaches when disagreements arise. Use when agents have conflicting recommendations, different approaches to the same problem, or disagreements on priorities. Analyzes conflicts, evaluates options, and makes decisions to resolve conflicts.

• convert-to-extension

  Converts a Claude Code plugin into a fully functional VS Code Chat Extension. Use when a plugin folder (with agents, skills, commands, templates, hooks, and markdown files) needs to be packaged as a VS Code extension using the Chat Participant API. Handles the full lifecycle from analysis through sc

• database-implementer

  Creates database schemas, migrations, queries, and data access layers. Use when implementing database-related tasks. Handles schema design, migrations, CRUD operations, and database optimization.

• design-system

  Design specification guide — layout, components, color, typography, spacing, interactions, responsive, accessibility.

• escalation-handler

  Handles escalations and determines appropriate escalation paths. Use when issues arise that need escalation or when determining whether to escalate to user vs. handle internally. Analyzes issues, determines severity, and routes to appropriate resolution path.

• git-commit-helper

  Generate well-structured git commit messages following conventional commits format. Use when committing changes, creating commit messages, or when commit history needs improvement. Ensures commits are clear, descriptive, and follow project conventions.

• idea-refiner

  Collaboratively refine ideas with the user before handing off to autonomous agents. Asks clarifying questions, proposes approaches with tradeoffs, and reaches agreement before execution.

• implementation-planner

  Creates detailed, step-by-step implementation plans from specifications. Use when you have requirements and need to break them down into actionable implementation steps. Organizes work into phases, identifies dependencies, and creates a clear roadmap.

• import-formatter

  Format and organize import statements in code files. Use when imports are messy, unordered, or need to follow project conventions. Automatically groups imports by type (standard library, third-party, local) and sorts them alphabetically.

• interaction-designer

  Designs interactions, animations, transitions, and micro-interactions. Specifies hover states, click feedback, loading states, and user feedback mechanisms. Ensures interactions are accessible and performant.

• layout-designer

  Designs page layouts, grid systems, and structural arrangements. Use when creating layouts for pages, sections, or components. Considers responsive design, visual hierarchy, and accessibility.

• performance-analyzer

  Analyzes code for performance issues including inefficient algorithms, unnecessary computations, memory leaks, large file sizes, slow queries, and missing caching. Returns structured performance issue reports with optimization suggestions.

• quality-gate-manager

  Manages quality gates and checkpoints to ensure work meets standards before proceeding to next phases. Use when you need to verify work quality, set quality standards, or decide if work is ready to proceed. Defines quality criteria, checks work against criteria, and makes go/no-go decisions.

• requirement-analyzer

  Analyzes ideas and extracts functional and non-functional requirements. Use when breaking down concepts into specific, measurable requirements. Identifies what needs to be built, constraints, and success criteria.

• resource-allocation-optimizer

  Comprehensive resource management that prioritizes tasks, allocates agents, and optimizes the allocation in a single pass. Use when you need to plan work execution, assign agents to tasks, or optimize resource usage. Combines task prioritization, agent allocation, and optimization into one unified w

• responsive-design-planner

  Plans responsive design breakpoints, mobile-first approaches, and adaptive layouts. Defines how designs adapt across different screen sizes and devices. Considers touch vs mouse interactions.

• security-scanner

  Scans code for security vulnerabilities including SQL injection, XSS, hardcoded secrets, insecure authentication, and missing input validation. Returns structured security issue reports with file paths, line numbers, and remediation steps.

• spacing-system-designer

  Creates spacing and sizing systems including margins, padding, gaps, and consistent spacing scales. Defines spacing tokens and usage guidelines for consistent layouts.

• specification-checker

  Compares code implementation against specifications and requirements. Verifies functional requirements, non-functional requirements, acceptance criteria, and technical specifications are met. Returns structured reports of specification gaps and misalignments.

• task-to-agent-matcher

  Matches tasks to appropriate agents by analyzing task requirements and finding agents with matching capabilities. Use when you need to assign tasks to agents or determine which agent should handle a task. Considers task type, requirements, and agent capabilities.

• team-health-checker

  Audits the scrum team structure by analyzing all agents and skills. Identifies coverage gaps, overlapping responsibilities, workflow issues, and skill utilization problems. Use when you need to review and improve team efficiency, validate team structure, or diagnose operational issues.

• technical-spec-writer

  Creates detailed technical specifications including architecture, data models, APIs, and technology choices. Use when you need to document technical implementation details, system design, or API contracts. Provides concrete technical guidance for implementation.

• test-writer

  Writes comprehensive test cases including unit tests, integration tests, and E2E tests. Supports two modes - writing tests from design specs/requirements OR generating tests by analyzing existing code. Creates tests that cover happy paths, edge cases, error conditions, and follow testing best practi

• typography-designer

  Designs typography systems including font choices, font sizes, font weights, line heights, and text styles. Creates type scale and defines usage guidelines. Ensures readability and accessibility.

• utility-implementer

  Implements utility functions, helpers, and shared code. Use when implementing reusable functions, validation utilities, formatting functions, or helper modules. Creates clean, reusable utility code.

Slash commands (2)

• /mlst:build
• /mlst:convert-to-extension

Subagents (7)

• code-reviewer-feedback

  Reviews code and provides structured feedback documents for coding agents. Use when code needs review after commits to main, branch merges, or pull requests. Orchestrates multiple review skills to create comprehensive, actionable feedback with file paths, line numbers, code examples, and prioritizat

• implementation-engineer

  Implements tasks from scrum-master, submits to code-reviewer-feedback, responds to feedback iteratively until approved, then commits changes. Use when you have tasks ready for implementation. Handles both frontend and backend implementation work.

• infrastructure-engineer

  Sets up infrastructure, CI/CD pipelines, deployment configurations, and development environments. Use when tasks involve infrastructure, deployment, or DevOps work. Creates configuration files, sets up automation, and ensures deployment readiness. Accepts infrastructure and deployment tasks from scr

• scrum-master

  Breaks down specifications into atomic, modular tasks that can be implemented independently. Use when you have a specification that needs to be converted into actionable tasks with dependencies, acceptance criteria, and testing requirements.

• specification-writer

  Transforms ideas into detailed specifications and implementation directions. Use when you have a concept or idea that needs to be broken down into actionable specifications for another agent to implement. Creates structured plans with requirements, technical details, and step-by-step directions.

• test-runner

  Writes and runs tests for implementations. Use after implementation to validate code works correctly, or on-demand for regression testing. Tests must pass before code proceeds to review. Can generate missing tests and execute full test suites.

• ui-ux-designer

  Accepts design-focused tasks from scrum-master and adds design specifications. Use when tasks require UI/UX design work. Creates design specs in markdown, considers accessibility and responsive design, and updates task documents with design input using a hybrid approach (sections for simple tasks, s

Similar plugins