Menu
Use when writing durable public design prose for RFCs, proposals, architecture notes, and canonization summaries where the document must serve users, implementers, maintainers, educators, and future readers.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review the conversation for threads that were started but not followed — ideas mentioned in passing, decisions deferred implicitly, tensions named but not resolved. Use when taking stock, before saving, or whenever the user wants to know what's been left on the table.
Use when drafting, updating, or reviewing a GitHub pull request title or body, including PR creation flows that need reviewer-facing prose. Follow the repo PR template when present, preserve the user's or project's voice, and route validation/session details to the right surface.
End-of-day close: the user is stepping away and won't serve as a bridge. Full collaborative triage, working-style reflection, and anticipatory framing for the next day. Invoke with /session-close.
Start a new session cycle by reconciling Project Orientation, restoring repo context, and resuming the active bet or opening vision steering when selection genuinely changed.
End-of-cycle transition: interpret the session, triage dangling threads with the user, and prepare SESSION-TRAJECTORY.md for the next cycle. The user is still around and serves as a light bridge. Invoke with /session-rest.
Keeps SESSION-TRAJECTORY.md warm as work progresses and offers checkpoints at natural boundaries. Saving is not stopping.
| name | public-design-reasoning |
| description | Use when writing durable public design prose for RFCs, proposals, architecture notes, and canonization summaries where the document must serve users, implementers, maintainers, educators, and future readers. |
| user-invocable | false |
Write design prose as public reasoning that future work can rely on.
A durable design document explains why a change should exist, what shape it takes, how it affects the system around it, and what readers can safely carry forward. The prose is concise because each sentence has a job in the argument. It is precise because future readers will use it without the conversation that produced it.
Public design prose serves multiple audiences at once. Users need to understand the effect on their work. Implementers need the contract they are building. Maintainers need the tradeoffs and compatibility surface. Educators need the conceptual path. Future readers need to know what decision was made and what evidence supported it.
The skill is to make one coherent account that lets each audience find its part without turning the document into parallel explanations.
A standards proposal explains a new language feature by connecting motivation, semantics, examples, edge cases, and migration into one public argument. The proposal succeeds when people can implement, teach, and later revise the feature from the same document.
An architecture record explains a system boundary by naming the forces that made the boundary necessary, the contract the boundary creates, and the changes that would call the decision back into question.
A curriculum note explains a new idiom by showing the reader why the idiom exists, how it fits nearby concepts, and what practice should become natural after the explanation.
The shared shape is public continuity: prose that carries a design from private reasoning into a durable artifact other people can build from.
Template sections are reader contracts. A section title promises a kind of help: motivation makes the change worth considering, detailed design makes it buildable, drawbacks make the tradeoff honest, alternatives make the choice legible, and unresolved questions mark what is still being learned.
Inhabit the job of the section before writing into it. If a section has no live work to do for the current artifact, compress it or explain the specific reason it is empty.
This stance composes with collaborative-grounding when the design depends on the user's situated intent, socratic-elicitation when that intent needs to be articulated, interpretive-synthesis when many design details need one coherent account, hypothesis-evaluating when readiness depends on evidence, and relational-continuity when wording must remain attached to the work that produced it.
