hora-spec-usecases
Stage 1 of /hora-spec. Fix who uses the product and what each of them completes end to end, and — where something already runs — how far each feature is built and whether it is specified or only listed. Writes the document information, the actors, the terminology, the existing assets, and every feature's two blocks. Invoked by /hora-spec, or directly.
openreachtech · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add openreachtech/hora-core --skill hora-spec-usecases技能说明
name: hora-spec-usecases description: Stage 1 of /hora-spec. Fix who uses the product and what each of them completes end to end, and — where something already runs — how far each feature is built and whether it is specified or only listed. Writes the document information, the actors, the terminology, the existing assets, and every feature's two blocks. Invoked by /hora-spec, or directly.
hora-spec-usecases
Stage 1 of /hora-spec. Nothing else in a spec can be decided until this is: a table has nothing to hold, an operation has nobody calling it, and a screen has no reason to exist.
Read ../hora/references/structure.md and ../hora-spec/references/principles.md first. ../hora-spec/references/stages.md is the authority on this stage's exit condition, and ../hora/references/spec-format.md on the format of everything written here.
What this stage decides
who uses this product, what each of them is called, and how each is identified
what each of them comes here to complete, start to finish
which of those this release will serve at all
what the product is called
what the words mean
what already exists, whether it may be used, and how much of it this version accepts
What it must not decide
| Whose it is | |
|---|---|
| which table holds any of it | stage 4 |
| which operation serves a use case | stage 4 |
| which screen a use case passes through | stage 5 |
| whether a use case is in this release or the next | stage 2 — this stage collects them all, including the ones that will be deferred |
| where a behavior that spans several features is checked | stage 2, which holds the order. This stage hands it over rather than placing it |
| what a role may and may not do, operation by operation | stage 6 |
| a class name, a table name, an identifier | /hora-plan. A term and its description are all that belongs here |
Collect more than this release will build. A use case that stage 2 defers is what stage 2 weighs, and it is where stage 3's foreseen numbers come from.
The conversation
Where stage 0 found something running, start from what it read, not from a blank page. Put the implied feature list and actor candidates up as checks, batched per area. A conversation about a list somebody is amending is far shorter than one about a list they must produce (../hora-spec/references/investigation.md).
What no surface implies is question 1, 3, 5 and 6. Why it exists, what somebody is trying to accomplish, what they do without it, and what must never happen are not in any tree.
Ask in this order. Each answer narrows the next question.
1. What is this for, in one sentence? Who is worse off if it does not exist?
2. Who uses it? For each one:
what do you call them (their word, not a generic one)
how are they identified — a login, an invitation, a device, nothing at all
roughly how many of them
inside the organisation, or outside it
3. For each of those: what do they come here to do?
Push for whole sentences. "Attendance" is a heading; "a member of staff
who forgot to clock in files yesterday's hours the next day" is a use case
4. Which of those happens every day, and which once a month?
5. What do they do today, without this? Is there code, and may it be used?
And where there is code: when it and the spec disagree, which one is right —
as-built (what runs is what this version is) or to-spec (the spec is; the
code catches up)? And how much of what already runs does this version's tag
claim — verified (every inherited feature specified and accepted before it)
or inventoried (a feature may be listed unaccepted, one at a time)?
6. What must never happen?
7. What is the product called?
then, before 8, and only where Baseline: inventoried was declared: which
features are listed rather than specified? Per feature, four at a time, and
never an option inside 8 (below)
8. Only where something is already running: how far is each feature actually
built? Under as-built the derived table goes up whole, then each feature
is confirmed by selection; under to-spec it is never asked; without a
declaration, it is asked per feature, open (below)
Question 3 is the stage. Everything else supports it.
| Push for | Away from |
|---|---|
| who is doing it | "the system does X" |
| what they are trying to achieve | "there is a button for X" |
| where it starts and where it is done | a step in the middle, with no beginning |
| enough that somebody with no access to the code could follow it | selectors, endpoints, table names |
Question 4 is not small talk. Frequency decides what a screen puts first at stage 5, and the once-a-month operation that touches everything is usually the heaviest one stage 3 is about to ask for.
Question 5 has four parts wherever code exists, and two on a new project. What exists; whether it may be read (which one it is may never be inferred — ../hora/references/structure.md, invariant 2); which side is authoritative when the code and the spec disagree; and how much of what already runs this version's tag claims (../hora/references/spec-format.md, "Existing assets"). One question each, two options each, and Authority is overridable per feature (<!-- authority: -->).
The last two are both asked before question 8, never after, because each decides how question 8 is asked at all. Authority decides its shape — a derived table to confirm, or an open question per feature. Baseline decides whether the listing question is asked at all, and what a built: answer then does: acted on, or merely recorded.
verified is required wherever code exists, and it is what adoption has always done. Writing the line down turns it from an unstated default into a choice somebody made; inventoried is that choice going the other way.
**Both lines are approved in prose, on their own, and neither is ever folded into an opt
阅读完整来源 ↗