← ClaudeAtlas

choiceslisted

Summarize the open decisions/choices from the current conversation into a simple, copy-paste WhatsApp message for the team to weigh in on. Use when work is blocked on product/scope decisions a human must make.
Jewgah/claude-code-skills · ★ 2 · AI & Automation · score 73
Install: claude install-skill Jewgah/claude-code-skills
# Choices - WhatsApp decision summary Generate a concise, copy-paste WhatsApp message (English) that lists the open decisions the team needs to make, based on the current conversation. This is the sibling of `/explain-dev` (which announces *finished* work in French): `/choices` surfaces *pending* decisions in English so the team can pick. ## The audience is ALWAYS the client Every `/choices` message is written to be forwarded to the CLIENT (the partner or stakeholder who pays for the work), never to an internal dev channel. Write it as if the client is reading every line, because they are. Two consequences that are easy to get wrong: - **Address the client in the second person.** If a named person owes an answer and that person is the recipient, write "you answered 1 to 4 in July but not this one", never "Alex answered 1 to 4". Third-personing the reader is an instant tell that the message was written for someone else. - **Money questions: ask what is theirs to decide, never what is mine.** The line is who the decision belongs to, not whether money is mentioned. - **Legitimate** (the client genuinely decides): approving a quote for upcoming work, which period to bill something to, whether to authorise more spend, how to prioritise a fixed envelope. Put these in plainly, with a number when I have one. - **Never** (mine alone): whether I gift, absorb, discount or write off work, my margin, my capacity, my internal hour estimates. "Should I gift y