mde-linear

Manages Linear issue creation, updates, and status sync for the mdeai sanjiovani workspace.

1|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/amoai-tech/mdeai --skill mde-linear-amoai-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mde-linear
Source: https://github.com/amoai-tech/mdeai/tree/main/.claude/skills/archive/linear/mde-linear
Command: npx skills add https://github.com/amoai-tech/mdeai --skill mde-linear-amoai-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? This Skill enforces mdeai-specific conventions when working with Linear issues, preventing bare issue numbers, title-only descriptions, and premature Done states across the sanjiovani workspace. ## Core Features & Use Cases - Executable Issue Descriptions: Generates full issue skeletons with lettered completion-step checklists (A1–E5), Mermaid Gantt diagrams, and persona-first plain-language summaries. - Issue Lifecycle Workflows: Covers creation, update, and Done-gate workflows including branch naming (ai/san-NNN-spec-id-slug), PR magic words (Closes SAN-NNN), and progress tracker sync with todo.md and changelog.md. - Use Case: When asked to create a Linear issue for a launch P0 task, the Skill drafts a complete description with completion steps, a Gantt chart, required labels (phase:launch, prefix, stack), and creates it via the Linear MCP save_issue tool. ## Quick Start Ask the agent to create a Linear issue for a specific task and it will draft the full executable description with checklist, Gantt diagram, and labels before saving it to the sanjiovani workspace.

Frequently Asked Questions about mde-linear

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Linear issue with a full executable description?

Follow the creation workflow: resolve the full title, draft the description skeleton with lettered completion steps (A1–E5), a Mermaid Gantt diagram, and a skills table, then create it via the MCP save_issue tool or the linear CLI with team, project, and phase labels set.

How do I mark a Linear issue Done in Linear?

Verify all completion steps E1–E5 are checked, run task-verifier on disk claims, confirm the PR merged with Closes SAN-NNN, update the todo.md tracker and changelog, then set the Linear state to Done. Do not flip Done on floor failures or missing evidence.

What labels are required on new Linear issues for this workspace?

Every issue needs one phase label (phase:launch, phase:mvp, or later phases), at least one track label, a prefix label such as prefix:EVT or prefix:PAY, and up to three stack labels like stack:nextjs or stack:copilotkit. Deprecated labels like IMP-* and SCREEN-* must not be used.

Can I use Mermaid diagrams inside Linear issue descriptions?

Yes, Linear descriptions support Markdown with Mermaid fences. Every executable issue requires a Gantt diagram using dateFormat YYYY-MM-DD, and sequence diagrams are added for HITL or routing flows. Pass descriptions with real newlines, not escaped \n, when using MCP.

Why should I not use the mde-linear skill anymore?

The mde-linear skill is deprecated as of 2026-06-20 and superseded by the canonical linear skill in .agents/skills/linear/. All of its content was merged there, so new work should load the linear skill instead of extending this archived version.