From 125de3955d9843a46553c1a7d70add55124efb43 Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Mon, 31 Aug 2026 16:45:23 -0500 Subject: [PATCH 1/3] docs: explain Spec Kit dogfooding Assisted-by: GitHub Copilot (model: GPT-5.6 Sol, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index de92639cec..e4afe801a7 100644 --- a/README.md +++ b/README.md @@ -33,6 +33,7 @@ - [🧩 Making Spec Kit Your Own: Extensions & Presets](#-making-spec-kit-your-own-extensions--presets) - [📦 Bundles: Role-Based Setups](#-bundles-role-based-setups) - [📚 Core Philosophy](#-core-philosophy) +- [🪞 Does Spec Kit Use Spec Kit?](#-does-spec-kit-use-spec-kit) - [🌟 Development Phases](#-development-phases) - [🎯 Experimental Goals](#-experimental-goals) - [🔧 Prerequisites](#-prerequisites) @@ -321,6 +322,22 @@ Spec-Driven Development is a structured process that emphasizes: - **Multi-step refinement** rather than one-shot code generation from prompts - **Heavy reliance** on advanced AI model capabilities for specification interpretation +## 🪞 Does Spec Kit Use Spec Kit? + +Yes — we dogfood Spec Kit while developing Spec Kit, especially for substantial +features and changes to the development workflow. Contributors are asked to test +relevant changes through the Spec-Driven Development commands, and the +[feature assessment workflow](./.github/workflows/feature-assess.md) installs the +CLI from the current checkout and runs Spec Kit's `assess` extension against +feature requests. + +This does not mean every change goes through the full workflow. Small fixes can +use the normal issue, pull request, review, and test process. Most generated +dogfooding scaffolding and feature artifacts (`.specify/`, `specs/`, and agent +command files) are also intentionally gitignored, so they usually do not appear +in the repository history. See the [contributor development +workflow](./CONTRIBUTING.md#development-workflow) for the validation expectations. + ## 🌟 Development Phases | Phase | Focus | Key Activities | From cc01a85a72df269524d6eb926048301eeadb7588 Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Tue, 1 Sep 2026 06:38:11 -0500 Subject: [PATCH 2/3] docs: clarify agentic workflow dogfooding Assisted-by: GitHub Copilot (model: GPT-5.6 Sol, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4d15814-30af-4ed9-a57e-24d81fbaca4d --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index e4afe801a7..4077dd0048 100644 --- a/README.md +++ b/README.md @@ -326,10 +326,12 @@ Spec-Driven Development is a structured process that emphasizes: Yes — we dogfood Spec Kit while developing Spec Kit, especially for substantial features and changes to the development workflow. Contributors are asked to test -relevant changes through the Spec-Driven Development commands, and the -[feature assessment workflow](./.github/workflows/feature-assess.md) installs the -CLI from the current checkout and runs Spec Kit's `assess` extension against -feature requests. +relevant changes through the Spec-Driven Development commands. The +[feature assessment workflow](./.github/workflows/feature-assess.md) is currently +the automated dogfooding path: its setup uses the CLI from the current checkout +to initialize Copilot and install the `assess` extension, after which Copilot +follows the generated assessment skills against feature requests. The other +agentic workflows currently operate independently of the Specify CLI. This does not mean every change goes through the full workflow. Small fixes can use the normal issue, pull request, review, and test process. Most generated From 1945a7773fdf1342ee985c45fbdfb2bd381dd695 Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Tue, 1 Sep 2026 07:30:19 -0500 Subject: [PATCH 3/3] docs: correct dogfooding gitignore details Assisted-by: GitHub Copilot (model: GPT-5.6 Sol, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4077dd0048..db31a48be2 100644 --- a/README.md +++ b/README.md @@ -334,10 +334,12 @@ follows the generated assessment skills against feature requests. The other agentic workflows currently operate independently of the Specify CLI. This does not mean every change goes through the full workflow. Small fixes can -use the normal issue, pull request, review, and test process. Most generated -dogfooding scaffolding and feature artifacts (`.specify/`, `specs/`, and agent -command files) are also intentionally gitignored, so they usually do not appear -in the repository history. See the [contributor development +use the normal issue, pull request, review, and test process. Dogfooding +scaffolding and artifacts under `.github/agents/`, `.github/prompts/`, +`.github/copilot-instructions.md`, `.grok/`, `.specify/`, and `specs/` are +intentionally gitignored. The automated assessment workflow is ephemeral and +neither commits nor pushes its generated Copilot skills, so its output does not +enter repository history. See the [contributor development workflow](./CONTRIBUTING.md#development-workflow) for the validation expectations. ## 🌟 Development Phases