specify-cli 1.2.2__tar.gz → 1.2.3__tar.gz

{specify_cli-1.2.2 → specify_cli-1.2.3}/.github/security-audit-requirements.txt

@@ -318,6 +318,10 @@ cryptography==50.0.2 \
     --hash=sha256:fa8f5efb344d6908a1ce62f4a24e2e5780f825d6f53f5f50ec5ffacac72936cb \
     --hash=sha256:fdd28f912fccfec1846a94e2e1e8f9b0012f557f0c46fe4f3eb0d7a87afcf90b
     # via pyjwt
+execnet==2.1.2 \
+    --hash=sha256:63d83bfdd9a23e35b9c6a3261412324f964c2ec8dcd8d3c6916ee9373e0befcd \
+    --hash=sha256:67fba928dd5a544b783f6056f449e5e3931a5c378b128bc18501f7ea79e296ec
+    # via pytest-xdist
 h11==0.16.0 ; sys_platform != 'emscripten' \
     --hash=sha256:4e35b956cf45792e4caa5885e69fba00bdbc6ffafbfa020300e549b208ee5ff1 \
     --hash=sha256:63cf8bbe7522de3bf65932fda1d9c2772064ffb3dae62d55932da54b31cb6c86
@@ -543,10 +547,15 @@ pytest==9.1.1 \
     # via
     #   specify-cli (pyproject.toml)
     #   pytest-cov
+    #   pytest-xdist
 pytest-cov==7.1.0 \
     --hash=sha256:30674f2b5f6351aa09702a9c8c364f6a01c27aae0c1366ae8016160d1efc56b2 \
     --hash=sha256:a0461110b7865f9a271aa1b51e516c9a95de9d696734a2f71e3e78f46e1d4678
     # via specify-cli (pyproject.toml)
+pytest-xdist==3.8.0 \
+    --hash=sha256:202ca578cfeb7370784a8c33d6d05bc6e13b4f25b5053c30a152269fd10f0b88 \
+    --hash=sha256:7e578125ec9bc6050861aa93f2d59f1d8d085595d6551c2c90b6f4fad8d3a9f1
+    # via specify-cli (pyproject.toml)
 python-multipart==0.0.32 \
     --hash=sha256:be54b7f3fa167bb83e4fcd936b887b708f4e57fe75911c02aebf53efaf8d938e \
     --hash=sha256:ff6d3f776f16878c894e52e107296ffc890e913c611b1a4ec6c44e2821fe2e23

{specify_cli-1.2.2 → specify_cli-1.2.3}/.github/workflows/lint.yml

@@ -23,7 +23,6 @@ jobs:
         SECURITY.md
         SUPPORT.md
         spec-driven.md
