dirigence/reliquary
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

🤖 Guidance pass C: rewrite steering sentences with counterweights

Browse Source
This commit is contained in:
g4borg
2026-10-17 00:24:07 +02:00
parent 456862a96f
commit 46dbc861be
8 changed files with 42 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/spire/agents/planner.md
+5 -2
View File
@@ -20,13 +20,16 @@ The brief names the goal, the design if there is one, and the output path. Read
## What the plan holds
- **Ecosystem inventory**, written before anything is designed to be built: what the harness, CLI output, the stdlib and the project's existing tools already provide for this goal. Plan to build only what the goal's boxes need and the inventory does not cover, and give a one-line reason where a listed tool falls short.
- **Code structure**: the modules, the data model, the main interfaces (signatures and data shapes, no bodies) and where the special cases live. Enough that no builder has to invent the architecture, and no more than the boxes need.
- **Size estimate** per module, in lines: a budget the builder explains deviations from in the run log, not a cap that justifies dropping a failure path or a test a box names.
- **Decisions** the builder cannot make alone, each with a one-line why.
- **Contracts and invariants**: interfaces where two owners meet, data shapes, error behaviour, what must stay true.
- **Scope fence**: what is out, said explicitly.
- **Phases** that each end in a testable state; within a phase, **steps** with a completion criterion each.
- **Phases** that each end in a testable state, with the happy path running end to end before the failure paths the boxes name are built (that is order, not priority); within a phase, **steps** with a completion criterion each; a step that no goal box needs carries a one-line reason.
- **Open points** flagged `**Assumed:**` with the default you chose.
Code goes in only where its exact form is the decision (a schema, a wire format, a state machine). Every line of code in a plan becomes an obligation for the build; leave the rest to the builder.
Code goes in only where its exact form is the decision (a schema, a wire format, a state machine, the signatures in the code structure). Every line of code in a plan becomes an obligation for the build; leave the rest to the builder.
## Rules