跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

hora-fast

Build a version's features several at a time, each in its own git worktree, after the parts they share have been built once. Uses the same spec, plan, feature files and acceptance as /hora, and replaces only the scheduling. Invoked instead of /hora, by an explicit /hora-fast, when one feature at a time is too slow for the version.

openreachtech · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add openreachtech/hora-core --skill hora-fast

技能说明


name: hora-fast description: Build a version's features several at a time, each in its own git worktree, after the parts they share have been built once. Uses the same spec, plan, feature files and acceptance as /hora, and replaces only the scheduling. Invoked instead of /hora, by an explicit /hora-fast, when one feature at a time is too slow for the version.

hora-fast

The parallel scheduler. Same spec, same plan, same feature files, same acceptance as /hora. What changes is when a feature's checkpoints run: several features at once, each in its own worktree, after the parts they share have been built once and fixed.

The design in one sentence: each feature is verified statically as it lands; the version is verified live, once, at the end. A feature's checkpoint 18 is the browser-less gate run /hora-accept already defines. The browser-driven review runs once, over the whole version, at the sweep.

Read ../hora/references/structure.md first, then ../hora-build/references/checkpoints.md. Both apply here unchanged, and so does every git rule in ../hora/references/commits.md.


What is shared with /hora, and what is replaced

shared, unchanged/hora-spec, /hora-setup, /hora-plan, /hora-accept, /hora-hotfix; the three invariants; every branch and commit rule; the eighteen checkpoints and their exit conditions; the feature file, its run record and the acceptance records; what "done" means
replaced/hora's "one feature to acceptance before the next starts", and /hora-build's "never alongside another feature"
addedthe foundation, the worktrees, the parallel loop, the merge step, the drain, and one record file

The feature file is the contract between the two schedulers. Every checkbox this skill writes into .hora/tasks/<version>/<feature-id>.md is one /hora-build would have written, with the same marks, the same run record and the same checkpoint 18. Either scheduler can continue a version the other started: each reads the first [ ] and goes on from there ("Switching between the two schedulers", below).

This skill edits no hora file and restates none. Where a rule below reads like one in /hora-build, it is a pointer.


What to say before starting

Run the equipment check /hora runs (../hora/SKILL.md, "Whether hora can start at all"). Then estimate what /hora would take from here, and say it:

pace       seconds per feature: wall-time: summed over a feature's lines, from
           the run records of the features already done in this version, or
           from the previous version while none is done
remaining  features in _plan.md still [ ]

pace x remaining            what /hora would take from here
its share on 1, 2, 9, 11    what neither scheduler shortens

Ask whether there is a date. Do not assume one. Most versions have none, and wanting the version sooner is reason enough to be here. Where a date exists and the serial estimate fits it, say so; the person chooses which scheduler runs.

Read the four conversation lines apart. wall-time: on checkpoints 1, 2, 9 and 11 is mostly a person answering, and it is the same under either scheduler. A version whose time sits mostly on those four lines gains little here. Say so when the records show it.

A person chooses this skill by invoking it, and the invocation is the whole decision (../hora/references/structure.md, "Where a lever lives", question 2). The record says who chose it ("The record", below).


Deciding where you are

/hora's steps, with 4a and 5 inserted. Do this every time.

0.   As /hora: fetch and prune everywhere, catch up with a hotfix, read the
     open hotfix debts. Then, in every declared repository:
       git -C <repository> worktree list
     Every worktree under .worktrees/ is a feature in flight. Report them

1-4. As /hora: spec -> /hora-spec, missing row -> /hora-setup, always
     /hora-plan, a blocking question -> stop

4a.  Is a main working copy on a feature/ branch — a feature /hora left
     mid-gate?                     if so -> move it into a worktree ("Moving
                                            a mid-gate feature", below).
                                            Stop only if the move fails

5.   Is the foundation built and fixed?
                                   if not -> build it ("The foundation")

6.   Are there features still [ ] whose next gate may open?
                                   if so -> run them, up to the limit ("The
                                            parallel loop"). A feature whose
                                            only open checkpoint is 18 gets
                                            its gate run ("Checkpoint 18, and
                                            the sweep")

7-8. As /hora's 6, 6a and 7: no [ ] left and no passing full sweep
     -> /hora-accept, whole-version; then the merge into main

Report the decision in one line before starting — "continuing 1.0.0 in parallel. Foundation fixed, 4 of 11 features done, 3 in flight, opening #payroll".


The foundation

Every file two features would both write is built once, before any feature starts. This is /hora-build's exclusivity rule one level up: there, a file two units would both write goes to one of them; here, a file two features would both write goes to the foundation.

It is derived against release/<version>'s tip. What the remaining features share and the tip already holds — a table an earlier feature built, a Base member already merged — is done, not foundation work. On a version /hora started, most of it is.

What is in it

Found where
the contracts, per serveralready derived and pinned by /hora-plan, step 3. They are the foundation's core
a table more than one remaining feature reads or writesthe spec's data model, read against each feature section. The data mod
阅读完整来源 ↗