dx-references

Run a discovery conversation and write a brief — the problem, the evidence behind it, the scope, the decisions, and the next uncertainty to resolve.

Think through a raw idea before committing to it — weigh alternatives, price doing nothing, and route to a change, an effort, or nothing at all.

Actively sharpen the ubiquitous language in foundation/glossary.md.

Feedback-loop-first diagnosis for bugs and performance regressions.

Create, edit, or promote a standard in context/standards/ — from the conversation, a graduated lesson, or another project.

Interview to settle the problem framing, alternatives, and user cases for a change or effort before planning — writes frame.md.

Interview and write plan.md for a change — matches standards, surfaces priors, owns Progress.

Triage findings from a review report and apply the fixes you choose.

Decompose an effort into an ordered list of vertical slices and write roadmap.md.

Mine the project's real conventions from tooling, code, and docs and write them into the standards layer.

Hunt the codebase for refactor opportunities, present them inline, and promote the ones you pick into changes.

Investigate one topic — codebase or external doc — and write it down with provenance for a plan to lean on.