Skip to content

donald-ada/workinggenius / skills/genius-file

genius-file

Verified

Read and update Working Genius work files — the work's folder holding the bounded snapshot a cold session acts on, the append-only log behind it, and the contract that binds the unbuilt slices. Use when a stage skill needs the work-file discipline, when the user asks what work is in flight or where a piece of work left off, or before resuming any work tracked under .genius/.

FileKindSize
BACKLOG-FORMAT.mdmarkdown4.8 KB
FILE-FORMAT.mdmarkdown20.4 KB
FORMAT-EDGES.mdmarkdown3.9 KB
SKILL.mdskill md7.1 KB
measure.pyexecutablescript18.3 KB
stop-judge.pyscript3.5 KB

FORMAT-EDGES.md

View on GitHub
# Format Edges

What [FILE-FORMAT.md](FILE-FORMAT.md) leaves out on purpose: the two cases a session meets rarely, and the measurements behind rules that would otherwise read as arbitrary. Read it when you meet the case, or before disagreeing with a rule. `/compact` links here, and `/reconcile` reaches it through the format's pointer, when they meet a key with prose after it; a slice close never reads it.

## A heading that broke its own anchor

A log heading that appends prose after its key (`## s4-board 配置状态牌四件`) is a different anchor from the key, so every link to it is already broken. **The repair is the link, never the heading** — and every link to it, not the first one you saw. The heading records and the snapshot binds; fixing the heading edits a record to spare a binding file an edit, which is the layering exactly backwards (`errata` skill). This is the case that most tempts a retroactive pass into editing a log, and the one `/compact` checks for before calling a link's target missing: it looks missing and is not.

## A log from before the tree

A log written before it became a tree holds its entries in `<slug>.log.md` itself, under their own `##` keys. **They stay where they are**: the log is never edited, and `.genius/BACKLOG.log.md`, which can never be repaired, may point at them as `<slug>.log.md#<key>`. The next entry goes to its branch under `log/`, with its line appended to the root below the old entries, so the file reads its old entries first and the tree after, and `measure.py anchors` lists both. Moving the old entries out would be a pass that edits a record to tidy a shape, which is what the format's one-format rule never asks of a record.

## What was measured

The rules are what they are because of these, and a rule reopens the way every ruling here reopens — a counter-example somebody measured, named against the leg it breaks.

- **Characters, not lines.** At 90 columns on one real Chinese work file, a 305-line snapshot displayed as 595 lines (1.95×) and a 17-line backlog as 82 (4.82×); one entry ran to 842 columns on a single physical line. A line budget rewards not pressing return; characters cannot be reflowed away. (`5a5f6de`)
- **Not bytes.** `wc -m` under an unset or `C` locale reported 9596 on a compliant 4939-character CJK snapshot. A ceiling defended by an instrument that silently doubles on the writing system that motivated it is worse than no ceiling. (`5a5f6de`)
- **A ceiling without an object does not hold.** One real snapshot's character count across its own commits ran 1514 → 3444 through Discernment, 8320 at contract v1, 25621 at the sixth slice — over the ceiling from the commit after the plan and never back under, with every close nominally compacting. That is why compaction has a question, and why the contract has its own file. (`76fd725`)
- **The log does not already hold what a collapse displaces.** On a real work file the log carried every distinctive token of the later slices' paragraphs and only 57–78% of the first two slices', because early entries are thinner than the summaries written above them. That is why a collapse appends verbatim and never reads the log to decide what is redundant. (`5a5f6de`)
- **Provenance is not a removal trigger.** Block titles in the contract's established layer are written as "who established this", not "who still needs it"; an eviction pass keyed on those titles threw away the newest rule in the file. That is why the established layer is never drained.
- **A seed that became its work can still lose content.** Measured once: a backlog seed's stated rule reached no section of the work that absorbed it. That is why the line leaves only after checking the work took the seed's content up. (`84f227b`)
- **A line bound does not bound the file.** On one real project sixteen commits took `BACKLOG.md` from 748 to 10062 characters, and none of them left it smaller. That is why the backlog gets a log behind it and the same invariant a work has. (`96d2144`)
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall