Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

hora

Implement an application from its spec. Decides where a project stands and runs the five skills that do the work — spec, setup, plan, build, accept — one feature at a time, each to acceptance before the next starts. Runs at the root of the hora repository. Started or restarted only by an explicit `/hora` invocation.

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

About this skill


name: hora description: Implement an application from its spec. Decides where a project stands and runs the five skills that do the work — spec, setup, plan, build, accept — one feature at a time, each to acceptance before the next starts. Runs at the root of the hora repository. Started or restarted only by an explicit /hora invocation.

hora

The orchestrator. Decide where this project stands, run the skill that comes next, and own every git operation on the way.

/hora does no implementation of its own. Five skills do the work:

SkillDoesRuns
/hora-specwrites the version's spec, in conversation — stage 0 reads what already exists, then its own seven stagesonce per version, until stage 7 passes
/hora-setupcreates the repositories the spec declares, fills in the project's values, reads the real treeonce per version, idempotent
/hora-planfixes the version, verifies the spec in conversation, writes the feature listonce per version, re-entered every run
/hora-buildtakes one feature through the eighteen checkpointsonce per feature
/hora-acceptruns the full unit suites every time, and the acceptance review at the invocation's reachat each feature's checkpoint 18 (scoped), and once as a whole-version sweep (full)

An emergency fix is not one of the five. /hora-hotfix takes one defect to main on its own, gives up the acceptance review, and records what it gave up as a debt. /hora reports that debt; /hora-plan turns it back into work (../hora-hotfix/SKILL.md).

Replacing a running system starts before the five, and /hora never starts it. /hora-replace describes the old system from its code in several passes and proposes a scope, and a person places what it wrote in annex/ and request/ before /hora-spec runs (../hora-replace/SKILL.md).

Read references/structure.md before anything else — the repository layout, where a per-repository command runs, and the three invariants all come from there. references/commits.md holds every git rule.


The shape of a run

/hora-spec ─> /hora-setup ─> /hora-plan ──┬─> /hora-build #A ─> /hora-accept ─┐
                                          ├─> /hora-build #B ─> /hora-accept ─┤
                                          └─> /hora-build #C ─> /hora-accept ─┴─> sweep ─> merge

One feature goes all the way to acceptance before the next one starts. Backend, then frontend, then acceptance — per feature, not per layer. Building every backend task, then every frontend task, then testing, means the first time anyone finds out whether a feature works is after all of them are written.

Re-entrancy is the center. A single session does not run to the end. Each run decides where it is and continues from there. Nothing is ever redone because a session ended — every checkpoint's checkbox is written the moment it passes.

Serial down to the checkpoint. No feature ever runs alongside another, and no checkpoint alongside another checkpoint.

/hora-fast is the other scheduler. It builds several features at once, each in its own git worktree, on the same feature files this one writes. A person chooses it by invoking it instead of /hora (../hora-fast/SKILL.md).

Inside a checkpoint, its units do run together. Five of the eighteen divide into units whose files are exclusive — a table, a module, an operation, a component, a screen — and each gets an implementer of its own. The checkpoint stays one gate with one exit condition (../hora-build/SKILL.md, "Step 5 — splitting a checkpoint into units").


Whether hora can start at all

The procedures /hora orders are not in this repository, and /hora never puts them in place itself. They arrive as skills of their own, alongside these, and this is the one thing to confirm before deciding anything else.

Is there at least one skill under .claude/skills/ whose name carries an
hoc- / hor- / hof- / hos- prefix?
                             if not → stop. Report that the implementation
                                      skills are not equipped, and ask for
                                      them to be equipped before rerunning

Is /hora-setup under .claude/skills/ too?
                             if not → stop. Report that code setup is not
                                      equipped, and ask for it before
                                      rerunning

/hora-setup is asked for here because it is not in this package either. What it does is one stack from beginning to end — which repositories exist, what fills them, what to read once they arrived — so it is written by the boilerplate that knows that stack, and equipped from there. /hora orders it like the rest, and a project whose boilerplate has not put it in place cannot get past step 2.

Nothing here checks the hora skills themselves. /hora is one of them, so a session that reached this line has already proved they are equipped. What cannot be known from the inside is the other package's state, and that is the whole of what this section asks.

A partial set is not a failure. Which of them a repository equips is its own decision, and a checkpoint that finds nothing covering its work says so and carries on (references/structure.md, "How the match is made"). Only the empty case stops, because there nothing is covered at all.

How they are equipped is not this file's business. Say what is missing, not what command to run — the route differs by repository, and naming one of them here would be wrong wherever the other is used.


Deciding where you are

With that settled, do this every time — a fresh start and a restart alike.

0. git fetch origin --prune, for the hora repository and every declared row
   that already exists. Then check for a hotfix that landed on main
   (references/commits.md, "Keeping release/<version> curren
Read the complete source ↗