Built in the open. Yours to improve.

A clause the checker passed that your reviewer caught, a deviation date that does not match the memo you are holding, a protest decision filed under the wrong ground. These are the highest-value reports on the project and the hardest to find without a practitioner looking. An issue with the clause number, the date you expected, and where you got it is enough; a citation to the memo makes it immediate.

Most of what slows acquisition down is procedural, not technical, and it does not show up in any repository. How your office actually routes a Section I review, which step eats the afternoon, what you paste between two systems because nothing connects them. Workflow notes like these decide what gets built next as much as any feature request.

Code, prompts, reference data, documentation, all welcome. Small and focused beats large and sweeping: one clause correction that is obviously right merges faster than a refactor that needs a conversation first. If a change is big enough that you would want agreement before writing it, open an issue and say what you have in mind.

Install a skill, run the dashboard, and report what went wrong. Setup instructions that assume too much, an error that says nothing useful, a step that only works on one operating system. Nobody sees these except the person hitting them for the first time.