hora-plan
Plan one version from its spec. Fixes which version is being built, verifies the spec for holes and contradictions in conversation, and writes the feature-level task list. Runs at the root of the hora repository. Invoked by /hora, or directly as /hora-plan.
openreachtech · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add openreachtech/hora-core --skill hora-planAbout this skill
name: hora-plan description: Plan one version from its spec. Fixes which version is being built, verifies the spec for holes and contradictions in conversation, and writes the feature-level task list. Runs at the root of the hora repository. Invoked by /hora, or directly as /hora-plan.
hora-plan
The planner. Decide which version is being built, get its spec into a state that can actually be built, and write the list of features to build.
Read ../hora/references/structure.md first — the layout, the invariants and the language rule. ../hora/references/asking.md fixes how anything here is put to a person, and it is the same file /hora-spec reads.
The three things this skill does
1. Fix the version being implemented
2. Verify the spec for holes and contradictions, and resolve them in conversation
3. Write the task list — one entry per feature, plus the acceptance tasks
The task list is feature-level, never implementation-level. "Build the attendance feature" is an entry. "Write the RpaFlow model" is a checkpoint inside /hora-build, and this skill does not decide it.
This skill may write into specs/. Only /hora-spec may too
Planning is a conversation with whoever wrote the spec, and asking that person to hand-edit twenty separate holes defeats the point of having it. So this skill may write into specs/, under ../hora/references/structure.md, invariant 1:
1. state the hole or contradiction found
2. propose the exact edit, in full
3. wait for that person to approve THAT edit
4. write it
Approval is per edit, never blanket. What is protected is that no requirement enters specs/ without a human having read the exact words first.
Step 2 is a proposal, and it is said as one — "I suggest this edit; it is yours to decide". Where the finding is instead that this skill may have misread the document, that is a check — "I read this as X; is that right?" — settled before any edit is proposed (../hora/references/asking.md). Half of what looks like a hole in a spec is a hole in the reading of it.
Step 3 stays in prose. The edit's exact words have to be read, and an option labelled "approve" is what lets somebody not read them. Everything around it defaults to the question tool.
A finding that needs design work goes to /hora-spec instead, at the stage that owns it. The split is by what the fix is, not by how large it looks:
| The finding | Where it is fixed |
|---|---|
a missing annotation, a target that names no repository, a typo, a section number that drifted | here, one edit at a time |
| a missing use case, a use case the design cannot serve, an operation with no kind or no caller, a scope split nobody has made, a contradiction between two designed things | /hora-spec, at the stage ../hora-spec/references/stages.md names |
Why it is not all done here. A use case written into specs/ by the planner is a use case no stage ever walked against a data model or a screen.
Never write into a past version's directory. A fix that belongs to an already-released version goes into the version currently being planned, as a full replacement of that section.
1. Fix the version
A version directory is one under specs/ whose name is a semver version, and nothing else. specs/skeleton/ holds the blank spec — never planned, never implemented, never counted as unfinished. Any other non-semver directory is skipped, and reported once so nobody assumes it was read.
The target version: among those directories, the lowest one whose .hora/tasks/<version>/ has not been generated or still holds unfinished features. If all are finished, the lowest version that exists under specs/ but not under .hora/tasks/. If there is no such version either, report that every version is complete.
Only the directory name counts. If the version written inside spec.md contradicts it, have a human fix it.
If the target version's spec.md is empty or missing, hand the run to /hora-spec and stop. Never write the first spec of a version here — writing it without those stages means writing use cases nothing ever walked against a design.
A version whose .hora/spec/<version>/_stages.md holds a split handoff not marked consumed is handed over the same way. A hand-written spec satisfies the test above while the moved criteria sit unread; the handoff's presence is as mechanical a test as the emptiness (../hora-spec-horizon/SKILL.md, "Splitting a version under way").
Resolve the diffs first
Sort the version directories in ascending semver order and apply them in turn, each overwriting the last. The lowest version is complete; every one after it is a diff against the version immediately before it.
1.0.0 full
1.0.1 overwrites 1.0.0
1.1.0 overwrites 1.0.1 ← the previous version is the base, not the lowest one
The key for overwriting is id. A section that does not appear in the diff is carried over unchanged.
| What the diff wrote | Result |
|---|---|
| heading and annotations only | annotations are overwritten one by one; the body carries over from the previous version |
| heading, annotations and body | the whole body is replaced (partial patches of prose are not supported) |
Because of this rule, reviving a section takes three lines.
# Payroll
<!-- id: payroll -->
<!-- kicked: no -->
No target, no depends, no body. Only kicked is overwritten.
Deferring is expressed as "kicked: yes in this version, kicked: no in the next". kicked: yes carries over through diffs.
rows is the one annotation that does not carry over. Read it from the section as this version writes it, never from the resolved document: a version that does not write it runs every row target names, where one that inherited an earlier version's rows would silently skip a row nobody chose to skip.
**Files of past
Read the complete source ↗