Add markitdown to community catalog

[BenBtg]

Adds the MarkItDown Document Converter community extension to the Spec Kit extension catalog.

This extension converts documents (PDF, Word, PowerPoint, Excel, and more) to Markdown using Microsoft's MarkItDown library, making them available as spec reference material in Spec Kit workflows. It provides a single convert command and requires markitdown >= 0.1.0.

Changes:

• Added markitdown entry to catalog.community.json
• Added MarkItDown row to the community extensions table in README.md
• Bumped catalog updated_at timestamp to 2026-04-28

Testing

• Tested locally with uv run specify --help
• Ran existing tests with uv sync && uv run pytest
• Tested with a sample project (if applicable)

AI Disclosure

• I did not use AI assistance for this contribution
• I did use AI assistance (describe below)

Extension authored with GitHub Copilot assistance, including the extension.yml manifest, convert.md instruction file, and catalog entry.

[Copilot]

Pull request overview

Adds a new community extension entry to Spec Kit’s extension catalog so users can discover and use the MarkItDown-based document-to-Markdown converter in workflows.

Changes:

• Updated extensions/catalog.community.json updated_at and added new catalog entry/entries.
• Added a new row to the Community Extensions table in README.md.

Show a summary per file

File	Description
extensions/catalog.community.json	Bumps catalog timestamp and adds new extension metadata entries (including MarkItDown; also includes an unexpected duplicate m365 entry).
README.md	Adds Community Extensions table rows for MarkItDown (and Microsoft 365).

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (2)

extensions/catalog.community.json:1252

• The extensions object contains two separate "m365" entries (one earlier around lines 944–982 and another here). In JSON, duplicate keys are ambiguous and most parsers will silently keep only the last occurrence, which would discard the first entry and make the catalog data inconsistent (different descriptions/commands/created_at/etc.). Keep a single m365 entry and remove the duplicate; also ensure the remaining entry’s fields are consistent and placed in the correct sorted position within the catalog.

This issue also appears on line 1260 of the same file.

    "memory-loader": {
      "name": "Memory Loader",
      "id": "memory-loader",
      "description": "Loads .specify/memory/ files before spec-kit lifecycle commands so LLM agents have project governance context",
      "author": "KevinBrown5280",

extensions/catalog.community.json:1263

• This requires.tools value is a list of strings, but the publishing guide’s catalog format uses an array of objects (with at least a name, optionally version/required). Using a different shape here makes the catalog inconsistent and can break tooling that assumes the documented schema. Please switch tools to the object form (or remove this block if you’re deleting the duplicate m365 entry).

      "requires": {
        "speckit_version": ">=0.6.0"
      },
      "provides": {

• Files reviewed: 2/2 changed files
• Comments generated: 2

[Copilot]

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0 new

[mnriem]

Thank you!