What problem does it solve? Most events publish a code of conduct with no enforcement behind it: no named response team, no working reporting channel, no sanctions ladder. This Skill produces both halves - the published policy document and the pipeline of named people who can act on a report before the event ends. ## Core Features & Use Cases - Policy drafting and scope clause: Adapts an established template (MLH, PyCon US, confcodeofconduct.com lineage) and writes the scope clause covering people, spaces, dates, and off-site conduct, including sponsors, booth staff, unofficial fringe events, and event-supplied transportation. - Reporting channels and response team: Designs the channel mix (published alias, anonymous intake, visible on-site responders) and staffs a named 3-6 person team with conflict-of-interest recusal rules and a fixed decision method. - Incident runbook, sanctions ladder, and appeals: Provides an on-site intake sequence, capture fields, a published response clock, a pre-published sanctions ladder with asymmetric appeal rights, and transparency reporting. - Use Case: A first-edition 800-person conference needs a code of conduct live before ticket sales open in three weeks. The Skill runs a scoping interview, adapts an established text, stands up a named response team and channels, and publishes a ladder and response clock before the policy goes live. ## Quick Start Ask the assistant to write a code of conduct and incident reporting process for your upcoming conference, including the response team and sanctions ladder.
