mk-spec-master 0.1.0__tar.gz

mk_spec_master-0.1.0/.dockerignore

@@ -0,0 +1,15 @@
+.git
+.github
+.venv
+venv
+__pycache__
+*.pyc
+.pytest_cache
+.mypy_cache
+.ruff_cache
+dist
+build
+*.egg-info
+docs
+examples
+.DS_Store

mk_spec_master-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,74 @@
+name: Publish to PyPI
+
+# Triggered by every published GitHub Release. Releases are created
+# manually (via `gh release create` or the GitHub UI) so we keep
+# control over what hits PyPI — no auto-publish on tag push.
+#
+# Authentication: PyPI Trusted Publishing (OIDC). No API token stored;
+# instead a one-time setup on PyPI links this repo + workflow file to
+# the project name. Setup mirrors mk-qa-master's "Publishing" section.
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  # OIDC token exchange for Trusted Publishing — no PYPI_API_TOKEN secret needed.
+  id-token: write
+  contents: read
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tooling
+        run: python -m pip install --upgrade build twine
+
+      - name: Verify pyproject version matches the release tag
+        # The release tag (e.g. `v0.1.0`) must equal `v<pyproject.version>`.
+        # Catches the "tagged but forgot to bump pyproject" failure mode
+        # before we ship a wrong-versioned wheel.
+        run: |
+          set -eu
+          TAG="${GITHUB_REF_NAME#v}"
+          PY_VER=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+          echo "release tag (without v) = $TAG"
+          echo "pyproject version       = $PY_VER"
+          test "$TAG" = "$PY_VER"
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      - name: Validate distribution metadata
+        run: twine check dist/*
+
+      - name: Upload distribution artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/mk-spec-master/
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

mk_spec_master-0.1.0/.gitignore

@@ -0,0 +1,42 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+.venv
+venv/
+ENV/
+
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.tox/
+htmlcov/
+.coverage
+.coverage.*
+
+.idea/
+.vscode/
+*.swp
+*.swo
+.DS_Store
+
+# mk-spec-master runtime data (when dogfooding in this repo)
+.mk-spec-master/

mk_spec_master-0.1.0/Dockerfile

@@ -0,0 +1,28 @@
+# MK Spec Master container — built primarily so Glama (and any other MCP
+# catalog that introspects servers in a sandbox) can boot the server,
+# send `initialize` + `tools/list` over stdio, and confirm a clean
+# JSON-RPC response.
+#
+# Day-to-day use stays `uvx mk-spec-master` on the host: real spec
+# fetches need access to the user's repo, network for Linear/JIRA APIs,
+# and credentials that live outside any sane container.
+
+FROM python:3.12-slim
+
+# Install from local source so the image always reflects the current
+# commit (introspection should pass even before a PyPI release).
+WORKDIR /srv
+COPY pyproject.toml README.md LICENSE ./
+COPY src/ ./src/
+RUN pip install --no-cache-dir .
+
+# Defaults for the introspection probe. SPEC_PROJECT_ROOT just needs to
+# resolve to a writable path — config.py only `.resolve()`s it, doesn't
+# require it to exist until a real fetch happens (which we don't expect
+# inside this container).
+ENV SPEC_SOURCE=markdown_local \
+    SPEC_PROJECT_ROOT=/tmp/spec-project \
+    PYTHONUNBUFFERED=1
+
+WORKDIR /tmp/spec-project
+ENTRYPOINT ["python", "-m", "mk_spec_master.server"]

mk_spec_master-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jack Kao (kao273183)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

mk_spec_master-0.1.0/PKG-INFO

@@ -0,0 +1,78 @@
+Metadata-Version: 2.4
+Name: mk-spec-master
+Version: 0.1.0
+Summary: MCP server bridging specs (Linear / JIRA / GitHub Issues / Notion / Markdown / Figma) to tests, with bidirectional traceability and a spec-quality coach (AI 規格大師)
+Project-URL: Homepage, https://github.com/kao273183/mk-spec-master
+Project-URL: Repository, https://github.com/kao273183/mk-spec-master
+Author-email: Jack Kao <52775937+kao273183@users.noreply.github.com>
+License: MIT
+License-File: LICENSE
+Keywords: acceptance-criteria,mcp,model-context-protocol,requirements,sdd,spec-driven-development,testing,traceability
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Requires-Dist: mcp>=1.0.0
+Description-Content-Type: text/markdown
+
+<h1 align="center">MK Spec Master</h1>
+
+<p align="center">
+  <em>AI 規格大師 — specs in, scenarios out. Bidirectional traceability so you always know what's tested.</em>
+</p>
+
+<p align="center">
+  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT" /></a>
+  <img src="https://img.shields.io/badge/status-pre--alpha-orange.svg" alt="Status: Pre-alpha" />
+</p>
+
+> **⚠️ Alpha — v0.1 MVP.** 7 tools shipped (markdown_local + github_issues sources). Full design in [`docs/prd.md`](docs/prd.md). Next: Linear / JIRA adapters + coverage matrix in v0.2.
+
+---
+
+## What this is
+
+An MCP server that turns specs — Linear tickets, JIRA stories, GitHub Issues, Notion pages, Figma annotations, plain Markdown — into structured test scenarios, hands them to any test runner (via [`mk-qa-master`](https://github.com/kao273183/mk-qa-master) or directly), and maintains a live spec ↔ test coverage matrix.
+
+Sibling to `mk-qa-master` in the `mk-*` family of opinionated AI-QA MCPs.
+
+## Why this is missing from the ecosystem
+
+| Tool | Lock-in | What we do differently |
+|---|---|---|
+| AWS Kiro | AWS IDE only, proprietary | MCP-native, multi-client, open source |
+| Jama Connect MCP | $50k+/year, enterprise-only | SMB / indie / AI-native segment |
+| GitHub Spec Kit | spec→code; runtime test coverage out of scope | We add runtime test coverage |
+| testomat.io / JIRA MCPs | Single source (JIRA), SaaS lock | Multi-source, file-based index, no lock |
+
+See [`docs/prd.md` §4](docs/prd.md) for the full positioning.
+
+## Status
+
+| Milestone | Target | Status |
+|---|---|---|
+| v0.1 (MVP — markdown_local + github_issues, 7 tools) | June 2026 | ✅ Shipped |
+| v0.2 (Linear, JIRA, coverage matrix, spec-quality coach) | Aug 2026 | ⬜ |
+| v0.3 (Notion, Figma, auto-link, optimization plan) | Oct 2026 | ⬜ |
+| v1.0 (production-ready, docs, integration recipes) | Q4 2026 | ⬜ |
+
+## Quick design read
+
+- **Vision + problem**: [`docs/prd.md` §1–2](docs/prd.md)
+- **Competitive positioning**: [`docs/prd.md` §4](docs/prd.md)
+- **Tool surface**: [`docs/prd.md` §8](docs/prd.md)
+- **Walkthrough (end-to-end with mk-qa-master)**: [`docs/prd.md` §19](docs/prd.md)
+
+## Related
+
+- [mk-qa-master](https://github.com/kao273183/mk-qa-master) — the QA loop sibling. Tests run via mk-qa-master; coverage tracked here.
+
+## License
+
+MIT — see [LICENSE](LICENSE).

mk_spec_master-0.1.0/README.md

@@ -0,0 +1,55 @@
+<h1 align="center">MK Spec Master</h1>
+
+<p align="center">
+  <em>AI 規格大師 — specs in, scenarios out. Bidirectional traceability so you always know what's tested.</em>
+</p>
+
+<p align="center">
+  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT" /></a>
+  <img src="https://img.shields.io/badge/status-pre--alpha-orange.svg" alt="Status: Pre-alpha" />
+</p>
+
+> **⚠️ Alpha — v0.1 MVP.** 7 tools shipped (markdown_local + github_issues sources). Full design in [`docs/prd.md`](docs/prd.md). Next: Linear / JIRA adapters + coverage matrix in v0.2.
+
+---
+
+## What this is
+
+An MCP server that turns specs — Linear tickets, JIRA stories, GitHub Issues, Notion pages, Figma annotations, plain Markdown — into structured test scenarios, hands them to any test runner (via [`mk-qa-master`](https://github.com/kao273183/mk-qa-master) or directly), and maintains a live spec ↔ test coverage matrix.
+
+Sibling to `mk-qa-master` in the `mk-*` family of opinionated AI-QA MCPs.
+
+## Why this is missing from the ecosystem
+
+| Tool | Lock-in | What we do differently |
+|---|---|---|
+| AWS Kiro | AWS IDE only, proprietary | MCP-native, multi-client, open source |
+| Jama Connect MCP | $50k+/year, enterprise-only | SMB / indie / AI-native segment |
+| GitHub Spec Kit | spec→code; runtime test coverage out of scope | We add runtime test coverage |
+| testomat.io / JIRA MCPs | Single source (JIRA), SaaS lock | Multi-source, file-based index, no lock |
+
+See [`docs/prd.md` §4](docs/prd.md) for the full positioning.
+
+## Status
+
+| Milestone | Target | Status |
+|---|---|---|
+| v0.1 (MVP — markdown_local + github_issues, 7 tools) | June 2026 | ✅ Shipped |
+| v0.2 (Linear, JIRA, coverage matrix, spec-quality coach) | Aug 2026 | ⬜ |
+| v0.3 (Notion, Figma, auto-link, optimization plan) | Oct 2026 | ⬜ |
+| v1.0 (production-ready, docs, integration recipes) | Q4 2026 | ⬜ |
+
+## Quick design read
+
+- **Vision + problem**: [`docs/prd.md` §1–2](docs/prd.md)
+- **Competitive positioning**: [`docs/prd.md` §4](docs/prd.md)
+- **Tool surface**: [`docs/prd.md` §8](docs/prd.md)
+- **Walkthrough (end-to-end with mk-qa-master)**: [`docs/prd.md` §19](docs/prd.md)
+
+## Related
+
+- [mk-qa-master](https://github.com/kao273183/mk-qa-master) — the QA loop sibling. Tests run via mk-qa-master; coverage tracked here.
+
+## License
+
+MIT — see [LICENSE](LICENSE).