-        integrations/*.md
         presets/*.md
         workflows/*.md
     steps:

{specify_cli-1.2.2 → specify_cli-1.2.3}/.github/workflows/test.yml

@@ -52,4 +52,4 @@ jobs:
       # because it cannot handle native Windows paths in test fixtures.
       # See tests/conftest.py::_has_working_bash() for details.
       - name: Run tests
-        run: uv run pytest
+        run: uv run pytest -n 2

{specify_cli-1.2.2 → specify_cli-1.2.3}/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 <!-- insert new changelog below this comment -->
 
+## [1.2.3] - 2026-10-22
+
+### Changed
+
+- Feat/4913 workflow mcp inventory (#5054)
+- docs: correct built-in workflow step source paths (#5059)
+- fix(events): preserve dispatcher ownership during cleanup (#5055)
+- feat: add .presetignore support (#5020)
+- fix(scripts): write --json output of the Python helpers as ASCII (#5048)
+- Update Linear Weave extension to v1.0.2 (#5049)
+- fix(events): preserve unowned Vibe hooks files (#4646)
+- ci: shorten test runs with two workers and faster fixture shutdown (#5051)
+- fix(powershell): treat bracketed feature paths literally (#4970)
+- fix(cli): align integration guidance with available output (#5041)
+- fix(integrations): map Pi JSON dispatch to --mode json (#5043)
+- docs: organize agent-specific integration documentation (#5034)
+- feat(integration): add none for shared scaffolding only (#5030)
+- fix(extensions): reject malformed catalog entries before removal (#5033)
+- fix(integrations): map Kimi Code JSON dispatch to --output-format stream-json (#5031)
+- docs: streamline README onboarding and process guides (#5029)
+- docs: distinguish extension events from hooks (#5026)
+- fix(workflows): keep integer number inputs exact instead of rounding them (#5027)
+- docs: say how to replace an older install before specify init (#5004)
+- chore: release 1.2.2, begin 1.2.3.dev0 development (#5024)
+
 ## [1.2.2] - 2026-10-19
 
 ### Changed

{specify_cli-1.2.2 → specify_cli-1.2.3}/CONTRIBUTING.md

@@ -11,7 +11,7 @@ These are one time installations required to be able to test your changes locall
 1. Install [Python 3.11+](https://www.python.org/downloads/)
 1. Install [uv](https://docs.astral.sh/uv/) for package management
 1. Install [Git](https://git-scm.com/downloads)
-1. Have an [AI coding agent available](https://github.github.io/spec-kit/reference/integrations.html)
+1. Have an [AI coding agent available](https://github.github.io/spec-kit/integrations/index.html)
 
 <details>
 <summary><b>💡 Hint if you are using <code>VSCode</code> or <code>GitHub Codespaces</code> as your IDE</b></summary>
@@ -172,7 +172,7 @@ its pinned archive URL and preferably its SHA-256 in a catalog. Registering a
 catalog only enables discovery/download; importing executable adapter code
 requires the user's trust decision and an install-enabled source. Follow the
 [integration API and lifecycle design](design/integration.md#external-adapter-package-contract)
-and [integration catalog contribution guide](integrations/CONTRIBUTING.md).
+and [integration catalog contribution guide](docs/integrations/contributing.md).
 Add public-path positive and negative tests rather than injecting test classes
 directly into the registry; include fresh-process loading and rollback evidence.
 

{specify_cli-1.2.2 → specify_cli-1.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: specify-cli
-Version: 1.2.2
+Version: 1.2.3
 Summary: Specify CLI, part of GitHub Spec Kit. A tool to bootstrap your projects for Spec-Driven Development (SDD).
 License-File: LICENSE
 Requires-Python: >=3.11
@@ -16,6 +16,7 @@ Requires-Dist: rich
 Requires-Dist: typer>=0.24.0
 Provides-Extra: test
 Requires-Dist: pytest-cov>=4.0; extra == 'test'
+Requires-Dist: pytest-xdist>=3.0; extra == 'test'
 Requires-Dist: pytest>=7.0; extra == 'test'
 Description-Content-Type: text/markdown
 
@@ -52,7 +53,7 @@ process, customize it, or bring your own.
 | Decide whether an idea deserves investment | [Idea assessment](#idea-assessment) | An evidence-backed go, clarify, or stop decision |
 | Adopt or create a different process | [Your own process](#capabilities) | A process adapted or assembled from reusable primitives |
 
-These are **independent entry points**, not mandatory phases. SDD ships in core;
+These are independent entry points, not mandatory phases. SDD ships in core;
 bug fixing and assessment are bundled extensions you install when needed, and
 the primitives below let you adopt or create other processes.
 
@@ -62,10 +63,11 @@ Spec Kit combines ready-to-use processes with composable mechanisms:
 
 | Capability | Spec Kit mechanism |
 | --- | --- |
-| Connect to or switch between coding agents | [Integration](https://github.github.io/spec-kit/reference/integrations.html) |
+| Connect to or switch between coding agents | [Integration](https://github.github.io/spec-kit/integrations/index.html) |
 | Add a command, quality gate, or complete process | [Extension](https://github.github.io/spec-kit/reference/extensions.html) |
 | Connect a process to an external tool or service | [Extension](https://github.github.io/spec-kit/reference/extensions.html) |
-| React to coding-agent lifecycle events | [Extension event hook](https://github.github.io/spec-kit/reference/extensions.html#project-extension-and-hook-configuration) |
+| React to coding-agent lifecycle events | [Extension runtime event](https://github.github.io/spec-kit/reference/extensions.html#extension-runtime-events) |
+| Run extension commands before or after Spec Kit commands | [Extension hook](https://github.github.io/spec-kit/reference/extensions.html#project-extension-and-hook-configuration) |
 | Adapt templates, commands, terminology, or methodology | [Preset](https://github.github.io/spec-kit/reference/presets.html) |
 | Enforce organizational or regulatory standards | [Preset](https://github.github.io/spec-kit/reference/presets.html) |
 | Override a template for one project | [Project-local override](https://github.github.io/spec-kit/guides/customization.html#project-local-overrides-and-resolution) |
@@ -90,9 +92,11 @@ community source code before installing or running it.
 
 ## Get started
 
-You need **Python 3.11+**, **[uv](https://github.github.io/spec-kit/install/uv.html)**,
+You need Python 3.11+, [uv](https://github.github.io/spec-kit/install/uv.html),
 and a supported AI coding agent on Linux, macOS, or Windows.
-For **CLI setup only**, run this in your terminal to install Spec Kit and create a project:
+
+Run these commands in your terminal to install Spec Kit and create a project.
+This example uses GitHub Copilot.
 
 ```bash
 uv tool install specify-cli
@@ -102,34 +106,30 @@ cd my-project
 
 <a id="-supported-ai-coding-agent-integrations"></a>
 
-The examples use **GitHub Copilot's default skills mode**. Replace `copilot` with
-your [integration key](https://github.github.io/spec-kit/reference/integrations.html)
-to use another supported agent.
+After installing the Specify CLI and creating your project, launch your coding
+agent in the project directory, then choose a process below.
 
-Already have code? Follow the
-[existing-project guide](https://github.github.io/spec-kit/guides/existing-projects.html).
-For pinned releases, other installers, CI, or troubleshooting, see
-[Installation](https://github.github.io/spec-kit/installation.html).
-To update an existing installation, see [Upgrade](https://github.github.io/spec-kit/upgrade.html).
+For other setups:
 
-Now **launch your coding agent in the project directory** and choose a process
-below. Invoke each `/speckit-*` **skill in your agent's chat**, one at a time,
-and review the result before continuing. These are agent skills, not terminal
-commands. Other agents and modes may use
-[different invocation syntax](https://github.github.io/spec-kit/reference/integrations.html#command-invocation).
+- [Installation](https://github.github.io/spec-kit/installation.html) for pinned releases, other installers, CI, and troubleshooting.
+- [Existing projects](https://github.github.io/spec-kit/guides/existing-projects.html) to start with code you already have.
+- [Other agents](https://github.github.io/spec-kit/integrations/index.html) for integration keys and [invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
+- [Upgrade](https://github.github.io/spec-kit/upgrade.html) to update an existing installation.
 
 <a id="-what-is-spec-driven-development"></a>
 <a id="sdd-quickstart"></a>
 
 ## Spec-Driven Development
 
-Define **what and why** before deciding **how** to build it. SDD turns your
-requirements into a specification, a technical plan, and actionable tasks,
-then guides implementation against those artifacts.
+Define what to build and why, then turn the specification into a plan, tasks,
+and working code.
 
-**Constitution once per project; specify → plan → tasks → implement → converge per feature.**
+The minimal flow is shown below. Create a constitution once per project and
+repeat the remaining steps for each feature. Run these skills in your agent's
+chat, not your terminal, one at a time, reviewing each result before continuing.
 
-Invoke these skills in your agent's chat:
+This example uses GitHub Copilot's default skills syntax. For another agent,
+use its [equivalent invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
 
 ```text
 /speckit-constitution Create principles focused on code quality, testing, and maintainability.
@@ -140,9 +140,8 @@ Invoke these skills in your agent's chat:
 /speckit-converge
 ```
 
-Repeat **implement → converge** until convergence reports **Converged**.
-Add clarification, checklists, and consistency analysis when you need extra
-quality gates.
+Repeat implement and converge until convergence reports `Converged`.
+For clarification, checklists, and consistency analysis, see the SDD walkthrough.
 
 [SDD walkthrough](https://github.github.io/spec-kit/quickstart.html) ·
 [Command reference](https://github.github.io/spec-kit/reference/agentic-sdd.html)
@@ -152,16 +151,20 @@ quality gates.
 
 ## Bug fixing
 
-Keep diagnosis, repair, and verification separate so the agent fixes the assessed
-cause and checks the original symptom. No SDD feature workflow is required first.
+Assess the cause, fix the bug, and verify the original symptom is resolved.
+No SDD feature workflow is required first.
 
-**CLI setup (terminal):** install the opt-in extension from the project directory:
+Install the bug-fixing extension in your terminal, from the project directory:
 
 ```bash
 specify extension add bug
 ```
 
-Then invoke the **assess → fix → test** skills in your agent's chat:
+Run these skills in your agent's chat, not your terminal, one at a time,
+reviewing each result before continuing.
+
+This example uses GitHub Copilot's default skills syntax. For another agent,
+use its [equivalent invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
 
 ```text
 /speckit-bug-assess "Submitting an empty password crashes the login form." slug=login-crash
@@ -169,8 +172,8 @@ Then invoke the **assess → fix → test** skills in your agent's chat:
 /speckit-bug-test slug=login-crash
 ```
 
-The reports live in `.specify/bugs/login-crash/`. Review the final verdict:
-`verified`, `partial`, or `failed`. Missing verification is not a successful fix.
+Review the reports in `.specify/bugs/login-crash/`. The final verdict is
+`verified`, `partial`, or `failed`; only `verified` confirms a successful fix.
 
 [Bug-fixing walkthrough](https://github.github.io/spec-kit/guides/bugfix.html) ·
 [Command reference](https://github.github.io/spec-kit/reference/agentic-bugfix.html)
@@ -180,16 +183,20 @@ The reports live in `.specify/bugs/login-crash/`. Review the final verdict:
 
 ## Idea assessment
 
-Gather evidence before committing to an idea, whether or not it becomes software.
-This standalone process works even in a project with no source code.
+Gather evidence to decide whether an idea is worth pursuing.
+No source code or SDD feature workflow is required.
 
-**CLI setup (terminal):** install the opt-in extension from the project directory:
+Install the assessment extension in your terminal, from the project directory:
 
 ```bash
 specify extension add assess
 ```
 
-Then invoke the **intake → research → define → shape → decide** skills in your agent's chat:
+Run these skills in your agent's chat, not your terminal, one at a time,
+reviewing each result before continuing.
+
+This example uses GitHub Copilot's default skills syntax. For another agent,
+use its [equivalent invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
 
 ```text
 /speckit-assess-intake "Let users work offline and sync when they reconnect." slug=offline-mode
@@ -199,11 +206,13 @@ Then invoke the **intake → research → define → shape → decide** skills i
 /speckit-assess-decide slug=offline-mode
 ```
 
-The artifacts live in `.specify/assessments/offline-mode/`, ending in a
-**go / needs-clarification / kill** decision. Resolve unknowns by refining the
-existing Markdown artifacts directly or with the agent, rather than regenerating
-whole stages. A `go` decision can be handed to `/speckit-specify` if you choose
-to build it; stopping with a documented reason is also a useful result.
+Review the artifacts in `.specify/assessments/offline-mode/` and the final
+decision: `go`, `needs-clarification`, or `kill`. Resolve unknowns by editing the
+existing Markdown artifacts, directly or with your agent, rather than rerunning
+whole stages. If you choose to build a software idea with a `go` decision,
+establish a project constitution if needed, then pass the handoff summary from
+`decision.md` to `/speckit-specify`. Stopping with a documented reason is also a
+useful outcome.
 
 [Assessment walkthrough](https://github.github.io/spec-kit/guides/assessment.html) ·
 [Command reference](https://github.github.io/spec-kit/reference/agentic-assessment.html)
@@ -214,12 +223,20 @@ to build it; stopping with a documented reason is also a useful result.
 
 ## Customize or bring your own process
 
-**Extensions** add capabilities, **presets** adapt existing behavior,
-**workflows** automate steps, and **bundles** package a role-based setup.
-Use project-local overrides for one-off template changes.
+Customize Spec-Driven Development, bug fixing, or idea assessment to fit your
+team's standards. Or bring your own process without adopting any of them.
+Combine the [capabilities above](#capabilities) to match your goal:
+
+- Adapt an existing process with a preset, such as requiring regulatory traceability in plans. Use a project-local override for a one-off template change.
+- Bring your own process by adding its commands through an extension and exposing them to your coding agent through an integration.
+- Automate commands and checks in a workflow. Use overlays to adapt an installed workflow without forking it, or add custom workflow steps when the built-in types are not enough.
+- Share a reusable setup by packaging its extensions, presets, workflows, and workflow steps in a bundle.
+
+Start with the smallest change that meets your needs; you do not have to replace
+the whole process.
 
 [Customization guide](https://github.github.io/spec-kit/guides/customization.html) ·
-[Community extensions, presets, bundles, and walkthroughs](https://github.github.io/spec-kit/community/overview.html)
+[Community components and walkthroughs](https://github.github.io/spec-kit/community/overview.html)
 
 <a id="-specify-cli-reference"></a>
 <a id="available-slash-commands"></a>
@@ -227,16 +244,20 @@ Use project-local overrides for one-off template changes.
 <a id="-core-philosophy"></a>
 <a id="-development-phases"></a>
 <a id="-experimental-goals"></a>
-<a id="-video-overview"></a>
 <a id="-does-spec-kit-use-spec-kit"></a>
 
 ## Documentation
 
 - [CLI reference](https://github.github.io/spec-kit/reference/overview.html) and [process commands](https://github.github.io/spec-kit/reference/agentic-sdd.html#command-overview)
 - [SDD philosophy](https://github.github.io/spec-kit/concepts/sdd.html), [full methodology](./spec-driven.md), and [evolving existing specs](https://github.github.io/spec-kit/guides/evolving-specs.html)
-- [Video overview](https://github.github.io/spec-kit/quickstart.html#video-overview) and [project history](https://github.github.io/spec-kit/history.html)
+- [Project history](https://github.github.io/spec-kit/history.html)
 - [How Spec Kit uses Spec Kit](./CONTRIBUTING.md#does-spec-kit-use-spec-kit)
 
+## In the news
+
+- [Open Source Friday: Spec Kit Part 2](https://www.youtube.com/watch?v=8hHCpNVLhmI) (October 16, 2026) — Manfred Riem and Nicole Haugen discuss Spec Kit 1.0 and the expanded toolkit.
+- [Open Source Friday with Spec Kit](https://www.youtube.com/watch?v=2IArMAhkJcE) (May 8, 2026) — An introduction and SDD demonstration with Manfred Riem.
+
 ## Star history
 
 <p align="center">

{specify_cli-1.2.2 → specify_cli-1.2.3}/README.ja.md

@@ -46,11 +46,11 @@ cd my-project
 
 <a id="-対応しているaiコーディングエージェント"></a>
 
-この例では **GitHub Copilotのデフォルトのスキルモード** を使用しています。他の対応エージェントを使う場合は、`copilot` をお使いのエージェントの[連携キー](https://github.github.io/spec-kit/reference/integrations.html)に置き換えてください。
+この例では **GitHub Copilotのデフォルトのスキルモード** を使用しています。他の対応エージェントを使う場合は、`copilot` をお使いのエージェントの[連携キー](https://github.github.io/spec-kit/integrations/index.html)に置き換えてください。
 
 すでにコードがありますか？[既存プロジェクト向けガイド](https://github.github.io/spec-kit/guides/existing-projects.html)を参照してください。バージョン固定でのインストール、その他のインストーラー、CI、トラブルシューティングについては[インストールガイド](https://github.github.io/spec-kit/installation.html)を、既存のインストールを更新する場合は[アップグレードガイド](https://github.github.io/spec-kit/upgrade.html)を参照してください。
 
-ここから**プロジェクトディレクトリでコーディングエージェントを起動し**、下記のいずれかのプロセスを選んでください。各 `/speckit-*` **スキルはエージェントのチャット内で**、1つずつ呼び出し、結果を確認してから次に進んでください。これらはターミナルコマンドではなく、エージェントのスキルです。エージェントやモードによっては、[異なる呼び出し方](https://github.github.io/spec-kit/reference/integrations.html#command-invocation)を使う場合があります。
+ここから**プロジェクトディレクトリでコーディングエージェントを起動し**、下記のいずれかのプロセスを選んでください。各 `/speckit-*` **スキルはエージェントのチャット内で**、1つずつ呼び出し、結果を確認してから次に進んでください。これらはターミナルコマンドではなく、エージェントのスキルです。エージェントやモードによっては、[異なる呼び出し方](https://github.github.io/spec-kit/integrations/cli.html#command-invocation)を使う場合があります。
 
 <a id="-仕様駆動開発とは"></a>
 <a id="sdd-クイックスタート"></a>
@@ -157,7 +157,7 @@ specify extension add assess
 
 - [CLIリファレンス](https://github.github.io/spec-kit/reference/overview.html) と [プロセスコマンド](https://github.github.io/spec-kit/reference/agentic-sdd.html#command-overview)
 - [SDDの理念](https://github.github.io/spec-kit/concepts/sdd.html)、[完全な方法論](./spec-driven.md)、[既存の仕様の進化](https://github.github.io/spec-kit/guides/evolving-specs.html)
-- [紹介動画](https://github.github.io/spec-kit/quickstart.html#video-overview) と [プロジェクトの歴史](https://github.github.io/spec-kit/history.html)
+- [プロジェクトの歴史](https://github.github.io/spec-kit/history.html)
 - [Spec KitはSpec Kit自身をどう使っているか](./CONTRIBUTING.md#does-spec-kit-use-spec-kit)
 
 ## スター数の推移

{specify_cli-1.2.2 → specify_cli-1.2.3}/README.ko.md

@@ -51,7 +51,7 @@ cd my-project
 <a id="-supported-ai-coding-agent-integrations"></a>
 
 예시는 **GitHub Copilot의 기본 스킬 모드**를 기준으로 합니다. 지원되는 다른 에이전트를 쓰려면
-`copilot`을 해당 에이전트의 [통합 키](https://github.github.io/spec-kit/reference/integrations.html)로 바꾸세요.
+`copilot`을 해당 에이전트의 [통합 키](https://github.github.io/spec-kit/integrations/index.html)로 바꾸세요.
 
 이미 코드가 있나요? [기존 프로젝트 가이드](https://github.github.io/spec-kit/guides/existing-projects.html)를 따르세요.
 특정 버전 고정, 다른 설치 방법, CI, 문제 해결은
@@ -61,7 +61,7 @@ cd my-project
 이제 **프로젝트 디렉터리에서 코딩 에이전트를 실행**하고 아래 프로세스 중 하나를 고르세요.
 각 `/speckit-*` **스킬은 에이전트 채팅에서** 한 번에 하나씩 호출하고, 결과를 검토한 뒤 다음으로
 넘어가세요. 이들은 터미널 명령어가 아니라 에이전트 스킬입니다. 에이전트나 모드에 따라
-[호출 문법이 다를 수 있습니다](https://github.github.io/spec-kit/reference/integrations.html#command-invocation).
+[호출 문법이 다를 수 있습니다](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
 
 <a id="-what-is-spec-driven-development"></a>
 <a id="sdd-quickstart"></a>
@@ -170,14 +170,13 @@ specify extension add assess
 <a id="-core-philosophy"></a>
 <a id="-development-phases"></a>
 <a id="-experimental-goals"></a>
-<a id="-video-overview"></a>
 <a id="-does-spec-kit-use-spec-kit"></a>
 
 ## 문서
 
 - [CLI 레퍼런스](https://github.github.io/spec-kit/reference/overview.html)와 [프로세스 명령어](https://github.github.io/spec-kit/reference/agentic-sdd.html#command-overview)
 - [SDD 철학](https://github.github.io/spec-kit/concepts/sdd.html), [전체 방법론](./spec-driven.md), [기존 스펙 발전시키기](https://github.github.io/spec-kit/guides/evolving-specs.html)
-- [소개 영상](https://github.github.io/spec-kit/quickstart.html#video-overview)과 [프로젝트 연혁](https://github.github.io/spec-kit/history.html)
+- [프로젝트 연혁](https://github.github.io/spec-kit/history.html)
 - [Spec Kit이 Spec Kit을 쓰는 방법](./CONTRIBUTING.md#does-spec-kit-use-spec-kit)
 
 ## 스타 추이