Build and refactor MDT frontend components following project conventions. Use when creating React components, writing CSS classes, working with modals, tabs, or any UI surface in src/. Enforces STYLING.md patterns, Tailwind 3 constraints, and build safety checks.
Run a project-agnostic ticket lifecycle pipeline from discovery and specification through implementation, verification, review, and user-approved close. Use when asked to run the full pipeline, implement a ticket end to end, take a ticket to done, resume a lifecycle pipeline, or coordinate spec-to-code work with…
Instructions for andkirby/markdown-ticket, a project described as: Kanban-style ticket board system using markdown files for storage. Features drag-and-drop ticket management, multi-project support, real-time updates, and integrated document viewer. Lightweight, version-control-friendly project management with MCP…
Use the mdt-cli CLI for quick ticket and project lookups from the terminal. This skill should be used when the user wants to inspect tickets, list projects, create tickets, or update attributes without MCP tools. Prefer mdt-cli over MCP read operations for single-entity lookups. Covers epic-level tickets (level=epic)…
MDT command workflows and ticket/ADR generation for the mdt-all MCP system. Use when asked to create or update MDT CRs/ADRs or to run /mdt: workflows (ticket creation, requirements, BDD, assess, PoC, domain lens/audit, architecture, tests, clarification, tasks, implement, tech-debt, reflection), including selecting…
Interactive clarification workflow for MDT architectural decision records (ADRs) using MCP mdt-all ticket system. Identifies underspecified areas in CR tickets and encodes answers directly into the ticket content.
Capture post-implementation learnings from the conversation and selected workflow artifacts, then encode approved updates into the CR and any chosen MDT documents. Focus on artifact-level insights and specification adjustments only.