problem-brief

Topics in the source

• Problem Brief
• Overview
• When to use
• Called as /problem-brief with nothing else asked — walk the open questions
• When the operator answers or rules — this turn, before anything else
• Before raising anything — search, by class
• Start of every run — state check
• The entry — five parts, in this order

A problem brief is a published page whose one job is to let the operator rule without opening the repository. Every entry states a problem, proves it, and ends with a recommended way out. It is not a status report. The brief's JSON is the memory, not the conversation. Answers given in chat are lost when the session is summarised; to the operator, being asked again what they already answered is the worst failure this skill can have. The reader was not in your session and will not open a file. An entry that cannot be understood from the page alone is not finished. Every write to a brief's JSON goes through brief, short here for node /.claude/skills/problem-brief/bin/brief.mjs. Never edit the file by hand or with a script: each command validates the result and refuses to write anything broken, writes the change note, keeps the stamps in order and locks the file while it writes. brief --help lists every command and flag; brief set --field value changes any field the others do not cover. By default, unasked: anything the operator must rule on — a finding with more than one way out, an open decision, a question — goes into the brief for that subject (or a new one). Chat carries only the

This is an excerpt. Refer to the complete source and its current requirements.