markdown-ticket

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 quality gates across any language or repository.

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.

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.

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 modes like `--prep` and organizing outputs under `{TICKETS_PATH}`.