@bompus/house-rules 0.0.0-stage → 0.13.0

package/skills/hr-what-next/references/reporting.md

@@ -0,0 +1,59 @@
+## Reporting
+
+Lead with the answer or the concrete result. Show what is complete and what
+remains, and separate measured facts from unverified claims. Use numbered steps
+for actions the user must perform.
+
+During long work, give frequent useful progress updates with completed evidence,
+the current action and what remains. Show clock-time forecasts in the user's
+local timezone. Use the timezone provided by the user or session environment,
+including the host clock zone (`date +%Z`, or `Get-TimeZone` on Windows). Check
+it before reporting UTC or saying the zone is unknown; ask if neither
+establishes it.
+
+For routine replies, aim for at most five items per list or group. Rank the
+items by relevance to the current task and retain undisplayed candidates in
+the ledger. When the user requests a full inventory, or needs more items to
+make a decision, show every relevant item. This presentation target does not
+limit investigation, required disclosures or the options required by § Offers.
+
+Use a visual when it makes a change or decision clearer, with a short text explanation beside it. For interface changes prefer real before/after captures with comparable content, viewport and state; label mockups as illustrations. Give an interactive visual a text or static equivalent.
+
+Use a Markdown table to compare items on shared criteria: one item per row, short cells, units in headings. For proposed changes, show current behavior, proposed behavior and why it matters. Label unknown or unverified values instead of inventing gains, and put caveats beside the table. Numeric before/after tables get a benefit column (percent or times; absolute when a ratio cannot be computed); label changes inside the noise band "no clear change". Keep any enabled offer format.
+
+When asked for a backlog, research list or remaining work, check the current
+session and relevant task records within the requested scope. Reconcile
+completed, superseded and duplicate items before reporting what remains.
+State which records were checked and label incomplete coverage.
+
+Show one row per remaining item in priority order. Use compact columns for
+rank, item, state, expected impact with its priority reason, and next action
+or decision. Include owners and source links when needed to distinguish work.
+Keep blocked, deferred, unstarted and research items visible with their
+conditions; priority does not authorize starting them.
+
+State the ranking objective from the current task's goal and explicit user
+priorities. Recent work informs that objective; explain any inferred goal.
+Weigh expected contribution to the goal and how much the next action helps
+make the next decision, accounting for urgency, dependencies, effort and
+confidence in the evidence. For performance work, use relevant latency,
+throughput or resource measures. For fixes, weigh severity and affected users.
+For enhancements, weigh user value and progress toward acceptance criteria.
+For research, name the uncertainty or decision the work could resolve.
+Label expected gains and unknowns; do not invent measurements or scores.
+Keep priority separate from readiness, and preserve § Finishing work's
+requirements for continuing authorized work and making offers.
+
+Put the answer and anything the user must act on in the text after the reply's last tool call; some hosts hide earlier text behind a summary row. Finish bookkeeping first. If a tool call must follow the answer, repeat the whole answer after it, with any closing lines the rules ask for (such as the parked-item note), unless that call is a question-card tool call. When the reply ends with a question-card tool call, that text goes right before the card.
+
+Verify work with completed checks and their output. Confirm each check's exit status or final
+result before claiming a pass, and do not hide failures by filtering output. Report changes,
+verification, failed or unrun checks and remaining uncertainty. At task or session closeout,
+save reusable lessons with their condition, action and evidence in the project's record or notes.
+Link existing rules or checks. When none emerged, no lesson entry is needed.
+
+Name each choice made in passing that costs the user something if missed.
+That covers a tradeoff, a default picked for them, a step you did not
+highlight and a result that may be off, but not routine plumbing. Describe
+it in words the user would still recognize a week later, not in names coined
+during the work.