What problem does it solve? Maintainers and devtool teams who share their work publicly struggle to decide how much to disclose, how often to publish, and where to draw the line, and often burn out or overshare as a result. This Skill turns those decisions into a written charter the project can execute for a year. ## Core Features & Use Cases - Disclosure ladder selection: Ranks three practices (release-anchored shipping log, decisions-and-failures essays, open-startup dashboard) by efficiency, value, effort, and compliance cost, then recommends a rung matched to the project's goal and capacity. - Boundary and stop-condition design: Defines hard blocks (unpatched vulnerabilities, third-party data, MNPI), grey-zone decisions (roadmap dates, solo-maintainer income), a four-question pre-publish check, and a pre-committed stop condition for each disclosure. - Cadence, surfaces, and measurement: Sizes a cadence pattern against the worst month's capacity, picks one owned anchor surface plus amplifiers, and sets quarterly outcome-based signals instead of vanity metrics. - Use Case: A solo maintainer of a 3k-star Go library with four spare hours a month gets a recommendation to drop the planned metrics dashboard, adopt a release-spine cadence tied to an upcoming conference talk, and a charter with a pause rule written in advance. ## Quick Start Ask the assistant to design a build-in-public practice for your open-source project, stating your goal, available hours per month, and whether you are solo, bootstrapped, or funded.
