Skip to content

Commit 70fc8b1

Browse files
mnriemCopilot
andcommitted
docs(assess): distinguish empty project from no project
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
1 parent 68619ff commit 70fc8b1

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

β€Žextensions/assess/README.mdβ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Discovery answers *"is this worth building?"* Delivery answers *"how do we build
66

77
## Overview
88

9-
`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.
9+
`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.
1010

1111
Each idea lives in its own directory under `.specify/assessments/<slug>/`, with one Markdown artifact per stage:
1212

β€Žextensions/assess/commands/speckit.assess.intake.mdβ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The user input is the idea and (optionally) a slug. Treat it as one of:
2121
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.
2222
4. **A mix** of the above.
2323

24-
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.
24+
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.
2525

2626
If the input is empty, ask the user for the idea (interactive), or stop with a note that there is nothing to intake (automated).
2727

0 commit comments

Comments
Β (0)