--- name: onenote-prod-checklist-364ffe1df2fd description: >- Decide whether a OneNote integration is ready for production from evidence across delegated access, content safety, correctness, limits, operations, and rollback. Use when reviewing a launch or material change. Trigger with "review OneNote production readiness", "OneNote go-live checklist", or "approve OneNote launch". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: " " version: 1.7.0 license: MIT author: Jeremy Longshore tags: [saas, onenote, readiness] model: inherit effort: high compatibility: "Designed for Claude Code; live OneNote actions require network access, delegated authentication, and explicit approval" --- # OneNote Production Readiness Decision ## Overview Decide whether a OneNote integration is ready for production from evidence across delegated access, content safety, correctness, limits, operations, and rollback.. This workflow produces an auditable decision or artifact before any live action. ## Prerequisites - Current first-party Microsoft Graph OneNote documentation and the selected integration's tested contract. - Named identity, content, workload, security, and operations owners appropriate to the requested scope. - Synthetic or approved non-production fixtures with secrets and real notebook content removed. ## Current Contract A launch is ready only when the actual user-bound auth lifecycle, approved content roots, supported v1.0 operations, pagination, HTML semantics, throttling, monitoring, and reconciliation are evidenced together. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. ## Authentication Verify delegated scope, consent owner, token-cache protection, tenant and user binding, revocation, and reauthentication. App-only fallback is a launch blocker. ## Instructions 1. Verify immutable artifact, dependency, configuration, migration, and test receipts. 2. Confirm account type, tenant, user, app registration, delegated scopes, and approved user, group, or site roots. 3. Review reads, writes, HTML, binary parts, paging, errors, limits, and unsupported-feature assumptions. 4. Review data classification, logs, retention, queues, monitoring, incidents, and support custody. 5. Exercise canary, failure, revocation, 429, rollback, and reconciliation paths. 6. Issue GO, CONDITIONAL GO, or NO-GO with owners, expirations, and rollback triggers. ## Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, delegated credentials, tenant or notebook content, consent, file transfer, deployment, writes, spend, sharing changes, or deletion. ## Approval Boundaries Named release, security, identity, content, and operations owners approve their controls. Any content mutation or broad consent requires separate explicit approval. ## Error Handling - NO-GO on app-only auth, undocumented delta or webhook calls, unbounded retries, or incomplete pagination. - A skipped negative or rollback test remains an open condition. - Do not waive tenant or user binding as operational detail. ## Output Return the signed control matrix, evidence links, failed gates, decision, conditions, owners, expiry, and rollback authority. Identify assumptions, owners, expirations, and evidence gaps explicitly. ## Examples - Reject a release that assumes Retry-After on OneNote 429s. - Approve a read-only canary only after revoked-consent handling passes. ## Validation Exercise and record these paths with expected and observed results: - app-only blocker - pagination - HTML mismatch - 429 - revocation - rollback ## Resources - [Current first-party evidence map](references/official-docs.md) — recheck dated sources before relying on mutable behavior. - Treat observed tenant behavior as environment-specific evidence, never a universal OneNote guarantee. --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/onenote-pack/skills/onenote-prod-checklist/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/onenote-pack/skills/onenote-prod-checklist/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, Product Manager, Technical Product Manager Specialties: API Tools: Azure, Onenote Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 031cd73027cae51ade1e395d60d3d17ed1572ddf1f6ea6124aa9b56e71538ec5