From 68619ff94830c3976082989ec2eec320600683ee Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Fri, 24 Jul 2026 16:03:28 -0500 Subject: [PATCH 1/2] docs(assess): clarify the pipeline works on an empty project MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit State explicitly in the README and intake command that the assess pipeline requires no existing source code. An empty, freshly initialized project and an existing codebase are equally valid starting points — the input is just an idea (pasted text, a URL, a ticket, or a codebase pointer). Assisted-by: GitHub Copilot (model: Claude Opus 4.8, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9df2615e-6a99-4cdc-b4b2-fc72029bc1d9 --- extensions/assess/README.md | 2 ++ extensions/assess/commands/speckit.assess.intake.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/extensions/assess/README.md b/extensions/assess/README.md index 06cf5d1af6..0b3b425254 100644 --- a/extensions/assess/README.md +++ b/extensions/assess/README.md @@ -6,6 +6,8 @@ Discovery answers *"is this worth building?"* Delivery answers *"how do we build ## Overview +`assess` works equally well for a **freshly initialized, empty project** or for an **existing codebase** — you do not need any source code to assess an idea. The input is just an idea: pasted text, a URL, or a ticket work with no repo at all, and a codebase pointer lets you assess an idea for existing code. Neither is more "correct" than the other. + Each idea lives in its own directory under `.specify/assessments//`, with one Markdown artifact per stage: ``` diff --git a/extensions/assess/commands/speckit.assess.intake.md b/extensions/assess/commands/speckit.assess.intake.md index dac575c227..54bfc3597e 100644 --- a/extensions/assess/commands/speckit.assess.intake.md +++ b/extensions/assess/commands/speckit.assess.intake.md @@ -21,6 +21,8 @@ The user input is the idea and (optionally) a slug. Treat it as one of: 3. **A codebase pointer** — phrasing like "an idea for this repo" or a path. Read enough of the repository to record what the idea relates to. 4. **A mix** of the above. +There is **no requirement for existing source code**: intake works just as well for an empty, freshly initialized project as for an existing codebase. Pasted text or a URL (options 1–2) need no repo; a codebase pointer (option 3) targets existing code. Both are equally valid. + If the input is empty, ask the user for the idea (interactive), or stop with a note that there is nothing to intake (automated). ## Slug Resolution From 70fc8b1eabd28620bb97024befa0a656ff5b000c Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Fri, 24 Jul 2026 16:13:28 -0500 Subject: [PATCH 2/2] docs(assess): distinguish empty project from no project MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarify that assess still runs inside an initialized Spec Kit project (writing under .specify/assessments/) — only existing source code is optional. Reword 'no repo at all'/'need no repo' to 'need no existing codebase' so users don't expect intake to work outside a Spec Kit project. Assisted-by: GitHub Copilot (model: Claude Opus 4.8, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9df2615e-6a99-4cdc-b4b2-fc72029bc1d9 --- extensions/assess/README.md | 2 +- extensions/assess/commands/speckit.assess.intake.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/extensions/assess/README.md b/extensions/assess/README.md index 0b3b425254..b6af9a2289 100644 --- a/extensions/assess/README.md +++ b/extensions/assess/README.md @@ -6,7 +6,7 @@ Discovery answers *"is this worth building?"* Delivery answers *"how do we build ## Overview -`assess` works equally well for a **freshly initialized, empty project** or for an **existing codebase** — you do not need any source code to assess an idea. The input is just an idea: pasted text, a URL, or a ticket work with no repo at all, and a codebase pointer lets you assess an idea for existing code. Neither is more "correct" than the other. +`assess` runs inside an initialized Spec Kit project (it writes assessments under `.specify/assessments/`), but that project can be **completely empty of source code** — a freshly initialized project with no code works just as well as an established codebase. The input is just an idea: pasted text, a URL, or a ticket need no existing code, while a codebase pointer lets you assess an idea for code that already exists. Neither starting point is more "correct" than the other. Each idea lives in its own directory under `.specify/assessments//`, with one Markdown artifact per stage: diff --git a/extensions/assess/commands/speckit.assess.intake.md b/extensions/assess/commands/speckit.assess.intake.md index 54bfc3597e..02cfec9f14 100644 --- a/extensions/assess/commands/speckit.assess.intake.md +++ b/extensions/assess/commands/speckit.assess.intake.md @@ -21,7 +21,7 @@ The user input is the idea and (optionally) a slug. Treat it as one of: 3. **A codebase pointer** — phrasing like "an idea for this repo" or a path. Read enough of the repository to record what the idea relates to. 4. **A mix** of the above. -There is **no requirement for existing source code**: intake works just as well for an empty, freshly initialized project as for an existing codebase. Pasted text or a URL (options 1–2) need no repo; a codebase pointer (option 3) targets existing code. Both are equally valid. +There is **no requirement for existing source code**: within an initialized Spec Kit project, intake works just as well when the project is empty of code as when it already has a codebase. Pasted text or a URL (options 1–2) need no existing codebase; a codebase pointer (option 3) targets existing code. Both are equally valid. If the input is empty, ask the user for the idea (interactive), or stop with a note that there is nothing to intake (automated).